[google-appengine] Re: Error while handling "large'ish" number of parallel requests

[Vinay Chitlangia]

On Sunday, October 2, 2016 at 10:29:31 PM UTC+5:30, Adam (Cloud Platform 
Support) wrote:
>
> How many instances exist when the traffic burst occurs? Are you hitting 
> your defined max of 10 or is it not able to scale up to the maximum?
>
The number of instances does not go beyond 5.  

>
> Two possibilities come to mind: hitting the instance max and requests are 
> then being discarded, or scaling isn't happening quickly enough and there 
> are too many pending requests.
>
In the case of a "burst", there are ~20-30 concurrent requests.
And as I mentioned in the previous mail, the error code is 502, and no logs 
from my servlet. 

>  
>

> A value of 0 for "loading_request" means it was not the very first request 
> to the instance which caused it to spin up, which is normal for the 
> majority of requests.
>
 

>
> On Wednesday, September 28, 2016 at 10:36:46 AM UTC-4, Vinay Chitlangia 
> wrote:
>>
>> Hi,
>> I am using appengine flexible environment.
>>
>> I am facing issues when there is a sudden spurt of requests to our 
>> system. (About 30 requests in a second). The server gets back to normal in 
>> 5-10 seconds (perhaps with the decrease
>> in traffic again)
>> Generally the requests come at about 5-8 per second.
>>
>> I am running with 2 instances.
>>
>> 
>>   2
>>   10
>>   120
>>   
>> 0.7
>> 
>>
>>
>> AFAICT the requests did not hit my servlet. (I added a log, the first 
>> line in the servlet, and for failed request it does not get printed).
>> "loading_request" is 0 for the failed requests as well.
>>
>> The error code is 502
>>
>> Is it that the requests are queued while a new instance comes up? Is it 
>> possible to override that, that is start the process of bringing up the new 
>> servers,
>> but use the old one (if it is taking a while?). The log shows some of the 
>> request waiting for 600seconds, most though fail in 10-15ms.
>> The failure happens for between 0.5 to 2% of the requests
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5b90cc3e-594d-4942-90de-15258a415e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

[Thomas Wiradikusuma]

Hi Nick,

The web.xml snippet I gave earlier is the one before I take one out:

com.bla.ApiV2,com.bla.ApiV2Public

Notice class ApiV2 and ApiV2Public.

