Well. It turned out I was indeed doing something wrong and this was in no
way GCP tools' fault. After a more thorough study, what was happening was:
- All the files *had* been uploaded properly; dug through the staging GCS
bucket and there it was
- The error I was getting was not due to a file not being uploaded, instead
it was a silly case (sic) of require()'in the file in question with
improper character case
- The reason it worked locally was due to OSX's *FUN* feature of being case
ignorant; I was able to do require('foo/Bar.js') even if that one file was
really called foo/bar.js
Case closed, sorry for wasting your time. Should have known better than to
question my beloved AppEngine. As a long time Linux user this "feature" of
OSX never came to my mind before a colleague pointed it out.
- M
On Monday, September 9, 2019 at 6:13:23 PM UTC+3, George (Cloud Platform
Support) wrote:
>
> How did you run your command, exactly?
>
> What is the output from the following commands?
>
> gcloud components update
> gcloud info
> gcloud app deploy --verbosity debug
>
> You should edit out all private information, such as project numbers, from
> the copied output.
>
> This error is displayed usually when not all your files and directories
> under the app directory are ASCII-only, or when "app.yaml" contains some
> non-ASCII characters. All these need to be ASCII, as well as all gcloud
> command parameters.
>
> To facilitate communication, and set proper privacy levels, you are
> encouraged to open a similar issue in the Public Issue Tracker
> <https://issuetracker.google.com/>.
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/6ad8f840-b51a-49eb-84f7-9419ecd03ff1%40googlegroups.com.
