I'm trying to deploy my project to vercel but I got this error
I have checked my imports but I couldn't find any mistake including ChartOverview
Can anyone review my code please ? this is my repo
https://github.com/iceddrop/muse
Related
I been using Vercel for quite a while, it's never been a headache for me until now, i'm facing a very weird situation, since yesterday it doesn't matter how many git push i do to my project (it only has one branch, main) Vercel keeps deploying the same old version of it. I got no errors from Vercel, it tells me it's been ok, it's deployed, but it's still an old version of my project.
ps: i'm developing a webapp using nodejs + astro, i think isn't relevant...
I'm running out of possible solutions, I've tried to delete the deployment on Vercel and create it again, nothing works.
Working on a 3d globe using threejs, I have the deployment running on GitHub pages, I had to install vite.js to facilitate the use of importing .glsl files for 3d stuff, after installing vite and trying to run GitHub pages I get the error "Canceling since a higher priority waiting request for 'pages build and deployment # main' exists" and every git push I have made after that has resulted in the error "docker pull failed with exit code 1" what does this mean?
the first screenshot is the list of failed deployments to GitHub pages.
the middle screenshot is the initial error.
the last screenshot is the error I've been getting ever since the initial one.
I have even made a new repository and still getting the same error which makes me think not has nothing to do with vite but something is wrong with GitHub.
Any advice would be appreciated.
I'm trying to deploy from acceptance to production but I'm getting this error:
##[error]NotFound: Error retrieving function keys.
##[error]Check out the troubleshooting guide to see if your issue is addressed: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting
##[error]Task failed while creating or updating the template deployment.
Finishing: Azure Resource Group Deployment
This is the link to the full image since I can't post images:
Mentioned error
I don't know what can be wrong, all the deployments from dev are working good until I find the main and last branch.
Thanks for your help.
I am trying to deploy a github.io app and it has been working so far, but now I am having an issue with build and deployment. I can build the files without any issue on local server, but when I try to publish it on github server by pushing it, it throws a build and deployment error saying:
Error: Error: No uploaded artifact was found! Please check if there are any errors at build step.
I tried to remove the repo and create it again, but still get the same error.
I am very new to this and I have no idea what to do. I have seen some references to empty submodules after cloning, but I didn't clone it.
Any suggestions what else I can check?
I'm new to Azure DevOps (VSTS) and I'm attempting to set up a new Pipeline build using the Artifactory Maven build step. When running the build I get the following error:
2018-09-12T20:59:02.0861829Z ##[error]Error: Command failed: D:\a_jfrog\1.19.1\jfrog.exe rt mvn "install -f D:\a\1\s\pom.xml" D:\a\1\s\config --build-name="SomeProject-Maven-CI" --build-number="20180912.6"
2018-09-12T20:59:02.0988256Z [Error] Wrong number of arguments. You can read the documentation at https://www.jfrog.com/confluence/display/CLI/JFrog+CLI
I found this info on GitHub: https://github.com/jfrog/jfrog-cli-go/issues/165
Its a similar error but not quite the same. I'm not sure how to edit the command that Azure Pipeline is running or even if I can.
I figured out my issue. I had a space included in my build name and it apparently the JFrog Cli didn't like that. When I removed the space the error went away. Other errors came up but that's off-topic from this question.
Can you please report the errors your encountered in Artifactory VSTS extension's GitHub repository?
We'll really appreciate it.
Update: A pull request opened to target this issue. You can track it here.
Update 2: Fixed in latest release 1.4.0.