Also, I'm testing this from API explorer, which I think doesn't require the 
generation of client libraries. But, for curiosity sake, I did try it 
(https://cloud.google.com/endpoints/docs/frameworks/java/generate-client-libraries-android):

endpoints-framework-tools get-client-lib --war=target/war -bs gradle 
com.bla.ApiV2
endpoints-framework-tools get-client-lib --war=target/war -bs gradle 
com.bla.ApiV2Public

No error in the generation (but doesn't fix my issue).


Regards,
Thomas Wiradikusuma


On Tuesday, October 4, 2016 at 3:18:59 AM UTC+8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Thomas,
>
> Could you show what the web.xml file looks like before you take one out? 
> I'm not sure how you've included both of them and it appears you uploaded a 
> section from web.xml with only one Api class present.
>
> Also, just for testing's sake, have you managed to check whether 
> recompiling the client against the new API version resolves the issue?
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Sunday, October 2, 2016 at 11:24:21 PM UTC-4, Thomas Wiradikusuma wrote:
>>
>> Hi Nick,
>>
>> The error happens when receiving requests. I don't think it's necessary 
>> to update the client, as the update doesn't change the server.
>>
>> I'm posting here since I think it's either a bug of, or lack of 
>> documentation for, the V2 implementation @ApiClass. Let me explain.
>>
>> I have 2 classes that share @Api (
>> https://cloud.google.com/endpoints/docs/frameworks/java/multiclass): 
>>
>> @Api(name = "api", version = "v2", namespace = @ApiNamespace(ownerDomain 
>> = "bla.com", ownerName = "bla.com"))
>> @ApiClass(authenticators = {AccountManager.class}, scopes = 
>> {EMAIL_SCOPE}, clientIds = {API_V2_ANDROID_CLIENT_ID, API_V2_WEB_CLIENT_ID, 
>> API_EXPLORER_CLIENT_ID}, audiences = {API_V2_ANDROID_AUDIENCE})
>> public class ApiV2 { .. }
>>
>> @Api(name = "api", version = "v2", namespace = @ApiNamespace(ownerDomain 
>> = "bla.com", ownerName = "bla.com"))
>> public class ApiV2Public { .. }
>>
>> This is how they're defined in web.xml:
>>
>> 
>> api
>> com.google.api.server.spi.EndpointsServlet
>> 
>> services
>> 
>> com.bla.ApiV2,com.bla.ApiV2Public
>> 
>> 
>> 
>>
>> If I take out one from web.xml, it works. 
>>
>> This used to work in V1. It could be due to this new property "issuers" 
>> that's poorly documented (compare 
>> https://cloud.google.com/appengine/docs/java/endpoints/annotations vs 
>> https://cloud.google.com/endpoints/docs/frameworks/java/annotations, 
>> Ctrl+F for "issuers").
>>
>> Looking forward for a solution!
>>
>> Regards,
>> Thomas Wiradikusuma
>>
>>
>> On Saturday, October 1, 2016 at 4:54:42 AM UTC+8, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Thomas,
>>>
>>> This is just a guess, but it could be that it's necessary to update the 
>>> client as well. Does that error occur when you deploy, or when you receive 
>>> a request? That would be the way to determine if the issue is in the client 
>>> needing to be updated or another issue (not clarified as yet) in the server 
>>> code. 
>>>
>>> As a quick side-note, this forum is meant for general high level 
>>> discussion of the platform and services, design patterns, etc. So a thread 
>>> like this should actually be a Stack Overflow  
>>> post. Not to worry as we watch that forum as well. You are more likely to 
>>> find more users who can help, though, with a technical question in that 
>>> forum.
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Tuesday, September 27, 2016 at 9:29:27 PM UTC-4, Thomas Wiradikusuma 
>>> wrote:

 Hi guys,

 I'm a longtime user of Cloud Endpoints (v1), and decided to give v2 a 
 try. So I followed 
 https://cloud.google.com/appengine/docs/java/endpoints/migrating and 
 here's my diff:

 - compile 'com.google.appengine:appengine-endpoints:1.9.42'

 + compile 'com.google.endpoints:endpoints-framework:2.0.0-beta.8'


 - 
 com.google.api.server.spi.SystemServiceServlet

 + 
 com.google.api.server.spi.EndpointsServlet


 - /_ah/spi/*

 + /_ah/api/*


 I did *not* run the "generating client lib" as documented in 
 https://cloud.google.com/endpoints/docs/frameworks/java/generate-client-libraries-android
  as I thought, "from the client perspective it should be the same".


 I hit this error in the server:


 SEVERE: javax.servlet.ServletContext log: unavailable

 com.google.api.server.spi.config.validation.InconsistentApiConfigurationException:
  
 api: API-wide configuration does not match between the classes 
 com.foobar.ApiV2Public and com.foobar.ApiV2. All API classes with the same 
 API name and version must have the exact same 

[google-appengine] Re: Gcloud App Engine does not include django; Intentional?

['Adam (Cloud Platform Support)' via Google App Engine]

Thanks for reporting this. I'll do some investigation and will update the 
thread when I have more info.

On Friday, September 30, 2016 at 11:45:17 AM UTC-4, Evan Jones wrote:
>
> It appears that the documentation now recommends using the version of App 
> Engine shipped with gcloud (via gcloud components install 
> app-engine-python). However, this version does not include any of the 
> built-in versions of Django, which can be loaded by adding references to 
> the "libraries" section. Is this an intentional change, or is this a bug? 
> It is annoying because it means that an app that works with the standalone 
> version of dev_appserver.py may not work with the gcloud version. It also 
> means the documentation is wrong in many places. Its relatively easy to fix 
> by vendoring django, but it would be nice to fix the documentation and make 
> the two distributions be the same.
>
> Details:
>
> Here is the diff -u output between ls 
> google-cloud-sdk/platform/google_appengine/lib and ls google_appengine/lib. 
> You can see that the gcloud version is missing all versions of django, and 
> graphy.
>
>
> --- appengine 2016-09-30 11:43:22.0 -0400
>
> +++ gcloud 2016-09-30 11:42:07.0 -0400
>
> @@ -8,17 +8,10 @@
>
>  concurrent
>
>  deprecated_enum
>
>  distutils
>
> -django-0.96
>
> -django-1.2
>
> -django-1.3
>
> -django-1.4
>
> -django-1.5
>
> -django-1.9
>
>  docker
>
>  endpoints-1.0
>
>  fancy_urllib
>
>  google-api-python-client
>
> -graphy
>
>  grizzled
>
>  httplib2
>
>  ipaddr
>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/464ecf6e-0624-46c6-85a6-d6cc5fe16b81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Kevin,

The speed of deployment can be changed by limiting the size of the uploaded 
app, limiting the complexity of the build necessary in the Dockerfile, if 
present, and by ensuring a fast and reliable internet connection. Other 
than these variables, it's hard to comment on what specifically might be 
making deployment exhibit the timing that it does on your system. 

I hope this is helpful - let me know if you have any further questions! 
I'll be happy to help!

Cheers,

Nick
Cloud Platform Community Suppor

On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>
>
> Is there a faster way to deploy an app? Google App Engine is slow to 
> deploy, hangs on "Updating service [someproject]..." I am using a flexible 
> environment with PHP.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/38982d93-7611-4978-b6cb-740517932f39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Not Able to Enable GCM API in Appengine

['Adam (Cloud Platform Support)' via Google App Engine]

Are you trying to enable Google Cloud Messaging in the API Manager in the 
Cloud Console? This mentions that FCM is the new version of GCM but does 
not perform any redirects. This API will still work with existing GCM 
clients.

It's also unclear what you mean regarding Django and Firebase, as it's not 
related to GCM / FCM. It would help if you could give a more detailed 
description about what steps you've taken. Screen shots are helpful as well.

On Friday, September 30, 2016 at 9:06:22 AM UTC-4, Subroto Biswas wrote:
>
> Hi
>
> I am having trouble Enabling GCM API in appengine's new project. I get 
> redirected to FCM page everytime (GCM is still supported I guess)
>
> Problem is I have a backend in django, and I have ported it to Firebase, 
> but unable to find a way make changes in my backend code and run it in 
> Firebase
>
> Thanks for any help
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d8c8f429-02c7-40e8-bc41-8271094a4616%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Deploy application :Error Response: [13] Timed out when starting VMs.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Diego,

It appears from the error that something is failing in the build of your 
node project. See these lines (I've reversed the order of lines since they 
were written bottom-to-top in the output you pasted):

npm ERR! Failed at the a2viewer@1.0.0 tsc script 'tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the a2viewer package,
npm ERR! not with npm itself.

So, you should check your Dockerfile and check the version of node.js and 
npm installed. Another good method of debugging before deployment is to 
build a container image from the Dockerfile using the docker build 
 command. Then 
use docker run  
and see if the container receives requests and processes them properly. Of 
course if you were using an App Engine standard runtime "compat" base image 
,
 
the RPC connections to the production APIs would fail, but for a Node JS 
app, you'll get a more or less perfect approximation of the container in 
deployment, except for the google infrastructure between your request and 
the container.

Let me know if you have any further questions!

Cheers,

Nick
Cloud Platform Community Support

On Monday, October 3, 2016 at 10:06:51 AM UTC-4, Diego Molteni wrote:
>
> HI Nick,
> These are the error that I received when i try to upload the application:
>
>
> 08:58:55.000
> npm ERR! /app/npm-debug.log
> 08:58:55.000
> npm ERR! Please include the following file with any support request:
> 08:58:55.000
> 08:58:55.000
> npm ERR! There is likely additional logging output above.
> 08:58:55.000
> npm ERR! npm owner ls a2viewer
> 08:58:55.000
> npm ERR! Or if that isn't available, you can get their info via:
> 08:58:55.000
> npm ERR! npm bugs a2viewer
> 08:58:55.000
> npm ERR! You can get information on how to open an issue for this project 
> with:
> 08:58:55.000
> npm ERR! npm run tsc
> 08:58:55.000
> npm ERR! Tell the author that this fails on your system:
> 08:58:55.000
> npm ERR! not with npm itself.
> 08:58:55.000
> npm ERR! If you do, this is most likely a problem with the a2viewer 
> package,
> 08:58:55.000
> npm ERR! Make sure you have the latest version of node.js and npm 
> installed.
> 08:58:55.000
> npm ERR! Failed at the a2viewer@1.0.0 prestart script 'npm run tsc'.
> 08:58:55.000
> npm ERR!
> 08:58:55.000
> npm ERR! Exit status 1
> 08:58:55.000
> npm ERR! a2viewer@1.0.0 prestart: `npm run tsc`
> 08:58:55.000
> npm ERR! code ELIFECYCLE
> 08:58:55.000
> npm ERR! npm v3.10.3
> 08:58:55.000
> npm ERR! node v6.7.0
> 08:58:55.000
> npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
> 08:58:55.000
> npm ERR! Linux 3.16.0-4-amd64
> 08:58:55.000
> 08:58:55.000
> npm ERR! /app/npm-debug.log
> 08:58:55.000
> npm ERR! Please include the following file with any support request:
> 08:58:55.000
> 08:58:55.000
> npm ERR! There is likely additional logging output above.
> 08:58:55.000
> npm ERR! npm owner ls a2viewer
> 08:58:55.000
> npm ERR! Or if that isn't available, you can get their info via:
> 08:58:55.000
> npm ERR! npm bugs a2viewer
> 08:58:55.000
> npm ERR! You can get information on how to open an issue for this project 
> with:
> 08:58:55.000
> npm ERR! tsc
> 08:58:55.000
> npm ERR! Tell the author that this fails on your system:
> 08:58:55.000
> npm ERR! not with npm itself.
> 08:58:55.000
> npm ERR! If you do, this is most likely a problem with the a2viewer 
> package,
> 08:58:55.000
> npm ERR! Make sure you have the latest version of node.js and npm 
> installed.
> 08:58:55.000
> npm ERR! Failed at the a2viewer@1.0.0 tsc script 'tsc'.
> 08:58:55.000
> npm ERR!
> 08:58:55.000
> npm ERR! spawn ENOENT
> 08:58:55.000
> npm ERR! a2viewer@1.0.0 tsc: `tsc`
> 08:58:55.000
> npm ERR! syscall spawn
> 08:58:55.000
> npm ERR! errno ENOENT
> 08:58:55.000
> npm ERR! code ELIFECYCLE
> 08:58:55.000
> npm ERR! file sh
> 08:58:55.000
> npm ERR! npm v3.10.3
> 08:58:55.000
> npm ERR! node v6.7.0
> 08:58:55.000
> npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
> 08:58:55.000
> npm ERR! Linux 3.16.0-4-amd64
> 08:58:55.000
> 08:58:55.000
> sh: 1: tsc: not found
> 08:58:55.000
> npm ERR! /app/npm-debug.log
> 08:58:55.000
> npm ERR! Please include the following file with any support request:
> 08:58:55.000
> 08:58:55.000
> npm ERR! There is likely additional logging output above.
> 08:58:55.000
> npm ERR! npm owner ls a2viewer
> 08:58:55.000
> npm ERR! Or if that isn't available, you can get their info via:
> 08:58:55.000
> npm ERR! npm bugs a2viewer
> 08:58:55.000
> npm ERR! You can get information on how to open an issue for this project 
> with:
> 08:58:55.000
> npm ERR! npm run tsc
> 08:58:55.000
> npm ERR! Tell the author that this fails on your system:
> 08:58:55.000
> npm ERR! not with npm itself.
> 

[google-appengine] Re: Endpoints v2 InconsistentApiConfigurationException

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Thomas,

Could you show what the web.xml file looks like before you take one out? 
I'm not sure how you've included both of them and it appears you uploaded a 
section from web.xml with only one Api class present.

Also, just for testing's sake, have you managed to check whether 
recompiling the client against the new API version resolves the issue?

Cheers,

Nick
Cloud Platform Community Support

On Sunday, October 2, 2016 at 11:24:21 PM UTC-4, Thomas Wiradikusuma wrote:
>
> Hi Nick,
>
> The error happens when receiving requests. I don't think it's necessary to 
> update the client, as the update doesn't change the server.
>
> I'm posting here since I think it's either a bug of, or lack of 
> documentation for, the V2 implementation @ApiClass. Let me explain.
>
> I have 2 classes that share @Api (
> https://cloud.google.com/endpoints/docs/frameworks/java/multiclass): 
>
> @Api(name = "api", version = "v2", namespace = @ApiNamespace(ownerDomain = 
> "bla.com", ownerName = "bla.com"))
> @ApiClass(authenticators = {AccountManager.class}, scopes = {EMAIL_SCOPE}, 
> clientIds = {API_V2_ANDROID_CLIENT_ID, API_V2_WEB_CLIENT_ID, 
> API_EXPLORER_CLIENT_ID}, audiences = {API_V2_ANDROID_AUDIENCE})
> public class ApiV2 { .. }
>
> @Api(name = "api", version = "v2", namespace = @ApiNamespace(ownerDomain = 
> "bla.com", ownerName = "bla.com"))
> public class ApiV2Public { .. }
>
> This is how they're defined in web.xml:
>
> 
> api
> com.google.api.server.spi.EndpointsServlet
> 
> services
> 
> com.bla.ApiV2,com.bla.ApiV2Public
> 
> 
> 
>
> If I take out one from web.xml, it works. 
>
> This used to work in V1. It could be due to this new property "issuers" 
> that's poorly documented (compare 
> https://cloud.google.com/appengine/docs/java/endpoints/annotations vs 
> https://cloud.google.com/endpoints/docs/frameworks/java/annotations, 
> Ctrl+F for "issuers").
>
> Looking forward for a solution!
>
> Regards,
> Thomas Wiradikusuma
>
>
> On Saturday, October 1, 2016 at 4:54:42 AM UTC+8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Thomas,
>>
>> This is just a guess, but it could be that it's necessary to update the 
>> client as well. Does that error occur when you deploy, or when you receive 
>> a request? That would be the way to determine if the issue is in the client 
>> needing to be updated or another issue (not clarified as yet) in the server 
>> code. 
>>
>> As a quick side-note, this forum is meant for general high level 
>> discussion of the platform and services, design patterns, etc. So a thread 
>> like this should actually be a Stack Overflow  
>> post. Not to worry as we watch that forum as well. You are more likely to 
>> find more users who can help, though, with a technical question in that 
>> forum.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, September 27, 2016 at 9:29:27 PM UTC-4, Thomas Wiradikusuma 
>> wrote:
>>>
>>> Hi guys,
>>>
>>> I'm a longtime user of Cloud Endpoints (v1), and decided to give v2 a 
>>> try. So I followed 
>>> https://cloud.google.com/appengine/docs/java/endpoints/migrating and 
>>> here's my diff:
>>>
>>> - compile 'com.google.appengine:appengine-endpoints:1.9.42'
>>>
>>> + compile 'com.google.endpoints:endpoints-framework:2.0.0-beta.8'
>>>
>>>
>>> - 
>>> com.google.api.server.spi.SystemServiceServlet
>>>
>>> + 
>>> com.google.api.server.spi.EndpointsServlet
>>>
>>>
>>> - /_ah/spi/*
>>>
>>> + /_ah/api/*
>>>
>>>
>>> I did *not* run the "generating client lib" as documented in 
>>> https://cloud.google.com/endpoints/docs/frameworks/java/generate-client-libraries-android
>>>  as I thought, "from the client perspective it should be the same".
>>>
>>>
>>> I hit this error in the server:
>>>
>>>
>>> SEVERE: javax.servlet.ServletContext log: unavailable
>>>
>>> com.google.api.server.spi.config.validation.InconsistentApiConfigurationException:
>>>  
>>> api: API-wide configuration does not match between the classes 
>>> com.foobar.ApiV2Public and com.foobar.ApiV2. All API classes with the same 
>>> API name and version must have the exact same API-wide configuration. 
>>> Differing property: issuers 
>>> (com.google.api.server.spi.config.model.ApiIssuerConfigs@0 vs 
>>> com.google.api.server.spi.config.model.ApiIssuerConfigs@d03e1481).
>>>
>>> at 
>>> com.google.api.server.spi.config.validation.ApiConfigValidator.validate(ApiConfigValidator.java:89)
>>>
>>> at 
>>> com.google.api.server.spi.SystemService.registerLoadedService(SystemService.java:218)
>>>
>>> at 
>>> com.google.api.server.spi.SystemService.registerService(SystemService.java:193)
>>>
>>>
>>> How do I fix this?
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit 

Re: [google-appengine] Re: Deferred tasks in flexible environment

['Alex Martelli' via Google App Engine]

On Sun, Oct 2, 2016 at 11:59 PM, Randy Sugianto  wrote:

> I already solved it.
>
> This is because the flexible environment does not support
>
> builtins:
> - deferred: on
>
> on app.yaml.
>
> You should mention this on the migration document or emit an error when
> deploying. This is a really bad experience for those migrating with the
> lack of proper documentation on this.
>
Yes it is, and thanks for pointing it out -- investigating I see this had
been reported (including workaround) almost a year ago in
http://stackoverflow.com/questions/33968512/failed-to-import-google-appengine-ext-deferred-handler-py-in-google-app-engine
, and -- my bad! -- I hadn't opened the internal bug needed to get it fixed
(at least in the docs, better of course, if feasible, in the code).

I have opened the internal bug now -- thanks again.


Alex



>
> On Mon, Oct 3, 2016, 04:30 'Adam (Cloud Platform Support)' via Google App
> Engine  wrote:
>
>> Could you post an example app.yaml that shows your configuration? Also,
>> if you are using 'google.appengine.ext.deferred.defer' to spawn your
>> tasks, have you tested using the App Engine Task Queue API
>>  directly?
>>
>>
>> On Wednesday, September 28, 2016 at 1:41:56 PM UTC-4, Randy Sugianto
>> wrote:
>>
>>
>> Since I switched my App Engine app to a flexible environment, it seems
>> that all tasks failed to run. I was surprised that all tasks failed. But
>> when I open the logs, I got only this:
>>
>> 01:33:56.026POST500167 B4 msAppEngine-Google; (+http://code.google.com/
>> appengine)/_ah/queue/deferred
>>
>> The status code is 500, but when I expand it, there is only this
>> information inside:
>>
>> 0.1.0.2 - - [29/Sep/2016:01:33:56 +0800] "POST /_ah/queue/deferred
>> HTTP/1.1" 500 167 http://0.xxx.module-sync.x.appspot.com/_ah/
>> background "AppEngine-Google; (+http://code.google.com/appengine)" "
>> module-sync.xx.appspot.com" ms=4 cpu_ms=0 cpm_usd=1.8663e-8
>> loading_request=0 instance=- app_engine_release=1.9.45 trace_id=-
>> {
>> metadata: {…}
>> protoPayload: {…}
>> insertId: "2016-09-28|10:34:00.180396-07|10.106.31.139|1292268011"
>> log: "appengine.googleapis.com/request_log"
>> httpRequest: {…}
>> operation: {…}
>> }
>> There is no exception or stack trace or anything else that I usually see
>> when I was using the standard environment.
>>
>> How can I troubleshoot this? Why are my deferred tasks not run?
>>
>> --
>> 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 google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/google-appengine/03062645-dc70-4c82-9907-
>> 5bcb2098e67f%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/CAE9VMVc6D1Z-RxbcEEoCRHr7NyA-
> AUjTJKUc6S3H60efc9MNiQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAE46Be8_Kx4xfiQ1B%3DopNAiE2YGF0q_sAVNgudHRuetDU9tksg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Leave project that I am an "editor"

['Adam (Cloud Platform Support)' via Google App Engine]

You need to be an owner to revoke project permissions (including your own), 
so you'll need to request that the project owner remove you.
More info is available at 
https://cloud.google.com/iam/docs/granting-changing-revoking-access.

On Thursday, September 29, 2016 at 9:19:41 PM UTC-4, Thiago Balbo wrote:
>
> How can I leave a project I am an "editor"? The options I've found are 
> below. I haven't found any option nor clickable button to leave.
>
>
> 
>
> Appreciate any help,
> Thanks,
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ecb8bae8-e2b1-4383-9c6a-6c70f6c05794%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: https ERR_TOO_MANY_REDIRECTS

[PK]

I am not using Cloudflare because when I looked at it I could not find a way to 
get my traffic encrypted from Cloudflare to Google and I cannot tell my 
customers that they enjoy end to end SSL when portion of the way is 
unencrypted. 

By the way, why would people use Cloudflare at all in front of the GAE front 
end?

PK
p...@gae123.com




> On Oct 3, 2016, at 9:16 AM, 'Adam (Cloud Platform Support)' via Google App 
> Engine  wrote:
> 
> Glad I was able to help. 
> 
> For others who may come across this thread, would you mind sharing your 
> solution? I'll guess that you had disabled the additional redirect in the 
> Cloudflare dashboard, as it's no longer needed when using 'secure: always'.
> 
> On Saturday, October 1, 2016 at 8:58:56 PM UTC-4, vasya Guskuskudu wrote:
> All ok. Thanks for the tip where to look.
> 
> суббота, 1 октября 2016 г., 5:16:10 UTC+10 пользователь Adam (Cloud Platform 
> Support) написал:
> Could you share the custom domain of your app? The 'secure: always' directive 
> causes a redirect from http:// <> to https://,  which can cause 
> problems if you're using another service that is also configured to use 
> redirects, such as Cloudflare.
> 
> On Tuesday, September 27, 2016 at 9:11:01 AM UTC-4, vasya Guskuskudu wrote:
> Hello. I have a project made on the flask + gae init. I installed 
> https://letsencrypt.org  certificate, and the site 
> works is via https + www and without it, if you type the address manually. 
> But if I set app.yaml to "secure: always" the site stops working in the error 
> on the client specified too many redirects. Please tell me where to look for 
> the causes of such behavior?
> 
> -- 
> 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 google-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/fe942b20-070f-42a4-9c37-54ec14938ef3%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0D958AE3-FAF8-4275-B94C-23C4E4BE8AB5%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: https ERR_TOO_MANY_REDIRECTS

['Adam (Cloud Platform Support)' via Google App Engine]

Glad I was able to help. 

For others who may come across this thread, would you mind sharing your 
solution? I'll guess that you had disabled the additional redirect in the 
Cloudflare dashboard, as it's no longer needed when using 'secure: always'.

On Saturday, October 1, 2016 at 8:58:56 PM UTC-4, vasya Guskuskudu wrote:
>
> All ok. Thanks for the tip where to look.
>
> суббота, 1 октября 2016 г., 5:16:10 UTC+10 пользователь Adam (Cloud 
> Platform Support) написал:
>>
>> Could you share the custom domain of your app? The 'secure: always' 
>> directive causes a redirect from http:// to https://, which can cause 
>> problems if you're using another service that is also configured to use 
>> redirects, such as Cloudflare.
>>
>> On Tuesday, September 27, 2016 at 9:11:01 AM UTC-4, vasya Guskuskudu 
>> wrote:
>>>
>>> Hello. I have a project made on the flask + gae init. I installed 
>>> https://letsencrypt.org certificate, and the site works is via https + 
>>> www and without it, if you type the address manually. But if I set app.yaml 
>>> to "secure: always" the site stops working in the error on the client 
>>> specified too many redirects. Please tell me where to look for the causes 
>>> of such behavior?
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fe942b20-070f-42a4-9c37-54ec14938ef3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Latency graph

[Deepak Singh]

Hi Nick,

Did you get a chance to look into it as the problem still persists ? Let me
know we can send our app id privately to you if required.

Regards
Tech team

On Fri, Sep 30, 2016 at 11:30 PM, Deepak Singh 
wrote:

> Hi Nick,
>
> We have done a rigorous analysis for the latency issue here and we came to
> the following conclusion -
>
> Latency was analysed for the same url/request with the same source code on
> flex env.
> Latency is at irregular interval but most frequently and changes multiple
> times in an hour.
> Latency is so high (e.g. 140308) that it results with response code  502.
> Here 99% of the latency time is UNTRACED time on platform.
> At the moment the problem starts, latency / untraced time goes on
> increasing with each request until the platform comes to the normal
> behaviour.
>
>
> Now since it is common behaviour -
>
> Very high latency and most frequently.
> 502 response code.
> Untraced time is close to latency.
>
> So we conclude that there is nothing wrong with the code since the full
> latency is UNTRACED time and response code is 502. This is the common
> behaviour for all the requests that suffered.
>
> It proves to be a critical platform issue, at least with our app.
> Pls look into it.
>
> Here are few request/log for your reference -
>
> Gae/request_log_id
>
> 57eea31500ff0d8f062fcbf95d0001737e62616c616a6979617472616669
> 6e6465720001362d342d36370001012f
>
> 57eea30900ff0e2c2c75100fa1737e62616c616a6979617472616669
> 6e6465720001362d342d363700010138
>
> 57eea2f500ff04af2e506cdb530001737e62616c616a6979617472616669
> 6e6465720001362d342d36370001011d
>
> 57eea44700ff072044473595e20001737e62616c616a6979617472616669
> 6e6465720001362d342d363700010145
>
> 57ee7a3000ff08a4e1abebdb3b0001737e62616c616a6979617472616669
> 6e6465720001362d342d363700010104
>
> 57ee7a0d00ff055faed4696a470001737e62616c616a6979617472616669
> 6e6465720001362d342d363700010140
>
>
>
> Regards
> Tech team
>
> On Thu, Sep 22, 2016 at 5:22 AM, 'Nick (Cloud Platform Support)' via
> Google App Engine  wrote:
>
>> Hey Deepak,
>>
>> Since latency is the amount of time requests take to process and return
>> their response, it appears that you have high latency occurring in short
>> time periods fairly regularly. You can check the logs in those time periods
>> (also, observe the latency graph over a smaller time-frame to get a more
>> accurate determination of what that time period is), and see what kind of
>> requests they are. The latency could depend on many factors, but most
>> likely it depends on the code which is running inside the request handler.
>> Is it waiting synchronously on a network call which itself has high
>> latency? Is it fetching a lot of data? Is it running a very intensive
>> computation? Etc.
>>
>> I hope this helps get you started on looking into the latency. Let me
>> know if you have any further questions, as I'll be happy to help!
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>>
>> On Sunday, September 18, 2016 at 12:03:07 PM UTC-4, Deepak Singh wrote:
>>>
>>> PFA the attached graph for our latencyon dashboard (Java flex env).
>>> What should we conclude based on this data ?
>>>
>>> --
>>> Tech team
>>>
>> --
>> 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 google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/google-appengine/a04aa159-97e3-4005-b39c-3d5b39b670cb%
>> 40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Deepak Singh
>



-- 
Deepak Singh

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAF6cnzaKYAtZjZ5yPsvoL%2BXrHN2J6U9z4nM3VsR_%3DVU37D0Kpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: latency started spiking up dramatically today

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Wenzhe,

Apologies for not including this in my last message, as I had believed your 
original message included the necessary information. Can you email me your 
project ID directly at pay...@google.com? I'll be glad to take a look for 
you after that. Is this still occurring, by the way?

Regards,

Nick
Cloud Platform Community Support

On Monday, October 3, 2016 at 10:37:33 AM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Hey Wenzhe, 
>
> We have no incidents reported on the Cloud Status Dashboard 
>  for Datastore as of this moment. 
> Sometimes performance may degrade for a short period of time dependent on 
> Data-Center conditions. You should check out SLA on Datastore 
>  and consider implementing some 
> exponential back-off logic in your code to handle the possibility of 
> deadline exceeded errors. We have a document on this topic titled "Dealing 
> with DeadlineExceededErrors 
> ".
>
> I'll check to see if I can find any other explanation and will report back 
> to this thread. 
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, September 29, 2016 at 8:27:28 PM UTC-4, Wenzhe Gao wrote:
>>
>> Hi,
>>
>> Our app has been running fine with low latency for months now. Latency 
>> started spiking up dramatically at around 6:50am this morning. No real 
>> changes on our side. I see quite a few datastore RPC deadline exceeded 
>> errors in the logs. Ex:
>>
>> ...
>> rpc = datastore_rpc.MultiRpc.wait_any(self.rpcs) DeadlineExceededError: 
>> The overall deadline for responding to the HTTP request was exceeded.
>>
>> See latency graph attached for reference. Any ideas what's going on?
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7e410af0-6a68-4c23-b875-ba07b159f518%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: latency started spiking up dramatically today

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Wenzhe, 

We have no incidents reported on the Cloud Status Dashboard 
 for Datastore as of this moment. 
Sometimes performance may degrade for a short period of time dependent on 
Data-Center conditions. You should check out SLA on Datastore 
 and consider implementing some 
exponential back-off logic in your code to handle the possibility of 
deadline exceeded errors. We have a document on this topic titled "Dealing 
with DeadlineExceededErrors 
".

I'll check to see if I can find any other explanation and will report back 
to this thread. 

Cheers,

Nick
Cloud Platform Community Support

On Thursday, September 29, 2016 at 8:27:28 PM UTC-4, Wenzhe Gao wrote:
>
> Hi,
>
> Our app has been running fine with low latency for months now. Latency 
> started spiking up dramatically at around 6:50am this morning. No real 
> changes on our side. I see quite a few datastore RPC deadline exceeded 
> errors in the logs. Ex:
>
> ...
> rpc = datastore_rpc.MultiRpc.wait_any(self.rpcs) DeadlineExceededError: 
> The overall deadline for responding to the HTTP request was exceeded.
>
> See latency graph attached for reference. Any ideas what's going on?
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/da6620fb-81b8-4472-92de-6f2496c8a7e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Deploy application :Error Response: [13] Timed out when starting VMs.

[Diego Molteni]

HI Nick,
These are the error that I received when i try to upload the application:


08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project 
with:
08:58:55.000
npm ERR! npm run tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2viewer@1.0.0 prestart script 'npm run tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! Exit status 1
08:58:55.000
npm ERR! a2viewer@1.0.0 prestart: `npm run tsc`
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project 
with:
08:58:55.000
npm ERR! tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2viewer@1.0.0 tsc script 'tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! spawn ENOENT
08:58:55.000
npm ERR! a2viewer@1.0.0 tsc: `tsc`
08:58:55.000
npm ERR! syscall spawn
08:58:55.000
npm ERR! errno ENOENT
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! file sh
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "run" "tsc"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
sh: 1: tsc: not found
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project 
with:
08:58:55.000
npm ERR! npm run tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2viewer@1.0.0 prestart script 'npm run tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! Exit status 1
08:58:55.000
npm ERR! a2viewer@1.0.0 prestart: `npm run tsc`
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! npm v3.10.3
08:58:55.000
npm ERR! node v6.7.0
08:58:55.000
npm ERR! argv "/nodejs/bin/node" "/nodejs/bin/npm" "start"
08:58:55.000
npm ERR! Linux 3.16.0-4-amd64
08:58:55.000
08:58:55.000
npm ERR! /app/npm-debug.log
08:58:55.000
npm ERR! Please include the following file with any support request:
08:58:55.000
08:58:55.000
npm ERR! There is likely additional logging output above.
08:58:55.000
npm ERR! npm owner ls a2viewer
08:58:55.000
npm ERR! Or if that isn't available, you can get their info via:
08:58:55.000
npm ERR! npm bugs a2viewer
08:58:55.000
npm ERR! You can get information on how to open an issue for this project 
with:
08:58:55.000
npm ERR! tsc
08:58:55.000
npm ERR! Tell the author that this fails on your system:
08:58:55.000
npm ERR! not with npm itself.
08:58:55.000
npm ERR! If you do, this is most likely a problem with the a2viewer package,
08:58:55.000
npm ERR! Make sure you have the latest version of node.js and npm installed.
08:58:55.000
npm ERR! Failed at the a2viewer@1.0.0 tsc script 'tsc'.
08:58:55.000
npm ERR!
08:58:55.000
npm ERR! spawn ENOENT
08:58:55.000
npm ERR! a2viewer@1.0.0 tsc: `tsc`
08:58:55.000
npm ERR! syscall spawn
08:58:55.000
npm ERR! errno ENOENT
08:58:55.000
npm ERR! code ELIFECYCLE
08:58:55.000
npm ERR! file sh
08:58:55.000
npm ERR! npm v3.10.3

[google-appengine] Re: AttributeError: 'module' object has no attribute 'SignedJwtAssertionCredentials' with App Engine + Earth Engine API python

[Michael Johansson]

I have now tried the example in a Linux environment (Ubuntu 16.04.1 LTS).
After installing all required prerequisites to just get the environment up 
and running, I ran the build.sh and the examples ran pretty smoothly 
thereafter. This does tell me that something in the Earth Engine API as of 
now is not really working well in windows, or at least is a bit convoluted 
to get running.

I did discuss the issue on the GIT repository issue tracker but didn't 
really get closer to a solution. 
I will post about this in the Earth Engine Developers group.

//Best regards
Michael

On Friday, September 23, 2016 at 3:52:50 PM UTC+2, Michael Johansson wrote:
>
> Thank you for the reply. I will file an issue there and keep you updated 
> with what I find out or learn.
>
> I also tried another server example 
> , 
> I got the exact same error. Since I am using the same earth engine library, 
> it might be an issue with that API. When I know more I will post in the 
> earth engine developers forum as well.
> Because as of now I feel that I am guessing a lot :)
>
> During the weekend I will also try to run the examples in a linux 
> environment, if it is a Earth engine API issue, I guess it might not work 
> there as well.
>
> Best regards
> //Michael
>
>
>
> On Friday, September 23, 2016 at 1:49:02 AM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Michael,
>>
>> It appears you found an issue in the "trendy lights" demo. You should 
>> file an issue on the github repo and link this thread for context. It seems 
>> you did indeed find the source of the issue in the changed name of the 
>> function.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Wednesday, September 21, 2016 at 10:05:44 AM UTC-4, Michael Johansson 
>> wrote:
>>>
>>> *Update:*
>>> This seems to be an issue with how the authentication is done in the 
>>> example. It seems that it has changed since the example was written.
>>>
>>> As a newcomer to the App engine, this is pretty confusing to wrap my 
>>> head around. 
>>> Maybe it is really simple. I have at least been trying to figure out how 
>>> I can change the code in _helpers.py
>>> But instead of :
>>> AttributeError: 'module' object has no attribute 
>>> 'SignedJwtAssertionCredentials'
>>> I get: 
>>> AttributeError: 'module' object has no attribute 
>>> 'ServiceAccountCredentials'
>>>
>>> What I changed was: 
>>>  if key_file:
>>> key_data = open(key_file, 'rb').read()
>>>   return oauth2client.ServiceAccountCredentials(
>>>   email, key_data, oauth.SCOPE)
>>>
>>> Before it was:
>>>   
>>>   if key_file:
>>> key_data = open(key_file, 'rb').read()
>>>   return oauth2client.client.SignedJwtAssertionCredentials(
>>> email, key_data, oauth.SCOPE)
>>>
>>> I was trying to follow recommendations from this 
>>> 
>>>  
>>> on github 
>>> I've also been trying to understand the changes as they are explained 
>>> here: https://github.com/google/oauth2client/issues/401
>>>
>>> Maybe I'm way off here and the change is a pretty naive try to solve 
>>> this...
>>>
>>> //Michael
>>>
>>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b7977bfe-e2a0-4b8e-9b0b-986833fb0bca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Deferred tasks in flexible environment

[Randy Sugianto]

I already solved it.

This is because the flexible environment does not support

builtins:
- deferred: on

on app.yaml.

You should mention this on the migration document or emit an error when
deploying. This is a really bad experience for those migrating with the
lack of proper documentation on this.

On Mon, Oct 3, 2016, 04:30 'Adam (Cloud Platform Support)' via Google App
Engine  wrote:

> Could you post an example app.yaml that shows your configuration? Also, if
> you are using 'google.appengine.ext.deferred.defer' to spawn your tasks,
> have you tested using the App Engine Task Queue API
>  directly?
>
>
> On Wednesday, September 28, 2016 at 1:41:56 PM UTC-4, Randy Sugianto wrote:
>
>
> Since I switched my App Engine app to a flexible environment, it seems
> that all tasks failed to run. I was surprised that all tasks failed. But
> when I open the logs, I got only this:
>
> 01:33:56.026POST500167 B4 msAppEngine-Google; (+
> http://code.google.com/appengine)/_ah/queue/deferred
>
> The status code is 500, but when I expand it, there is only this
> information inside:
>
> 0.1.0.2 - - [29/Sep/2016:01:33:56 +0800] "POST /_ah/queue/deferred
> HTTP/1.1" 500 167
> http://0.xxx.module-sync.x.appspot.com/_ah/background
> "AppEngine-Google; (+http://code.google.com/appengine)" "
> module-sync.xx.appspot.com" ms=4 cpu_ms=0 cpm_usd=1.8663e-8
> loading_request=0 instance=- app_engine_release=1.9.45 trace_id=-
> {
> metadata: {…}
> protoPayload: {…}
> insertId: "2016-09-28|10:34:00.180396-07|10.106.31.139|1292268011"
> log: "appengine.googleapis.com/request_log"
> httpRequest: {…}
> operation: {…}
> }
> There is no exception or stack trace or anything else that I usually see
> when I was using the standard environment.
>
> How can I troubleshoot this? Why are my deferred tasks not run?
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/03062645-dc70-4c82-9907-5bcb2098e67f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAE9VMVc6D1Z-RxbcEEoCRHr7NyA-AUjTJKUc6S3H60efc9MNiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.