Closed Rob46 closed 7 years ago
CT4E doesn't auto-update itself, unless you have Eclipse configured to auto-update plugins.
That said these are errors from code that ship as part of the Google Cloud SDK (gcloud
). Have you updated that recently?
What's odd use that the file URLs look like they have been doubly percent-encoded: Program%2520Files
.
I think I did update gcloud via the command line after yesterday's deploy.
I did notice that in Eclipse the app engine version is listed as 1.9.51 whereas when I type gcloud version I see 1.9.54
I simply issued gcloud components restore and sure enough I can deploy again.
How am I supposed to update gcloud components? Is this a bug or am I doing something wrong?
I did notice that in Eclipse the app engine version is listed as 1.9.51 whereas when I type gcloud version I see 1.9.54
This shouldn't be a problem. That said, I think your gcloud is below 162.0.1. The 162.0.1 version went out last week and is supposed to fix this JSP compilation problem.
Unfortunately, looks like the latest version 162.0.1 doesn't update app-engine-java. It's still at the problematic 1.9.54.
Can you try again after moving (or copying) the gcloud directory to a path that does not contain any space? You will need to configure the new location in the preferences in Eclipse: Window > Preferences > Google Cloud Tools.
@Rob46: I did notice that in Eclipse the app engine version is listed as 1.9.51 whereas when I type gcloud version I see 1.9.54
Is this the version you see in the App Engine API library (as shown below)? If so, that's ok: that library is replaced as part of the deploy process.
Could you tell us what gcloud components list --show-versions
?
briandealwis, yes exactly.... that is exactly what I saw when it was failing and now that it is working (not changed). All I did was the gcloud restore and it started working again. This is what I currently see:
Configure Build Path > App Engine API > the number I see is 1.9.51 (same as image above)
And after the restore, at the command line on Windows 10:
$ gcloud version
Google Cloud SDK 157.0.0
app-engine-java 1.9.53
app-engine-python 1.9.54
bq 2.0.24
core 2017.05.30
gcloud
gsutil 4.26
@Rob46 I think you're hitting https://issuetracker.google.com/63417794. gcloud 161 (and seemingly 162 too) have a problem with spaces in a Cloud SDK path. A workaround is to downgrade below 161 (gcloud components update --version 159.0.0
) or move/copy the Cloud SDK to a path without spaces as I said.
Thanks. I'll try waiting for the next release. I know its google, but any idea when? About a week based on release history?
Finally fixed in the latest gcloud 171.0.0 that just went out.
should we set 171.0 as our minimum gcloud version?
Nothing has changed with the application. Yesterday it deployed without issue. Today I get a long list of errors as shown below (entire output included).
How to fix?