[google-appengine] Re: Java 9, 10 and forward on App Engine Standard

2018-08-01 Thread 'Jordan (Cloud Platform Support)' via Google App Engine
For clarification, the article you are referencing pertains to future Java 8 updates and support requiring an Oracle Java SE Advanced Desktop or Oracle Java SE Suite subscription starting in 2019. Therefore yes Java will continue to be free on App Engine Standard, but supported versions of Java

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

2018-08-01 Thread 'George (Cloud Platform Support)' via Google App Engine
Hello Yi, 503 is a back-end error, and a little too general to be useful. You mention that you have recently changed your app's business logic. This might have impacted your back-end behavior, and thus result in these 503 errors. The recommended practice, in such cases, is to implement

[google-appengine] Re: GCP components update causes “ConnectionRefusedError: [Errno 111] Connection refused” errors

2018-08-01 Thread 'George (Cloud Platform Support)' via Google App Engine
The he Nginx process would serve a 502 error for different reasons, so in itself, this message is not very useful. You may get 502 errors for an exception in your application, for an internal API call that causes an exception, but also if a request isn't replied to within the prescribed

[google-appengine] Re: Java 9, 10 and forward on App Engine Standard

2018-08-01 Thread 'Nicola Spreafico' via Google App Engine
+1 Il giorno mercoledì 1 agosto 2018 14:59:52 UTC+2, Leejjon ha scritto: > > Since Java 9, Oracle will release new Java versions every half year. > > I don't want to sound impatient, but supporting Java 8 took a long time. > Since Java 9 containing stuff like Jigsaw it looks to me that it would

[google-appengine] Re: GCP components update causes “ConnectionRefusedError: [Errno 111] Connection refused” errors

2018-08-01 Thread epssdev
Figured out that GCP uses python 3.6 when python_version is set to 3 in app.yaml Changed the version to 3.5. Hopefully, this should solve some problems. On Tuesday, July 31, 2018 at 10:10:33 AM UTC-7, eps...@gmail.com wrote: > > My GCP deployment was working fine until I did "gcloud components

[google-appengine] GCP deploy with 'python_version: 3.5' still uses python 3.6

2018-08-01 Thread epssdev
GCP app has been deployed without any errors, but the runtime configurations are not being considered. I have the following runtime settings for python in app.yaml runtime_config: python_version: *3.5* But I see this error: Traceback (most recent call last): File

[google-appengine] Re: gae flexible + firebase/firestore

2018-08-01 Thread ara howard
awesome. thanks for the info! easy to work around now. On Friday, 27 July 2018 14:35:40 UTC-6, ara howard wrote: > > i'm trying to build an admin (rails app) that adjusts some data in a > project we have in firebase that uses cloud firestore. however, getting > some really some feedback from

[google-appengine] Java 9, 10 and forward on App Engine Standard

2018-08-01 Thread Leejjon
Since Java 9, Oracle will release new Java versions every half year. I don't want to sound impatient, but supporting Java 8 took a long time. Since Java 9 containing stuff like Jigsaw it looks to me that it would be quite some work to support it (but good because it might make it easier to

[google-appengine] Re: GCP components update causes “ConnectionRefusedError: [Errno 111] Connection refused” errors

2018-08-01 Thread epssdev
Figured out that the GCP uses python 3.6 if the runtime config in app.yaml is 3. My app uses python 3.5, there are some subtle differences between python 3.5 and 3.6 that may be causing errors. 'python_version: 3.5' should downgrade the runtime env runtime_config: python_version: 3.5 On