-
Notifications
You must be signed in to change notification settings - Fork 604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Response:[400] Invalid character in file name. #973
Comments
@leekyungmoon You might have some luck posting this over on StackOverflow: http://stackoverflow.com/questions/tagged/gcloud. @jonparrott -- any ideas for this one? |
Just realized you already posted on SO: http://stackoverflow.com/questions/33980536/google-app-engine-error-with-gcloud |
How could you do that? ... it's not solved... how could you close this 2015-12-01 1:56 GMT+09:00 Stephen Sawchuk notifications@github.com:
|
Sorry, I should have mentioned I closed it because it was not just asked on SO, but answered. Did you see it?:
|
* chore(main): release 5.2.1 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
When I try to deploy my app with the command : "gcloud preview app deploy app.yaml --promote"
I got an error below :
ERROR: (gcloud.preview.app.deploy) Error Response: [400] Invalid character in filename: node_modules/gcloud/node_modules/gce-images/node_modules/google-auto-auth/node_modules/google-auth-library/node_modules/jws/node_modules/base64url/node_modules/meow/node_modules/indent-string/node_modules/repeating/node_modules/is-finite/node_modules/number-is-nan/index.js Deleted [https://www.googleapis.com/compute/v1/projects/photozzlewithnodejs-1136/zones/us-central1-f/instances/gae-builder-vm-20151129t162546].
Anyone having the same error and the solution for this?
The text was updated successfully, but these errors were encountered: