[google-appengine] Re: Google App Engine Unstable

['Adam Meyer' via Google App Engine]

I'm experiencing issues with Google App Engine this morning too.  Requests 
are spinning for 5+ mins, then the next request goes through fine.  Please 
investigate.

On Friday, December 10, 2021 at 2:00:25 PM UTC-5 Elliott (Cloud Platform 
Support) wrote:

> Hello,
>
> I understand that you would like to report downtime and instability in 
> your App Engine application. Please note that you may follow all outages or 
> infrastructure issues using the Google Cloud Dashboard 
> [1]. Looking at it briefly, I am unable 
> to find issues related to App Engine for Friday.
>
> Google Groups is meant for general discussions and opinions about Google 
> products. In this case, I would suggest reaching out to our regular 
> support channel [2] to report 
> instabilities related to your App Engine instance.
>
> If you would like to report a general issue related to our products, I 
> encourage you to use Google Issue Tracker 
> [3], which we will 
> investigate.
>
> [1] https://status.cloud.google.com/
>
> [2] https://cloud.google.com/support/docs
> [3] https://cloud.google.com/support/docs/issue-trackers
>
> On Friday, December 10, 2021 at 11:20:48 AM UTC-5 ime...@gmail.com wrote:
>
>> Hi, has anyone experienced downtimes and instability of their app engines 
>> web applications and endpoints, this Friday morning? I haven't had and 
>> issue since July 2nd 2019.
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fcdf0770-b39d-4942-a843-d1c2f49859d1n%40googlegroups.com.

Re: [google-appengine] App engine sub domain SSL not working

[Adam Jack]

H, sorry ... looking closer, your screenshot is the screen I was
showing you.

The more I poke about the more I see the same stuff you are showing.

That said, I don't have the wildcard pattern you seem to have at the end of
the dispatch.yaml. I have nothing for the default service.

Sorry I couldn't help.

regards

Adam

On Thu, Sep 16, 2021 at 8:22 PM Adam Jack  wrote:

> I'm no expert, but I did find instructions on how to set it up [I forget
> where] but I think you (at least) need to go here (after DNS is set up) and
> see the "SSL security"
>
>https://console.cloud.google.com/appengine/settings/domains?project=
> ...
>
> ... mine says "Google-managed, auto-renewing".
>
> regards
>
> Adam
>
> On Thu, Sep 16, 2021 at 8:46 AM Alexander Crosson 
> wrote:
>
>> Hi,
>>
>> I'm trying to get my app to run on app engine with subdomains for the
>> frontend and backend services. I'm able to get my apps to run at their app
>> spot URL https://dev-api-dot-.ue.r.appspot.com , but when
>> i try hitting https://dev.api..com I get "This site can’t
>> provide a secure connection", meaning the SSL cert handshake doesn't pass.
>> Can someone please suggest how to fix this? I've search all over the
>> internet but cannot find a solution.
>>
>> Here is the *dispatch.yaml* file
>> dispatch:
>> - url: "dev.app..com/*"
>>   service: dev-app
>> - url: "dev.api..com/*"
>>   service: dev-api
>> - url: "*/.*"
>>   service: default
>>
>> Here is the dev-api.yaml:
>> service: dev-api
>> runtime: nodejs16
>>
>> inbound_services:
>> - warmup
>> automatic_scaling:
>> max_instances: 1
>> resources:
>> cpu: 1
>> memory_gb: 0.5
>> disk_size_gb: 10
>> handlers:
>> - url: /.*
>> secure: always
>> redirect_http_response_code: 301
>> script: auto
>>
>>
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/fb7ad98b-3989-4df7-b648-9a8102711624n%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-appengine/fb7ad98b-3989-4df7-b648-9a8102711624n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Responserack
> - incidents happen, response is crafted...
> https://www.responserack.com
> (720) 340-2048 <720-340-2048> | LinkedIn
> <https://www.linkedin.com/company/responserack> | Facebook
> <https://facebook.com/Responserack> | Twitter
> <https://twitter.com/Responserack> | Capterra
> <https://www.capterra.com/p/234883/Responserack/>
>


-- 
Responserack
- incidents happen, response is crafted...
https://www.responserack.com
(720) 340-2048 <720-340-2048> | LinkedIn
<https://www.linkedin.com/company/responserack> | Facebook
<https://facebook.com/Responserack> | Twitter
<https://twitter.com/Responserack> | Capterra
<https://www.capterra.com/p/234883/Responserack/>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAMT-FFL2a-%3DDtUNeGrY%3DHTrju8%3DnH2sz_sog2viFD1CwasZBRg%40mail.gmail.com.

Re: [google-appengine] App engine sub domain SSL not working

[Adam Jack]

I'm no expert, but I did find instructions on how to set it up [I forget
where] but I think you (at least) need to go here (after DNS is set up) and
see the "SSL security"

   https://console.cloud.google.com/appengine/settings/domains?project= ...

... mine says "Google-managed, auto-renewing".

regards

Adam

On Thu, Sep 16, 2021 at 8:46 AM Alexander Crosson 
wrote:

> Hi,
>
> I'm trying to get my app to run on app engine with subdomains for the
> frontend and backend services. I'm able to get my apps to run at their app
> spot URL https://dev-api-dot-.ue.r.appspot.com , but when i
> try hitting https://dev.api..com I get "This site can’t provide a
> secure connection", meaning the SSL cert handshake doesn't pass. Can
> someone please suggest how to fix this? I've search all over the internet
> but cannot find a solution.
>
> Here is the *dispatch.yaml* file
> dispatch:
> - url: "dev.app..com/*"
>   service: dev-app
> - url: "dev.api..com/*"
>   service: dev-api
> - url: "*/.*"
>   service: default
>
> Here is the dev-api.yaml:
> service: dev-api
> runtime: nodejs16
>
> inbound_services:
> - warmup
> automatic_scaling:
> max_instances: 1
> resources:
> cpu: 1
> memory_gb: 0.5
> disk_size_gb: 10
> handlers:
> - url: /.*
> secure: always
> redirect_http_response_code: 301
> script: auto
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/fb7ad98b-3989-4df7-b648-9a8102711624n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/fb7ad98b-3989-4df7-b648-9a8102711624n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
Responserack
- incidents happen, response is crafted...
https://www.responserack.com
(720) 340-2048 <720-340-2048> | LinkedIn
<https://www.linkedin.com/company/responserack> | Facebook
<https://facebook.com/Responserack> | Twitter
<https://twitter.com/Responserack> | Capterra
<https://www.capterra.com/p/234883/Responserack/>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAMT-FFLVmTzrbSgvb37c18Eis9kMU86uasD%3DY%2BEGMTDrEk857g%40mail.gmail.com.

Re: [google-appengine] gcloud deployment error

[Adam Jack]

It says;

   No space left on device

... has your project been growing for 7 years?

regards,

Adam

On Tue, Dec 1, 2020 at 4:11 PM José Antonio Sánchez Ortiz <
jasof...@gmail.com> wrote:

> Hi, from six hours ago i´m getting:
>
> gcloud --quiet --project $PROJECT_ID_PRODUCTION app deploy
> app-default.yaml --version=$CI_COMMIT_SHORT_SHA
> Services to deploy:
> descriptor: [/builds/SFALC/gymup-web-app/app-default.yaml]
> source: [/builds/SFALC/gymup-web-app]
> target project: [xxx]
> target service: [default]
> target version: [f04afaed]
> target url: [http://xx.ew.r.appspot.com]
> Beginning deployment of service [default]...
> Building and pushing image for service [default]
> ERROR: gcloud crashed (IOError): [Errno 28] No space left on device
>
> Several years deploying this project and this is the first time we get
> this error
>
> Thanks in advance
>
> José Antonio Sánchez Ortiz
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/6c7e48b2-4848-4307-ab35-bf437996ac46n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/6c7e48b2-4848-4307-ab35-bf437996ac46n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
Responserack
- incidents happen, response is crafted...
https://www.responserack.com | LinkedIn
<https://www.linkedin.com/company/responserack> | Facebook
<https://facebook.com/Responserack> | Twitter
<https://twitter.com/Responserack>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAMT-FFKfy_eMOkabPssbQzuy7k%3DtOgJu3y5BxyJWbDqD%2BjUbog%40mail.gmail.com.

Re: [google-appengine] Re: GAE Web app sending mail using SendGrid

[Adam Jack]

I don't know the background here, but in case any of this helps:

Do you have an API key from SendGrid?

   https://app.sendgrid.com/settings/api_keys

In your appengine-web.xml  set the environment variable to pass that API
key into:


  




https://cloud.google.com/appengine/docs/standard/java/config/appref


Sorry if I am off base, it just looks similar to what I am doing (with Go.)


regards,

Adam

On Wed, Jul 15, 2020 at 6:20 AM Alexis CAPGEMINI <
alexis.capgem...@radiall.com> wrote:

> Can you please explain how you did this ?
>
> I'm still stuck with an error here :  SendGrid sendgrid = new
> SendGrid( System.getenv("SENDGRID_SENDER"));
>
> Thanks
>
> Le vendredi 7 septembre 2018 à 18:02:44 UTC+2, rashmi...@gmail.com a
> écrit :
>
>> I have solved the problem. I had to use Urlfetch configuration in
>> appengine-web.xml and use URLFetch class instead of HttpURLConnection. It
>> works now. Thanks for the help!
>>
>>
>> On Saturday, August 25, 2018 at 1:08:16 AM UTC+5:30, George (Cloud
>> Platform Support) wrote:
>>>
>>> If you would like us to look more in-depth in the issue, you should
>>> write a private message with your project ID. You can do this using the
>>> drop-down menu of the reply button, at the top-right of the message window.
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/21e0c86a-886a-491b-a57d-cd4d72b4e02cn%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/21e0c86a-886a-491b-a57d-cd4d72b4e02cn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
Responserack
- incidents happen, response is crafted...
https://www.responserack.com | LinkedIn
<https://www.linkedin.com/company/responserack> | Facebook
<https://facebook.com/Responserack> | Twitter
<https://twitter.com/Responserack>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAMT-FFKdRnu8Ajr5CrdCXCYf9Uk-OsecionwZfcP2NBRLnj1_Q%40mail.gmail.com.

[google-appengine] Re: Migrating from Go on GAE to Go on GAE using Google App Engine Go library...

[Adam Jack]

For completeness, as I wandered in the wilderness confused I stumbled upon 
this:

  
 
https://cloud.google.com/appengine/docs/standard/go/go-differences#migrating-appengine-sdk

... and I believe the answer to my question is *don't* do what I was 
attempting, instead skip the Google App Engine SDK (as a thing of the past) 
and go to Google Cloud APIs.

regards

Adam

On Saturday, June 27, 2020 at 6:33:24 PM UTC-6 Adam Jack wrote:

> Hello,
>
> I've been using GAE for a number of months running a go webapp (pretty 
> vanilla HTTP with a Gorilla MUX.) It has been working well. I've recently 
> started to want to access some of the GAE services and so am trying to 
> start to use the GAE go library. I also want to be able to develop offline 
> ('cos I often work where networks are poor.)
>
> I cannot seem to get my head around reworking my environment to succeed. 
> When I make GAE calls (e.g. to memcache) I get told "not an App Engine 
> context".
>
> I've tried reading documentation and Googling but I cannot seem to find 
> the pattern of setup I am missing, if one exists. Maybe I've painted myself 
> into a corner somehow.
>
> I've tried wrapping/replacing my context.Context via 
> appengine.WithContext, and my HTTP request. That said, I continue to get 
> the same error message.
>
> I tried calling appengine.Main (as some search results suggested) in my 
> main but things just hung badly. I don't know how to refactor to support 
> that entry point, but maybe I need to learn.
>
> Hmmm, reading the code comment inside appengine.Main I see a new path to 
> try, refactor so that when running on GAE the code sets up http handlers 
> (somehow) and dives into appengine.Main, and when not in GAE it runs my own 
> HTTP server. I think I can try that. Does anybody know of a code example I 
> can see to emulate?
>
> Further question ... once I am, in appengine.Main will all contexts I get 
> (from the HTTP requests) be ok for me to with.Context wrapper, to store my 
> own values? (I've read some older postings that this breaks the appengine 
> context.)
>
> Any pointers would be really helpful. I've googled and found "Getting 
> Started" and such, and some migration docs, but I'm starting to feel I'm 
> unintentionally following an uncommon path.
>
> BTW: Separately, it seems that memcache works on standard but not flex 
> (hopefully that is correct) which makes me think maybe memcache isn't a 
> good solution for long term. Is it deprecated in favor of something 
> else, or what?
>
> Thanks in advance for any suggestions.
>
> regards,
>
> Adam
> -- 
> Responserack
> - incidents happen, response is crafted...
> https://www.responserack.com | LinkedIn 
> <https://www.linkedin.com/company/responserack> | Facebook 
> <https://facebook.com/Responserack> | Twitter 
> <https://twitter.com/Responserack>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/11d91a40-70ab-43dd-9e91-e7678b404a3fn%40googlegroups.com.

[google-appengine] Migrating from Go on GAE to Go on GAE using Google App Engine Go library...

[Adam Jack]

Hello,

I've been using GAE for a number of months running a go webapp (pretty
vanilla HTTP with a Gorilla MUX.) It has been working well. I've recently
started to want to access some of the GAE services and so am trying to
start to use the GAE go library. I also want to be able to develop offline
('cos I often work where networks are poor.)

I cannot seem to get my head around reworking my environment to succeed.
When I make GAE calls (e.g. to memcache) I get told "not an App Engine
context".

I've tried reading documentation and Googling but I cannot seem to find the
pattern of setup I am missing, if one exists. Maybe I've painted myself
into a corner somehow.

I've tried wrapping/replacing my context.Context via appengine.WithContext,
and my HTTP request. That said, I continue to get the same error message.

I tried calling appengine.Main (as some search results suggested) in my
main but things just hung badly. I don't know how to refactor to support
that entry point, but maybe I need to learn.

Hmmm, reading the code comment inside appengine.Main I see a new path to
try, refactor so that when running on GAE the code sets up http handlers
(somehow) and dives into appengine.Main, and when not in GAE it runs my own
HTTP server. I think I can try that. Does anybody know of a code example I
can see to emulate?

Further question ... once I am, in appengine.Main will all contexts I get
(from the HTTP requests) be ok for me to with.Context wrapper, to store my
own values? (I've read some older postings that this breaks the appengine
context.)

Any pointers would be really helpful. I've googled and found "Getting
Started" and such, and some migration docs, but I'm starting to feel I'm
unintentionally following an uncommon path.

BTW: Separately, it seems that memcache works on standard but not flex
(hopefully that is correct) which makes me think maybe memcache isn't a
good solution for long term. Is it deprecated in favor of something
else, or what?

Thanks in advance for any suggestions.

regards,

Adam
-- 
Responserack
- incidents happen, response is crafted...
https://www.responserack.com | LinkedIn
<https://www.linkedin.com/company/responserack> | Facebook
<https://facebook.com/Responserack> | Twitter
<https://twitter.com/Responserack>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAMT-FFLT0srzczd56LmM_fSMAktDuc8Dj0kRisdvppPrk5mN5g%40mail.gmail.com.

[google-appengine] Re: (gcloud.app.deploy) INVALID_ARGUMENT: The following quotas were exceeded: IN_USE_ADDRESSES (quota: 4, used: 4 + needed: 2)

[Adam Woloszyn]

Hi Amit,
I ran into the same issue. You just need to increase your Quotas for these 
settings. You can find them in your IAM & Admin > Quotas section. Increase 
it to 10 or 12 and you should be able to deploy. I had a few others I had 
to increase as well when I was deploying several services.
Hope this helps -
Adam

On Wednesday, May 6, 2020 at 10:46:04 AM UTC-7, Amit Singh wrote:
>
> Earlier I was unable to deploy project to GCP but today I'm getting stuck 
> with this* (gcloud.app.deploy) INVALID_ARGUMENT: The following quotas 
> were exceeded: IN_USE_ADDRESSES (quota: 4, used: 4 + needed: 2) *error.
> Why this error is coming  while deploying to GCP? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/89c619d9-1d4f-4e03-b4da-fe7e01aab33a%40googlegroups.com.

[google-appengine] Postgres connection string

[Adam Woloszyn]

Greetings,
New to appengine and trying to receive some support regarding my connection 
to a postgres database from a .NET application I'm deploying. Here are some 
details:

App.yaml:
beta_settings:
cloud_sql_instances: "my-project:us-west1:dbName=tcp:5432"

appsettings.json:

"AppDbContext": "Uid=username;Pwd=*;Host=cloudsql;Database=dbName",

Any ideas on what I might be doing wrong? I just get "Exception: Error 
while connecting"

alt-svc: h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; 
ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; 
ma=2592000; v="46,43"  content-type: text/plain; charset=utf-8  date: Mon, 04 
May 2020 16:02:14 GMT  server: Kestrel  status: 400  via: 1.1 google 

Thanks!Adam

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e0ff893d-9af9-49bc-a2ff-46255ab3bf49%40googlegroups.com.

[google-appengine] Creating Cron Job With Kotlin's Ktor

[Adam Hurwitz]

Hi AppEngine Community, 

*Is there a way to run Cron Jobs with Ktor <https://ktor.io/>?*

I'm currently hosting multiple Java *.jar* apps written in Kotlin on 
AppEngine. I'm looking to refactor these apps into *Ktor* apps on AppEngine 
with a Cron Job 
<https://cloud.google.com/appengine/docs/standard/java/config/cron-yaml> for 
scheduled tasks, as the *.jar* apps I've noticed have more issues with 
dependencies. 

I'm looking for Ktor's equivalent to Cloud Functions' built-in 
implementation 
<https://firebase.googleblog.com/2019/04/schedule-cloud-functions-firebase-cron.html>
 for 
Cron Jobs with JavaScript. 

functions.pubsub.schedule

*Back-up option:* If Ktor does not have this feature and I want to keep the 
code in Kotlin, Google has an alpha, Using Kotlin with Google Cloud 
Functions 
<https://github.com/GoogleCloudPlatform/kotlin-samples/tree/master/functions>. 
It appears Kotlin + Cloud Functions' built-in implementation could be used 
with this approach.

Much appreciated!

Adam <https://www.linkedin.com/in/adamshurwitz/>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/94ddc218-ed75-4a52-a3a7-6a4f66b1e5e7%40googlegroups.com.

[google-appengine] Re: Custom Domain much slower than $PROJECT_ID.appspot.com

[Adam Weaver]

Hmmm I dont think it will ever resolve. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2b53133a-0dc2-433b-8343-1440b441fa6e%40googlegroups.com.

Re: [google-appengine] Re: 2nd Gen GAE Python 3.7 memory usage

[Adam Lugowski]

I'm using a Python profiler that appears to report resident size.

I understand what you're saying that there is more to memory usage than 
just the app. But I hope you can understand my frustration: AppEngine 
provides no tooling or metrics to help track down what is the root of a 
problem that is not reproducible anywhere else. Maybe Googlers have some 
internal metrics and/or profiling tools, because clearly the runtime is 
monitoring memory usage.

Even something as simple as a plot of the app's memory usage over time 
would be useful. I can make changes to the app, monitor requests, and see 
which request is causing a spike.

As of now, it looks like I'm just supposed to guess if the issue lies in 
the app, the kernel, memory mappings, or other bits and pieces.

On Thursday, September 20, 2018 at 4:44:46 PM UTC-7, Phillip Pearson wrote:
>
> Hi Adam,
>
> How are you measuring memory usage locally?  If you're looking at the 
> resident size (RSS in ps, RES in top), that's only a subset of the actual 
> memory used by your application, so you should expect the memory usage 
> reported in the App Engine console to be higher than what you see locally 
> -- it includes kernel memory specific to your app, mapped file data, and 
> some other bits and pieces.
>
> As for the entrypoint line, we haven't advertised this usage too widely 
> because we hope the defaults will work for most people -- and just in case 
> we come up with a better way to do it :)
>
> Cheers,
> Phil
>
> On Thu, Sep 20, 2018 at 2:12 PM Adam Lugowski  > wrote:
>
>> Thanks for the suggestions, Phillip.
>>
>> Yes the memory is as expected. This was never in doubt, the out-of-memory 
>> message says both usage and the quota. The quota matches GAE_MEMORY_MB. The 
>> problem is why the usage is so high, not that the quota isn't changing.
>>
>> Thank you for the command to use. Google's docs didn't make it clear that 
>> this is how you control parallelism. After adding gunicorn to 
>> requirements.txt, the following now helps:
>>
>> entrypoint: gunicorn main:app --threads 4 --workers 1 -c 
>> /config/gunicorn.py
>>
>> It only solves half the problem. This now no longer crashes an F4. It 
>> does still crash an F2, with 270 MB usage. Locally it's still only 115MB.
>>
>>
>> On Monday, September 17, 2018 at 1:25:55 PM UTC-7, Phillip Pearson wrote:
>>>
>>> Hi Adam,
>>>
>>> Here's a few ideas for diagnosis:
>>>
>>> 1. Can you try printing or logging repr(os.environ) and checking for the 
>>> GAE_MEMORY_MB environment variable?  I just tried deploying a test app with 
>>> instance_class: F4 and service: xyz, and print(repr(os.environ)) gives me 
>>> something like this:
>>>
>>>   environ({'GAE_MEMORY_MB': '512', 'GAE_INSTANCE': ...etc etc...})
>>>
>>> The python37 runtime *should* start one worker if GAE_MEMORY_MB <= 128, 
>>> two if <= 256, four if <= 512, otherwise eight.
>>>
>>> If you see 'GAE_MEMORY_MB': '512' in there but anything other than four 
>>> workers starting up, I'm extremely interested in figuring out why :)  
>>> Likewise if you see anything other than 512 for an F4 instance.
>>>
>>> 2. Check that you're looking at the logs for the correct service -- make 
>>> sure you see "GAE Application, xyz" and not "GAE Application, Default 
>>> Service" or just "GAE Application" (which combines logs from all services) 
>>> in the logs viewer.
>>>
>>> 3. Once you've done those two, if nothing sticks out, you can manually 
>>> configure the worker count by adding a line like this to app.yaml:
>>>
>>>   entrypoint: gunicorn main:app --workers 2 -c /config/gunicorn.py
>>>
>>> This will start up two workers.  You can also configure the number of 
>>> threads per worker:
>>>
>>>   entrypoint: gunicorn main:app --threads 8 --workers 2 -c 
>>> /config/gunicorn.py
>>>
>>> (The default if you just using 'gunicorn main:app -c 
>>> /config/gunicorn.py' is four workers with four threads each.)
>>>
>>> Cheers,
>>> Phil
>>>
>>> On Monday, September 17, 2018 at 10:30:06 AM UTC-7, Adam Lugowski wrote:
>>>>
>>>> Hi Rahul,
>>>>
>>>> I'm not manually configuring workers. Happy to learn of how to do that. 
>>>> My app.yaml is simple:
>>>>
>>>> runtime: python37
>>>> service : xyz
>>>>
>>>> inbound_services:
>>>> - warmup
>>>>
>>>> insta

[google-appengine] Re: 2nd Gen GAE Python 3.7 memory usage

[Adam Lugowski]

Thanks for the suggestions, Phillip.

Yes the memory is as expected. This was never in doubt, the out-of-memory 
message says both usage and the quota. The quota matches GAE_MEMORY_MB. The 
problem is why the usage is so high, not that the quota isn't changing.

Thank you for the command to use. Google's docs didn't make it clear that 
this is how you control parallelism. After adding gunicorn to 
requirements.txt, the following now helps:

entrypoint: gunicorn main:app --threads 4 --workers 1 -c /config/gunicorn.py

It only solves half the problem. This now no longer crashes an F4. It does 
still crash an F2, with 270 MB usage. Locally it's still only 115MB.


On Monday, September 17, 2018 at 1:25:55 PM UTC-7, Phillip Pearson wrote:
>
> Hi Adam,
>
> Here's a few ideas for diagnosis:
>
> 1. Can you try printing or logging repr(os.environ) and checking for the 
> GAE_MEMORY_MB environment variable?  I just tried deploying a test app with 
> instance_class: F4 and service: xyz, and print(repr(os.environ)) gives me 
> something like this:
>
>   environ({'GAE_MEMORY_MB': '512', 'GAE_INSTANCE': ...etc etc...})
>
> The python37 runtime *should* start one worker if GAE_MEMORY_MB <= 128, 
> two if <= 256, four if <= 512, otherwise eight.
>
> If you see 'GAE_MEMORY_MB': '512' in there but anything other than four 
> workers starting up, I'm extremely interested in figuring out why :)  
> Likewise if you see anything other than 512 for an F4 instance.
>
> 2. Check that you're looking at the logs for the correct service -- make 
> sure you see "GAE Application, xyz" and not "GAE Application, Default 
> Service" or just "GAE Application" (which combines logs from all services) 
> in the logs viewer.
>
> 3. Once you've done those two, if nothing sticks out, you can manually 
> configure the worker count by adding a line like this to app.yaml:
>
>   entrypoint: gunicorn main:app --workers 2 -c /config/gunicorn.py
>
> This will start up two workers.  You can also configure the number of 
> threads per worker:
>
>   entrypoint: gunicorn main:app --threads 8 --workers 2 -c 
> /config/gunicorn.py
>
> (The default if you just using 'gunicorn main:app -c /config/gunicorn.py' 
> is four workers with four threads each.)
>
> Cheers,
> Phil
>
> On Monday, September 17, 2018 at 10:30:06 AM UTC-7, Adam Lugowski wrote:
>>
>> Hi Rahul,
>>
>> I'm not manually configuring workers. Happy to learn of how to do that. 
>> My app.yaml is simple:
>>
>> runtime: python37
>> service : xyz
>>
>> inbound_services:
>> - warmup
>>
>> instance_class: F4
>>
>> handlers:
>> 
>>
>> On Sunday, September 16, 2018 at 6:59:38 AM UTC-7, rah...@google.com 
>> wrote:
>>>
>>> Hello Adam,
>>>   Could you paste your app.yaml? Are you explicitly configuring the 
>>> number of workers?
>>> Thanks,
>>> ~Rahul.
>>>
>>>
>>> On Friday, September 14, 2018 at 3:47:41 PM UTC-7, Adam Lugowski wrote:
>>>>
>>>> The only theory I have is informed by these log messages on startup:
>>>>
>>>> A  [2018-09-14 19:28:38 +] [1] [INFO] Starting gunicorn 19.9.0 
>>>> A  [2018-09-14 19:28:38 +] [1] [INFO] Listening at: 
>>>> http://0.0.0.0:8080 (1) 
>>>> A  [2018-09-14 19:28:38 +] [1] [INFO] Using worker: threads 
>>>> A  [2018-09-14 19:28:38 +] [8] [INFO] Booting worker with pid: 8 
>>>> A  [2018-09-14 19:28:38 +] [9] [INFO] Booting worker with pid: 9 
>>>> A  [2018-09-14 19:28:38 +] [10] [INFO] Booting worker with pid: 10 
>>>> A  [2018-09-14 19:28:38 +] [11] [INFO] Booting worker with pid: 11 
>>>> A  [2018-09-14 19:28:38 +] [12] [INFO] Booting worker with pid: 12 
>>>> A  [2018-09-14 19:28:38 +] [13] [INFO] Booting worker with pid: 13 
>>>> A  [2018-09-14 19:28:39 +] [14] [INFO] Booting worker with pid: 14 
>>>> A  [2018-09-14 19:28:39 +] [15] [INFO] Booting worker with pid: 15 
>>>>
>>>>
>>>> It looks like multiple workers are started, so maybe the fixed memory 
>>>> overhead is just duplicated by each worker.
>>>> This is also supported by the fact that some of my requests load 
>>>> matplotlib. Locally this makes a slow first request then fast on 
>>>> subsequent 
>>>> ones. On GAE F4 the first few are slow, then it stays fast, as if multiple 
>>>> processes have to be warmed up.
>>>> If this is true, then going to a larger instance is poor advice; 
>>>> doubl

[google-appengine] Re: 2nd Gen GAE Python 3.7 memory usage

[Adam Lugowski]

Hi Rahul,

I'm not manually configuring workers. Happy to learn of how to do that. My 
app.yaml is simple:

runtime: python37
service : xyz

inbound_services:
- warmup

instance_class: F4

handlers:


On Sunday, September 16, 2018 at 6:59:38 AM UTC-7, rah...@google.com wrote:
>
> Hello Adam,
>   Could you paste your app.yaml? Are you explicitly configuring the number 
> of workers?
> Thanks,
> ~Rahul.
>
>
> On Friday, September 14, 2018 at 3:47:41 PM UTC-7, Adam Lugowski wrote:
>>
>> The only theory I have is informed by these log messages on startup:
>>
>> A  [2018-09-14 19:28:38 +] [1] [INFO] Starting gunicorn 19.9.0 
>> A  [2018-09-14 19:28:38 +] [1] [INFO] Listening at: 
>> http://0.0.0.0:8080 (1) 
>> A  [2018-09-14 19:28:38 +] [1] [INFO] Using worker: threads 
>> A  [2018-09-14 19:28:38 +] [8] [INFO] Booting worker with pid: 8 
>> A  [2018-09-14 19:28:38 +] [9] [INFO] Booting worker with pid: 9 
>> A  [2018-09-14 19:28:38 +] [10] [INFO] Booting worker with pid: 10 
>> A  [2018-09-14 19:28:38 +] [11] [INFO] Booting worker with pid: 11 
>> A  [2018-09-14 19:28:38 +] [12] [INFO] Booting worker with pid: 12 
>> A  [2018-09-14 19:28:38 +] [13] [INFO] Booting worker with pid: 13 
>> A  [2018-09-14 19:28:39 +] [14] [INFO] Booting worker with pid: 14 
>> A  [2018-09-14 19:28:39 +] [15] [INFO] Booting worker with pid: 15 
>>
>>
>> It looks like multiple workers are started, so maybe the fixed memory 
>> overhead is just duplicated by each worker.
>> This is also supported by the fact that some of my requests load 
>> matplotlib. Locally this makes a slow first request then fast on subsequent 
>> ones. On GAE F4 the first few are slow, then it stays fast, as if multiple 
>> processes have to be warmed up.
>> If this is true, then going to a larger instance is poor advice; doubling 
>> memory size also doubles CPU count which doubles fixed overhead and we're 
>> back at square one.
>>
>

-- 
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/5551f47a-a195-42bf-ae2f-ed5bb868c3e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Up-to-date pip with AppEngine Python 3.6 flex env?

[Adam Lugowski]

Great, thank you!

It seems like it should be as easy as adding a `pip install --upgrade pip` 
line to the container construction mechanism they're using, so I hope they 
decide to add the feature.

I guess for today, though, I'll have to go to a custom environment.

On Friday, September 14, 2018 at 5:39:16 PM UTC-7, George (Cloud Platform 
Support) wrote:
>
> Hello Adam, 
>
> Developers are aware of this feature request, and they are going to 
> evaluate its merit and decide on possible implementation. 
>

-- 
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/9f70a52f-7083-4650-b6c2-750a05bf7bbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 2nd Gen GAE Python 3.7 memory usage

[Adam Lugowski]

The only theory I have is informed by these log messages on startup:

A  [2018-09-14 19:28:38 +] [1] [INFO] Starting gunicorn 19.9.0 
A  [2018-09-14 19:28:38 +] [1] [INFO] Listening at: http://0.0.0.0:8080 
(1) 
A  [2018-09-14 19:28:38 +] [1] [INFO] Using worker: threads 
A  [2018-09-14 19:28:38 +] [8] [INFO] Booting worker with pid: 8 
A  [2018-09-14 19:28:38 +] [9] [INFO] Booting worker with pid: 9 
A  [2018-09-14 19:28:38 +] [10] [INFO] Booting worker with pid: 10 
A  [2018-09-14 19:28:38 +] [11] [INFO] Booting worker with pid: 11 
A  [2018-09-14 19:28:38 +] [12] [INFO] Booting worker with pid: 12 
A  [2018-09-14 19:28:38 +] [13] [INFO] Booting worker with pid: 13 
A  [2018-09-14 19:28:39 +] [14] [INFO] Booting worker with pid: 14 
A  [2018-09-14 19:28:39 +] [15] [INFO] Booting worker with pid: 15 


It looks like multiple workers are started, so maybe the fixed memory 
overhead is just duplicated by each worker.
This is also supported by the fact that some of my requests load 
matplotlib. Locally this makes a slow first request then fast on subsequent 
ones. On GAE F4 the first few are slow, then it stays fast, as if multiple 
processes have to be warmed up.
If this is true, then going to a larger instance is poor advice; doubling 
memory size also doubles CPU count which doubles fixed overhead and we're 
back at square one.

-- 
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/6a3b7259-1ea8-42f6-bb38-97e78260018d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] 2nd Gen GAE Python 3.7 memory usage

[Adam Lugowski]

I have an app that works well in the python37 runtime.

However I keep running into memory usage problems. When I profiled my app 
running locally it uses about 115 MB and usage remains flat when processing 
requests. On the F1 instance I can understand that individual requests 
could bump over 128 MB. However, going up instance tiers doesn't help. Even 
F4 runs out of memory at nearly the same rate as F1, even though local 
profiling shows memory usage should never be anywhere near as high as 
AppEngine reports in its log message.

I have two questions:
 - How do I profile my AppEngine app so I can find out what is eating 
memory? Local profiling apparently has little relation to what happens on 
AppEngine.
 - Why does using a larger instance not 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/6d6994c0-1f8c-4dd7-a132-a248369d8ffc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Up-to-date pip with AppEngine Python 3.6 flex env?

[Adam Lugowski]

 

I want to move an app from the Python 3.7 standard environment to the 
Python 3.6 flex environment.


Python 3.7 comes with pip 18, Python 3.6 comes with pip 9. Pip 10 
introduced a very useful feature, build dependencies. Many analytics 
packages need this to work, otherwise you have to install build 
dependencies like Cython manually in a separate step. That is obviously a 
non-starter in GAE.


Outside of GAE the solution is pip install --upgrade pip.


Is it possible to have the Python 3.6 environment update its pip before it 
runs pip install -r requirements.txt?


Adding pip to requirements.txt has no effect.

-- 
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/3b8f76cc-c41f-4573-9668-da75d4f04344%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] help with finding something that was in my virgin mobile phone cloud . m

[Adam Weaver]

my phone broke and i desperately need information that was on my cloud but 
I dont know how to find it  can some one help me pls



-- 
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/ca1f7703-8380-4ecf-8be5-ec36413c5199%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE / Datastore issues right now?

[Adam Wilson]

I have been experiencing App Engine and Datastore issues since 12:50 MST. 
Go runtime.

On Thursday, February 15, 2018 at 1:07:48 PM UTC-7, Thanasis Delenikas 
wrote:
>
> Is anybody else experiencing issues with GAE (Java) in the last 10 minutes 
> or so?
>
> I see a ridiculous number of ConcurrentModificationException  - my app is 
> almost dead, nothing moves. All datastore ops seem to throw exceptions.
>

-- 
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/a40f8461-bd0c-4fac-a5f6-5a3db72880af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: URGENT: is GAE Standard memcache down????

[Adam Sah]

confirmed - that code is returning False for me too.

On Monday, November 6, 2017 at 1:00:44 PM UTC-8, bFlood wrote:
>
> agreed, memcache is down
>
> On Monday, November 6, 2017 at 3:56:52 PM UTC-5, PK wrote:
>>
>> This started returning False 15 minutes ago. My app is down because of 
>> it. 
>>
>> from google.appengine.api.capabilities import CapabilitySet 
>> print CapabilitySet('memcache', methods=['set']).is_enabled() 
>>
>>
>>
>>

-- 
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/b4870b4f-b28c-43cc-bb96-afdae7a222fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: renewed & installed SSL cert... but GAE still serving old one?

[Adam Sah]

Ssllabs.com is still reporting

Valid from  Tue, 11 Aug 2015 00:00:00 UTC
Valid until Mon, 09 Oct 2017 23:59:59 UTC (expires in 26 days, 5 hours)

Where are you seeing the new certificate?

-- 
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/64377429-bc6c-4bd7-91b6-020fd961c03a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] renewed & installed SSL cert... but GAE still serving old one?

[Adam Sah]

Has anyone else seen this?  I'm nervous that I'll have an emergency outage 
in 30 days...

I've installed new SSL certs and ran the tests.


*installation*

from https://console.cloud.google.com/appengine/settings/certificates

NameExpiration dateMapped domains
Certificate for *..com, .com October 9, 2017 
(none)<== the old certificate
my-cert-1 November 8, 2018 
.com, *. 
<https://console.cloud.google.com/appengine/settings/certificate/52:cc:18:f9:5d:79:96:67:26:62:7c:9d:f5:f4:95:01:c9:c0:9e:f9:02:fa:f3:e2:91:43:54:68:60:78:57:69:4d:f5:e4:5b:68:85:18:68:f5:ad:0b:cc:1a:d5:6c:d1:50:72:5b:1c:86:6c:30:ad:92:ef:21:b0:33:9c:dd:57:cf:d5:b1:41:16:9b:61:5f:f3:14:28:78:2d:1d:a6:39?project=bbf-prod-hrd=default>.com,
 
www..com  <== new certificate


*seen from outside google*

from https://www.ssllabs.com/ssltest/analyze.html   (I waited 48 hours -- 
still showing the old cert, ditto other SSL cert checking services...)

Valid from Tue, 11 Aug 2015 00:00:00 UTC
Valid until Mon, 09 Oct 2017 23:59:59 UTC (expires in 26 days, 7 hours)


*Google's instructions to verify certs*

seen in 
https://cloud.google.com/appengine/docs/standard/python/using-custom-domains-and-ssl#app_engine_support_for_ssl_certificates

Verify your SSL certificate and private key:

   1. 
   
   To verify that the private key and certificate match 
   <http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#verify>, you can use 
   the openssl x509 and openssl rsacommands. Examples:
   
   openssl x509 -noout -modulus -in concat.crt | openssl md5
   openssl rsa -noout -modulus -in myserver.key.pem | openssl md5
   
   Both the openssl x509 
   <https://www.openssl.org/docs/manmaster/man1/x509.html> and openssl rsa 
   <https://www.openssl.org/docs/manmaster/man1/rsa.html> commands should 
   return the same output.
   
$ openssl x509 -noout -modulus -in mycert.crt | openssl md5; openssl rsa 
-noout -modulus -in mycert.key.pem | openssl md5
315a794cca913774a0e8f8...hidden...
315a794cca913774a0e8f8...hidden...


   1. 
   
   To verify that a certificate and its CA chain are valid, you can use the 
openssl 
   verify <https://www.openssl.org/docs/manmaster/man1/verify.html> command. 
   For example:
   
   openssl verify -verbose -CAfile concat.crt concat.crt
   
   
$ cat STAR_mycert.crt AddTrustExternalCARoot.crt  COMODORSAAddTrustCA.crt 
COMODORSADomainValidationSecureServerCA.crt > concat.crt
$ openssl verify -verbose -CAfile concat.crt concat.crt
concat.crt: OK

thanks!
adam

-- 
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/7684148c-0539-4a99-adb0-e3226841e80c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Maven plugins

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

Yes, I should have specified that I meant the project type, not the plugin, 
since CT4E of course allows you to create a Maven-based project as well. 
I'm mostly speaking from personal preference. I like the additional options 
you get with M2Eclipse (like being able to specify a working set), and do 
most command invocation from a terminal. Hot reload also works fine when 
debugging this way with 'Build automatically' enabled in Eclipse, as it 
will replace .class files directly in the target/ directory without needing 
to invoke a Maven build.

Thanks Brian for shedding light on how CT4E handles debugging and 
integration with WTP. My understanding was that the JPDA remote debugger is 
still used under the hood when debugging locally in WTP, but I am nowhere 
near an expert on the Eclipse platform. Is this the case?

On Tuesday, May 9, 2017 at 11:11:00 AM UTC-4, Brian de Alwis wrote:
>
> CT4E offers two styles of App Engine projects for the standard environment:
>
>
> The first one, the *Google App Engine Standard Java Project*, is a 
> "native" WTP-based Eclipse project style.  The *Maven-based Google App 
> Engine Standard Java Project* creates a Maven-based project using the new 
> Maven App Engine plugins.  This Maven project uses M2Eclipse and its 
> accompanying m2e-wtp bindings to integrate with Eclipse, which works very 
> well.
>
> So I believe Adam is recommending using Maven-based projects for important 
> projects, like what is created by the second wizard.  I agree with that 
> recommendation as it allows leveraging the many tools in the Maven 
> ecosystem and works well with existing CI/CD solutions.
>
> Brian.
>
> On 9-May-2017, at 4:59 AM, Joshua Fox  wrote:
>
>
>
>
> * Eclipse incremental compiler and WTP to enable immediate run/debug and 
>> class replacement at debug-time *
>
>
> Thank  you. That makes sense.
>
> Adam of Cloud Platform Support, your statement (copied immediately below 
> in blue ) seems to contradict Brian's. Could you please explain?
>
>
> On Sat, May 6, 2017 at 11:08 PM, 'Adam (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>>  ...
>> a. Cloud Tools for Eclipse seems to be more of a 'getting started 
>> quickly' solution, with some UI conveniences but fewer features, so for 
>> more serious projects I'd personally recommend the Maven plugin.
>>
>> b. This really depends on your needs. There's nothing you can do with the 
>> Cloud Tools plugin that you can't do with the Maven plugin, and as 
>> mentioned you can also use both (one is a plugin for Maven via pom.xml, 
>> the other is for the Eclipse project proper, and they don't mess with each 
>> other).
>>
>
>
> On Mon, May 8, 2017 at 5:30 PM, Brian de Alwis  wrote:
>
>> CT4E is to the Maven plugin as m2eclipse is for maven: it uses Eclipse 
>> for what Eclipse does best, and Maven for what Maven does best.  CT4E 
>> leverages the Eclipse incremental compiler and WTP to enable immediate 
>> run/debug and class replacement at debug-time without having to restart the 
>> world.  And it also supports deployment from within Eclipse.
>>
>> Brian.
>>
>> On 8-May-2017, at 9:23 AM, Joshua Fox  wrote:
>>
>>  
>> On Mon, May 8, 2017 at 4:07 PM, Brian de Alwis  wrote:
>>
>>> Josuha, you can use the Cloud Tools for Eclipse (CT4E, the successor to 
>>> GPE) for launching even with Maven based plugins.
>>>
>>
>> Thank you. What added value does CT4E provide as compared to just Maven? 
>> Note that Adam of Google Support said:
>>  
>>  
>>
>> a. Cloud Tools for Eclipse seems to be more of a 'getting started 
>>> quickly' solution, with some UI conveniences but fewer features, so for 
>>> more serious projects I'd personally recommend the Maven plugin.
>>>
>>> b. This really depends on your needs. There's nothing you can do with 
>>> the Cloud Tools plugin that you can't do with the Maven plugin, 
>>>
>>>
>>  
>>
>>>  
>>>
>>>
>>> I didn't see a reference to this in the email thread, but I'm guessing 
>>> you're launching multiple services?  Launching multiple services is 
>>> supported by CT4E.
>>>
>>>
>> No, we are just launching  the builtin dev-appserver that you get when 
>> you run Maven goal  appengine:run on the Cloud-SDK Based 
>> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven>
>>  Maven plugin. Of course, I don't insist on using Maven to launch. 
>> Whatever it takes to avoid launching two processes just to debug ( 
>&

[google-appengine] Re: Google cloudstorage returns 404 Not Found when trying to delete from bucket (localhost)

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

Just noticed the Development/2.0 string in the response. When testing on 
the development server, the Cloud Storage client only interacts with the 
default bucket or the bucket set as the default on the command line. You 
can change the default bucket 
<https://cloud.google.com/appengine/docs/standard/python/googlecloudstorageclient/setting-up-cloud-storage#using_the_client_library_with_the_development_app_server>
 
by running dev_appserver.py with the --default_gcs_bucket_name 
[BUCKET_NAME] flag on the command line.

On Sunday, May 7, 2017 at 3:10:43 PM UTC-4, Richard Cheesmar wrote:
>
> It works when I delete an image cloudstorage.delete(image). However, that 
> image is in the apps default bucket.
>
>
> On Sunday, May 7, 2017 at 9:11:38 PM UTC+3, Adam (Cloud Platform Support) 
> wrote:
>>
>> Is this called from an App Engine standard app in production? Are you 
>> authenticating using specific credentials or using the default application 
>> credentials?
>>
>> On Sunday, May 7, 2017 at 9:49:02 AM UTC-4, Richard Cheesmar wrote:
>>>
>>> I am trying to delete a file (video) from Google Cloud Storage via the 
>>> cloudstorage api but although the file exists I'm getting the following 
>>> error:
>>>
>>> cloudstorage.delete('/catchamove-video/products/6411421952770048.mp4')
>>>
>>> *** NotFoundError: Expect status [204] from Google Storage. But got 
>>> status 404.
>>> Path: '/catchamove-video/products/6411421952770048.mp4'.
>>> Request headers: None.
>>> Response headers: {'transfer-encoding': 'chunked', 'date': 'Sun, 07 May 
>>> 2017 12:31:47 GMT', 'server': 'Development/2.0'}.
>>> Body: ''.
>>> Extra info: None.
>>> Both the bucket and file are present on the console.
>>>
>>> I have several buckets and this file is not in the default bucket...
>>>
>>

-- 
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/3abdd675-24ca-425b-8eb7-7de8d143f8b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: war size too large (exceeding 32M)

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

The archetype called 'skeleton-archetype' hasn't been updated since App 
Engine 1.7.5 circa 2013. Use the 'appengine-skeleton-archetype' or one of 
the other archetypes listed in the documentation 
<https://cloud.google.com/appengine/docs/standard/java/tools/maven#choosing_an_archetype>
.

On Saturday, May 6, 2017 at 10:48:10 PM UTC-4, Kent Tong wrote:
>
> Thanks for the reply!
>
> On Sunday, May 7, 2017 at 4:31:25 AM UTC+8, Adam (Cloud Platform Support) 
> wrote:
>>
>> What is the specific name of the archetype you're using, and how are you 
>> building and deploying? None of the archetypes from 
>> com.google.appengine.archetypes have files anywhere near that size.
>>
>
> I used the "skeleton-archetype". 
>
>>
>> Are you perhaps trying to upload your entire app's WAR as a single static 
>> file?
>>
>>
> What do you mean? I was trying to update the webapp with "mvn 
> appengine:update".
>

-- 
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/ebcc0c54-ba7e-4c61-976a-7200cb859409%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Maven plugins

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

I'm not sure I follow. You need to launch the dev_appserver process anyway 
to run your application locally. You're just passing extra JVM flags to 
enable the remote debugger so JDB can talk to it. AFAIK you need to enable 
the JPDA remote debugger to debug any Jetty app (or servlet container app 
for that matter). It's not a limitation of App Engine or the plugins.

On Sunday, May 7, 2017 at 9:01:22 AM UTC-4, Joshua Fox wrote:
>
>
>
> On Sat, May 6, 2017 at 11:08 PM, 'Adam (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>> 1. If I want to debug my projects without using "remote debugging"? 
>>
>> You need to use remote debugging to debug App Engine applications in 
>> Eclipse as the debugger must connect to the Jetty instance running on 
>> localhost.
>>
>>
> This is inconvenient.  Every time a developer runs their code, they have 
> to launch *two* processes. Is there a plan to improve that?
>
>
>
>> a. You don't need to use Google Cloud Tools for Eclipse as both maven 
>> plugins support the jvmFlags option which allows you to provide the 
>> necessary 
>> JVM flags for debugging 
>> <http://www.eclipse.org/jetty/documentation/9.4.5.v20170502/enable-remote-debugging.html>
>> :
>>
>> 
>> 
>>   -Xdebug
>>   
>> -Xrunjdwp:transport=dt_socket,address=,server=y,suspend=n
>> 
>>   
>>   
>> See the related discussion in an issue 
>> <https://github.com/GoogleCloudPlatform/appengine-maven-plugin/issues/6#issuecomment-134697957>
>>  
>> on the old plugin's project page for a solution involving Maven profiles 
>> (this applies equally to the new plugin as the same parameter is supported).
>>
>>
>> b. The ability to connect the debugger isn't dependent on the version of 
>> dev_appserver, which is mostly a Python wrapper around Jetty, so yes you 
>> would still be able to debug with either plugin. Note that as Jeff 
>> mentioned you can also use both plugins in your project.
>>
>>
>> 2. What is the recommended development setup for Standard Env?
>>
>> a. Cloud Tools for Eclipse seems to be more of a 'getting started 
>> quickly' solution, with some UI conveniences but fewer features, so for 
>> more serious projects I'd personally recommend the Maven plugin.
>>
>> b. This really depends on your needs. There's nothing you can do with the 
>> Cloud Tools plugin that you can't do with the Maven plugin, and as 
>> mentioned you can also use both (one is a plugin for Maven via pom.xml, 
>> the other is for the Eclipse project proper, and they don't mess with each 
>> other).
>>
>>
>> 3. What is the recommended development setup  for Flex Env development?
>>
>> No special App-Enginey bits are needed to test a flexible runtime app 
>> locally or manage it in Eclipse. This is covered in the docs 
>> <https://cloud.google.com/appengine/docs/flexible/java/testing-and-deploying-your-app#running_locally>;
>>  you 
>> can use mvn jetty:run-exploded with the Jetty plugin if you're on a 
>> Jetty based runtime or just mvn package; java -jar target/myjar.jar on 
>> any other runtime. A flexible runtime Java app is essentially just a 
>> Dockerized Java app that happens to run on the Flexible runtime.
>>
>>
>> On Wednesday, May 3, 2017 at 8:03:33 AM UTC-4, Joshua Fox wrote:
>> A question about Google Cloud Tools for Eclipse 
>> <https://cloud.google.com/eclipse/docs/>, given all these changes.
>>
>>
>> 1. If I want to debug my projects without using "remote debugging"? 
>> a. Do I need  Google Cloud Tools for Eclipse?
>> b. We are using the  Cloud-SDK-Based 
>> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven>
>>  1.30 Maven plugin  which has dev-appserver v1. If we wait until  
>> Cloud-SDK-Based 
>> Maven  plugin goes back to dev-appserver v2, (how long might hat be), will 
>> we be able to debug with a Cloud-SDK-Based Maven project (opened in 
>> Eclipse, but without Google Cloud Tools for Eclipse)?  
>>
>> 2. What is the recommended development setup for Standard Env? 
>> a. Is it Cloud Tools for Eclipse with the Cloud-SDK-Based Maven  plugin? 
>> b. Or just Cloud-SDK-Based Maven  plugin without Cloud Tools for Eclipse?
>>  
>> 3. What is the recommended development setup  for Flex Env development? 
>> We need a single dev-environment to develop a GAE-Standard-Env service and 
>> a GAE-Flex-Env service on the same codebase.
>> - We actually don't need "

[google-appengine] Re: Google cloudstorage returns 404 Not Found when trying to delete from bucket (localhost)

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

Is this called from an App Engine standard app in production? Are you 
authenticating using specific credentials or using the default application 
credentials?

On Sunday, May 7, 2017 at 9:49:02 AM UTC-4, Richard Cheesmar wrote:
>
> I am trying to delete a file (video) from Google Cloud Storage via the 
> cloudstorage api but although the file exists I'm getting the following 
> error:
>
> cloudstorage.delete('/catchamove-video/products/6411421952770048.mp4')
>
> *** NotFoundError: Expect status [204] from Google Storage. But got 
> status 404.
> Path: '/catchamove-video/products/6411421952770048.mp4'.
> Request headers: None.
> Response headers: {'transfer-encoding': 'chunked', 'date': 'Sun, 07 May 
> 2017 12:31:47 GMT', 'server': 'Development/2.0'}.
> Body: ''.
> Extra info: None.
> Both the bucket and file are present on the console.
>
> I have several buckets and this file is not in the default bucket...
>

-- 
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/23ae5ebb-55b6-4239-bb77-7d646b7e14ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: war size too large (exceeding 32M)

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

What is the specific name of the archetype you're using, and how are you 
building and deploying? No archetype I've tested from 
com.google.appengine.archetypes creates a WAR file anywhere near that size

On Saturday, May 6, 2017 at 1:24:38 AM UTC-4, Kent Tong wrote:
>
>
> Hi,
>
> Just the empty webapp created from the Google App Engine archetype creates 
> a war file of 43M. When I upload it, it will give an error saying that it 
> is larger than 32M. Is there anything fundamentally wrong here?
>
> Thanks in advance 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/276d8ee2-009c-42af-a3c3-9c7cedc2b4ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Maven plugins

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

1. If I want to debug my projects without using "remote debugging"? 

You need to use remote debugging to debug App Engine applications in 
Eclipse as the debugger must connect to the Jetty instance running on 
localhost.

a. You don't need to use Google Cloud Tools for Eclipse as both maven 
plugins support the jvmFlags option which allows you to provide the necessary 
JVM flags for debugging 

:



  -Xdebug
  
-Xrunjdwp:transport=dt_socket,address=,server=y,suspend=n

  
  
See the related discussion in an issue 

 
on the old plugin's project page for a solution involving Maven profiles 
(this applies equally to the new plugin as the same parameter is supported).


b. The ability to connect the debugger isn't dependent on the version of 
dev_appserver, which is mostly a Python wrapper around Jetty, so yes you 
would still be able to debug with either plugin. Note that as Jeff 
mentioned you can also use both plugins in your project.


2. What is the recommended development setup for Standard Env?

a. Cloud Tools for Eclipse seems to be more of a 'getting started quickly' 
solution, with some UI conveniences but fewer features, so for more serious 
projects I'd personally recommend the Maven plugin.

b. This really depends on your needs. There's nothing you can do with the 
Cloud Tools plugin that you can't do with the Maven plugin, and as 
mentioned you can also use both (one is a plugin for Maven via pom.xml, the 
other is for the Eclipse project proper, and they don't mess with each 
other).


3. What is the recommended development setup  for Flex Env development?

No special App-Enginey bits are needed to test a flexible runtime app 
locally or manage it in Eclipse. This is covered in the docs 
;
 you 
can use mvn jetty:run-exploded with the Jetty plugin if you're on a Jetty 
based runtime or just mvn package; java -jar target/myjar.jar on any other 
runtime. A flexible runtime Java app is essentially just a Dockerized Java 
app that happens to run on the Flexible runtime.


On Wednesday, May 3, 2017 at 8:03:33 AM UTC-4, Joshua Fox wrote:
A question about Google Cloud Tools for Eclipse 
, given all these changes.


1. If I want to debug my projects without using "remote debugging"? 
a. Do I need  Google Cloud Tools for Eclipse?
b. We are using the  Cloud-SDK-Based 

 1.30 Maven plugin  which has dev-appserver v1. If we wait until  
Cloud-SDK-Based 
Maven  plugin goes back to dev-appserver v2, (how long might hat be), will 
we be able to debug with a Cloud-SDK-Based Maven project (opened in 
Eclipse, but without Google Cloud Tools for Eclipse)?  

2. What is the recommended development setup for Standard Env? 
a. Is it Cloud Tools for Eclipse with the Cloud-SDK-Based Maven  plugin? 
b. Or just Cloud-SDK-Based Maven  plugin without Cloud Tools for Eclipse?
 
3. What is the recommended development setup  for Flex Env development? We 
need a single dev-environment to develop a GAE-Standard-Env service and a 
GAE-Flex-Env service on the same codebase.
- We actually don't need "Flex support" in the sense of a local Docker or 
builtin deployment. So the fact that  Cloud Tools for Eclipse  is said to 
not support Flex might not be relevant.
- For launching an appserver, we can use the Maven-Jetty plugin 
(org.eclipse.jetty::jetty-maven-plugin v 9.4.2)
- But I am not sure if that is the full recommended setup. What do you 
suggest?  

-- 
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/e0ad51ba-3dc0-45cd-8743-2fb1f9ba55a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Blobstore upload URLs fail intermittently

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

I'll take a look at the public issue and follow up there.

On Saturday, May 6, 2017 at 1:11:17 AM UTC-4, Attila-Mihaly Balazs wrote:
>
> Hello all,
>
> One of our clients is reporting that the blobstore upload URLs created by 
> create_upload_url is failing intermittently with 500 (but retrying works). 
> I created an issue with more details here: 
> https://issuetracker.google.com/issues/38046584 but I'm wondering if 
> anyone else is seeing this behavior? (this is especially tricky to track 
> down since the upload handler is a google controlled one which is 
> completely opaque for me and I see no logging or metrics from it and I need 
> to rely on customer reports to detect any issues).
>
> I also starred the following issue (and recommend you do the same if you 
> use the blobstore) to have an "error" callback/handler for better 
> monitoring - https://issuetracker.google.com/issues/35891517
>
> Attila
>

-- 
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/f06ea531-9bbd-4ce1-9b66-71d6bdd5e45d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error code 204 returned from Google App Engine - PHP

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

This generally signals an internal error. I'd advise opening a bug on the 
issue tracker  and 
include your project ID so we can take a look at the app server logs.

On Friday, May 5, 2017 at 12:22:52 AM UTC-4, Kelly Ingram wrote:
>
> Hi,
>
> I have been receiving the following 204 error quite a lot recently and 
> can't figure out what is causing the error as none of my PHP syslog items 
> are being output when it crashes.
>
>
> *A problem was encountered with the process that handled this request, 
> causing it to exit. This is likely to cause a new process to be used for 
> the next request to your application. (Error code 204)*
>
> It's a job that runs every half hour, so for the most part it works fine. 
>  It has only started doing this in the past 6 weeks or so.
>
> Any ideas on how to figure out what is going wrong?
>
>
> Thanks
>
> Kelly
>

-- 
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/6e659077-6e6c-494b-88f5-66819e75ea08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Maven plugins

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

Yes, you're right. I see that it was just changed in the 1.3.0 release 
<https://github.com/GoogleCloudPlatform/app-maven-plugin/blob/master/CHANGELOG.md>.
 
So you can ignore my first point, as it should now be fine to use the Cloud 
SDK based Maven plugin in all cases.

On Monday, May 1, 2017 at 2:20:12 PM UTC-4, Les Vogel wrote:
>
> Actually, the Cloud SDK based tooling now uses dev_appserver v1, not 
> dev_appserver 
> v2 to run your GAE Standard Java apps.
>
> On Sun, Apr 30, 2017 at 10:23 PM, Joshua Fox  wrote:
>
>> Thank you. That's useful.
>>
>> On Sun, Apr 30, 2017 at 9:48 PM, 'Adam (Cloud Platform Support)' via 
>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>
>>> To answer your questions:
>>>
>>>- Is it recommended over the other one? 
>>>
>>>It's actually recommended to use the App Engine standalone SDK based 
>>>plugin for now, due to some issues 
>>><https://b.corp.google.com/issues/36589995> with the development 
>>>server in the Cloud SDK.
>>>
>>>
>>>- See also the related discussion 
>>>
>>> <https://groups.google.com/d/topic/google-appengine/5MbPJK-TXAY/discussion> 
>>>for more details.
>>>
>>>- What is the relation to appcfg? Is it simply that appcfg is a 
>>>component of the Cloud-SDK (where the Cloud-SDK consists of gcloud 
>>>and related CLI tools)?
>>>
>>>The Cloud SDK based plugin doesn't have any dependency on appcfg. It 
>>>uses the gcloud command from the Cloud SDK to manage operations (eg. 
>>> gcloud 
>>>app <https://cloud.google.com/sdk/gcloud/reference/app> deploy). It 
>>>still invokes dev_appserver, but this is a newer version (v2) than 
>>>the one included in the standalone SDK (v1) and currently has some 
>>> issues 
>>>as mentioned above. 
>>>
>>>- Will an upcoming version depend on the Google App Engine SDK for 
>>>Java? 
>>>
>>>No, as the point of the plugin is to move away from the standalone 
>>>SDK and support the Cloud SDK.
>>>
>>>- I see that Google Cloud Tools for Eclipse interacts well with 
>>>Maven, so that Maven can handle dependency management, goals etc. Does 
>>> the 
>>>Google Cloud Tools for Eclipse bundle/use the 
>>>com.google.cloud.tools::appengine-maven-plugin?
>>>
>>>When you create a project using the template 'Maven-based Google App 
>>>Engine Standard Java Project', it will create a Maven project using the 
>>>appengine-standard-archetype archetype that uses the 
>>>com.google.cloud.tools::appengine-maven-plugin. This is just a UX 
>>>convenience for creating a regular Maven project that uses that same 
>>>archetype.
>>>
>>>
>>>  
>> What is the status of Google Cloud Tools for Eclipse? On the one hand, it 
>>  is recommended on the Google Group thread 
>> <https://groups.google.com/forum/#!topic/google-appengine/5MbPJK-TXAY/discussion>;
>>  
>> but on the other hand, it it is designed to work with the  Cloud-SDK 
>> Based 
>> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven>
>>  Maven plugin which is not now recommended.
>>  
>>
>>> On Sunday, April 30, 2017 at 9:30:39 AM UTC-4, Joshua Fox wrote:
>>>>
>>>> What is the difference between these  two Maven plugins?
>>>>
>>>>
>>>> - Based on the Google App Engine SDK for Java 
>>>> <https://cloud.google.com/appengine/docs/standard/java/tools/maven>
>>>>
>>>>- com.google.*appengine*::appengine:appengine-maven-plugin
>>>>- Older
>>>>
>>>>
>>>> - Cloud-SDK Based
>>>>
>>>> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven>
>>>>
>>>>- com.google.*cloud.tools:*:appengine-maven-plugin
>>>>- Newer
>>>>- Is it recommended over the other one? 
>>>>- What is the relation to *appcfg*? Is it  simply that appcfg is a 
>>>>component of the Cloud-SDK (where the Cloud-SDK consists of *gcloud 
>>>>*and related CLI tools)
>>>>- Will an upcoming version depend on the Google AppEngine SDK for 
>>>>Java? 
>>>>- I see that Google Cloud Tools for Eclipse 
>&g

[google-appengine] Re: Maven plugins

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

To answer your questions:

   - Is it recommended over the other one? 
   
   It's actually recommended to use the App Engine standalone SDK based 
   plugin for now, due to some issues 
    with the development server 
   in the Cloud SDK. See also the related discussion 
    
   for more details.
   
   - What is the relation to appcfg? Is it simply that appcfg is a 
   component of the Cloud-SDK (where the Cloud-SDK consists of gcloud and 
   related CLI tools)?
   
   The Cloud SDK based plugin doesn't have any dependency on appcfg. It 
   uses the gcloud command from the Cloud SDK to manage operations (eg. gcloud 
   app  deploy). It 
   still invokes dev_appserver, but this is a newer version (v2) than the 
   one included in the standalone SDK (v1) and currently has some issues as 
   mentioned above. 
   
   - Will an upcoming version depend on the Google App Engine SDK for Java? 
   
   No, as the point of the plugin is to move away from the standalone SDK 
   and support the Cloud SDK.
   
   - I see that Google Cloud Tools for Eclipse interacts well with Maven, 
   so that Maven can handle dependency management, goals etc. Does the Google 
   Cloud Tools for Eclipse bundle/use the 
   com.google.cloud.tools::appengine-maven-plugin?
   
   When you create a project using the template 'Maven-based Google App 
   Engine Standard Java Project', it will create a Maven project using the 
   appengine-standard-archetype archetype that uses the 
   com.google.cloud.tools::appengine-maven-plugin. This is just a UX 
   convenience for creating a regular Maven project that uses that same 
   archetype.


On Sunday, April 30, 2017 at 9:30:39 AM UTC-4, Joshua Fox wrote:
>
> What is the difference between these  two Maven plugins?
>
>
> - Based on the Google App Engine SDK for Java 
> 
>
>- com.google.*appengine*::appengine:appengine-maven-plugin
>- Older
>
>
> - Cloud-SDK Based
> 
>
>- com.google.*cloud.tools:*:appengine-maven-plugin
>- Newer
>- Is it recommended over the other one? 
>- What is the relation to *appcfg*? Is it  simply that appcfg is a 
>component of the Cloud-SDK (where the Cloud-SDK consists of *gcloud *and 
>related CLI tools)
>- Will an upcoming version depend on the Google AppEngine SDK for 
>Java? 
>- I see that Google Cloud Tools for Eclipse 
>   interacts well with Maven 
>, so that 
>Maven can handle dependency management, goals etc. Does the Google Cloud 
>Tools for Eclipse bundle/use the 
>- com.google.*cloud.tools:*:appengine-maven-plugin?
>
>

-- 
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/48be9f57-91ae-44ab-a47e-f8e325e20ba8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: many "Process terminated because the request deadline was exceeded. . (Error code 123)" errors for my go app recently

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

Good to hear you found the problem. Based on the information given, the 
only thing a reader would be able to deduce is that your request was taking 
too long for some reason and went over the 60 second deadline 

.

If you're seeing issue with the logs viewer I'd recommend filing a bug on 
the issue tracker  
and provide a screencast of the behavior as well as a HAR capture 
 of the session.

On Sunday, April 30, 2017 at 11:17:11 AM UTC-4, Tapir wrote:
>
> Aha, I think I found the issue.
> It is a bug in code.
> The code is modified two week ago.
>
> But it is weird that only the oldest log at April 24th prints the program 
> panic stack traces.
> Other logs don't print the stack traces.
>
> On Sunday, April 30, 2017 at 9:55:18 PM UTC+8, Tapir wrote:
>>
>> I can't get what is problem from the log:
>>
>> E  GET 500 0 B 100.9 s Googlebot 2 / GET 500 0 B 100.9 s 
>> Googlebot 2 
>> 590210c200ff08698603ab0f540001737e74617069722d67616d6573000132000100
>>   66.249.75.176 - - [27/Apr/2017:23:39:46 +0800] "GET / HTTP/1.1" 500 - - 
>>   "Mozilla/5.0 (compatible; Googlebot/2.1; +
>> http://www.google.com/bot.html)" 
>>   "www.tapirgames.com" ms=100878 cpu_ms=0 cpm_usd=0 loading_request=0 
>> instance=00c61b117c1539d61ab092aaf414fa9a3546b76458a415df22126384274e5d0a59a890fafe6c0872
>>  
>> app_engine_release=1.9.48 trace_id=7fb8718bb041a287d39cdbcd4b720651
>>
>>  {
>>  protoPayload: {
>>   @type: "type.googleapis.com/google.appengine.logging.v1.RequestLog"   
>>   appId: "s~tapir-games"   
>>   versionId: "2"   
>>   requestId: 
>> "590210c200ff08698603ab0f540001737e74617069722d67616d6573000132000100"   
>>   ip: "66.249.75.176"   
>>   startTime: "2017-04-27T15:39:46.551302Z"   
>>   endTime: "2017-04-27T15:41:27.430060Z"   
>>   latency: "100.878758s"   
>>   method: "GET"   
>>   resource: "/"   
>>   httpVersion: "HTTP/1.1"   
>>   status: 500   
>>   userAgent: "Mozilla/5.0 (compatible; Googlebot/2.1; +
>> http://www.google.com/bot.html)"   
>>   urlMapEntry: "_go_app"   
>>   host: "www.tapirgames.com"   
>>   instanceIndex: -1   
>>   finished: true   
>>   instanceId: 
>> "00c61b117c1539d61ab092aaf414fa9a3546b76458a415df22126384274e5d0a59a890fafe6c0872"
>>
>>
>>   line: [
>>0: {
>> time: "2017-04-27T15:41:27.429917Z" 
>> severity: "ERROR" 
>> logMessage: "Process terminated because the request deadline was 
>> exceeded. (Error code 123)" 
>>}
>>   ]
>>   appEngineRelease: "1.9.48"   
>>   traceId: "7fb8718bb041a287d39cdbcd4b720651"   
>>  }
>>  insertId: "59021127000691e464bf51ad"  
>>  httpRequest: {
>>   status: 500   
>>  }
>>  resource: {
>>   type: "gae_app"   
>>   labels: {
>>zone: "us2"
>>project_id: "tapir-games"
>>version_id: "2"
>>module_id: "default"
>>   }
>>  }
>>  timestamp: "2017-04-27T15:39:46.551302Z"  
>>  severity: "ERROR"  
>>  labels: {
>>   clone_id: 
>> "00c61b117c1539d61ab092aaf414fa9a3546b76458a415df22126384274e5d0a59a890fafe6c0872"
>>
>>
>>  }
>>  logName: "projects/tapir-games/logs/appengine.googleapis.com%2Frequest_log" 
>>  
>>
>>  operation: {
>>   id: 
>> "590210c200ff08698603ab0f540001737e74617069722d67616d6573000132000100"   
>>   producer: "appengine.googleapis.com/request_id"   
>>   last: true   
>>  }
>> }
>>
>> 23:41:27.429
>> Process terminated because the request deadline was exceeded. (Error code 
>> 123)
>>
>> Can someone provide me some hints?
>>
>

-- 
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/2e55317b-a89d-44dd-9d06-ff742fc28621%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: server not connect to aspmx.l.google.com 25

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

Further to the above,  aspmx.l.google.com is an inbound mail relay for 
GSuite / Google Apps <https://support.google.com/a/answer/33915?hl=en>, so 
can only route mail to GSuite domain users or Gmail users.

On Sunday, April 30, 2017 at 12:24:11 PM UTC-4, Adam (Cloud Platform 
Support) wrote:
>
> Socket connections to most Google IPs are blocked from App Engine 
> <https://cloud.google.com/appengine/docs/standard/php/sockets/>, which 
> includes aspmx.l.google.com. However you can connect to smtp.gmail.com on 
> port 465 or 587, which is the recommended way to send GSuite domain email 
> from an app <https://support.google.com/a/answer/176600?hl=en>.
>
> If you need to send more mail that the GSuite quota allows, you should use 
> an external mail relay service like Mailjet 
> <https://cloud.google.com/appengine/docs/standard/php/mail/mailjet> or 
> Sendgrid 
> <https://cloud.google.com/appengine/docs/standard/php/mail/sendgrid>.
>
> On Saturday, April 29, 2017 at 9:43:30 PM UTC-4, rlopez wrote:
>>
>> Hi I have a application in php-laravel running in a instance from google 
>> cloud but when I want to send a mail it does not work give a error 
>> as connect to alt2.aspmx.l.google.com[173.194.211.26]:25: Connection 
>> timed out ; when I try to connect with telnet aspmx.l.google.com 25 gime 
>> the this error 
>>
>> "Trying 173.194.197.26...
>> telnet: connect to address 173.194.197.26: Connection timed out
>> Trying 2607:f8b0:4001:c06::1a...
>> telnet: connect to address 2607:f8b0:4001:c06::1a: Network is unreachable"
>>
>> From my mac I run this telnet aspmx.l.google.com 25 it works well
>>
>> So? I do not know what happen , I need your help because my users can not 
>> reset their password because the mail does not sent
>>
>> 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/889e650f-8453-4f30-b9cc-4d165b6ebfaa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: server not connect to aspmx.l.google.com 25

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

Socket connections to most Google IPs are blocked from App Engine 
, which 
includes aspmx.l.google.com. However you can connect to smtp.gmail.com on 
port 465 or 587, which is the recommended way to send GSuite domain email 
from an app .

If you need to send more mail that the GSuite quota allows, you should use 
an external mail relay service like Mailjet 
 or 
Sendgrid 
.

On Saturday, April 29, 2017 at 9:43:30 PM UTC-4, rlopez wrote:
>
> Hi I have a application in php-laravel running in a instance from google 
> cloud but when I want to send a mail it does not work give a error 
> as connect to alt2.aspmx.l.google.com[173.194.211.26]:25: Connection 
> timed out ; when I try to connect with telnet aspmx.l.google.com 25 gime 
> the this error 
>
> "Trying 173.194.197.26...
> telnet: connect to address 173.194.197.26: Connection timed out
> Trying 2607:f8b0:4001:c06::1a...
> telnet: connect to address 2607:f8b0:4001:c06::1a: Network is unreachable"
>
> From my mac I run this telnet aspmx.l.google.com 25 it works well
>
> So? I do not know what happen , I need your help because my users can not 
> reset their password because the mail does not sent
>
> 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/e5ae0600-eccb-4fc0-af9d-befc3741815c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 503 error on deploy

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

I'd advise filing this on the Issue Tracker 
<https://cloud.google.com/support/docs/issue-trackers> and linking back to 
it here, so we can investigate further. It looks like you're trying to 
deploy over the same version, so you may also want to test deployment to a 
new version, or test on a new project.

On Saturday, April 22, 2017 at 3:15:56 PM UTC-4, Onno Eberhard wrote:
>
> Yes it is.
> I've attached a log file.
>
> Am Samstag, 22. April 2017 19:48:16 UTC+2 schrieb Adam (Cloud Platform 
> Support):
>>
>> In the past this has been related to issues on the App Engine side, but 
>> I'm not able to reproduce this currently. Is this a standard environment, 
>> Java 7 app?
>>
>> On Saturday, April 22, 2017 at 12:01:38 PM UTC-4, Onno Eberhard wrote:
>>>
>>> Hi,
>>>
>>> for a few days now, whenever I tried to deploy my application to GAE, I 
>>> received the following error:
>>>
>>> com.google.appengine.tools.admin.HttpIoException: Error posting to URL: 
>>> https://appengine.google.com/api/appversion/deploy?app_id=xx=1;
>>> 503 Service Unavailable
>>> Try Again (503)An unexpected failure has occurred. Please try again.
>>>
>>> This error occurs every time, except for maybe 1 in 30 attempts.
>>> I didn't have this error before, and I can't figure out what is causing 
>>> it..
>>>
>>> How can this problem be solved?
>>>
>>> Cheers,
>>> Onno Eberhard
>>>
>>

-- 
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/1a1e3fb1-a533-43be-b29b-282bba6ac83f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Flexible & Standard Appengine - Java

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

You can find a comprehensive list of changes in Migrating Services from the 
Standard Environment to the Flexible Environment. 
 You'll 
need to migrate your app to use the public APIs instead of the standard 
environment APIs. The most straightforward way is to use the 
google-cloud-java  
library.

Some services are not available in the flexible environment, notably 
Memcache 
 
and Push Task Queues 
, 
however there are replacements in early access alpha which you can sign up 
for, or use alternative services like Redis Labs Memcache or Google Cloud 
Pub/Sub / Pull Queues.

On Sunday, April 23, 2017 at 8:55:42 AM UTC-4, Rajesh Gupta wrote:
>
> We are on java standard appengine for 5+ years.
>
> Just want to know, what is not available in Flexible env that is available 
> in the Standard?
>
> What are the showstoppers to move to a flexible appengine env from a 
> Standard appengine.
>
> -- 
> Regards,
> Rajesh
> *www.VeersoftSolutions.com *
> *www.GainERP.com *
> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
> Mobile*
>
>

-- 
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/970579b8-3a01-4afd-bdf2-433f15e76d71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 503 error on deploy

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

In the past this has been related to issues on the App Engine side, but I'm 
not able to reproduce this currently. Is this a standard environment, Java 
7 app?

On Saturday, April 22, 2017 at 12:01:38 PM UTC-4, Onno Eberhard wrote:
>
> Hi,
>
> for a few days now, whenever I tried to deploy my application to GAE, I 
> received the following error:
>
> com.google.appengine.tools.admin.HttpIoException: Error posting to URL: 
> https://appengine.google.com/api/appversion/deploy?app_id=xx=1;
> 503 Service Unavailable
> Try Again (503)An unexpected failure has occurred. Please try again.
>
> This error occurs every time, except for maybe 1 in 30 attempts.
> I didn't have this error before, and I can't figure out what is causing 
> it..
>
> How can this problem be solved?
>
> Cheers,
> Onno Eberhard
>

-- 
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/8a9349ef-1fc1-4f42-a82f-d7af83f3a22f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Drive API - Does the API automatically create a folder for our Application.

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

Yes it does, see Storing Application Data 
, as well as Authorizing 
requests with OAuth 2.0 
 for 
details on the scopes required to access application data in Drive.

On Tuesday, April 18, 2017 at 3:41:07 PM UTC-4, Michael Joyner wrote:
>
> Hi out there.
>
> We our building our product for Google Drive and I wanted to know if the 
> Google Drive API automatically creates a App Folder like Dropbox does.
>
> I know some other Applications that I have like "draw.io" I can see that 
> they create App Folders, or at least I think they do. I know with Dropbox 
> that after OAuth Dropbox automatically will create a Application folder if 
> one does not exist.
>

-- 
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/5ecd2fb2-7f7a-469b-8663-694b6d9ce923%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App engine flex deployment fail

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

This looks related to an internal config issue. I'd advise opening a bug 
report on the issue tracker 
<https://cloud.google.com/support/docs/issue-trackers> and linking to it in 
this thread, so we can have the engineering team take a look at it. 

On Sunday, April 16, 2017 at 10:46:24 PM UTC-4, Roy Lee wrote:
>
> Yup, I get the same error message :(
>
> On Sunday, April 16, 2017 at 9:39:56 AM UTC-7, Adam (Cloud Platform 
> Support) wrote:
>>
>> Does deployment still fail when deploying to a new version, rather than 
>> over an existing version?
>>
>> On Sunday, April 16, 2017 at 12:06:30 PM UTC-4, Roy Lee wrote:
>>>
>>>
>>> Hello,
>>>
>>> I'm trying to deploy a nodejs app to app engine flex env, but I'm 
>>> constantly getting the following message.
>>>
>>> ERROR: (gcloud.app.deploy) Error Response: [13] Unexpected Error. ()
>>>
>>> I'm attaching the full output with --verbosity debug and a screen shot 
>>> of app engine activity. Please help!
>>>
>>> Thank you,
>>> Roy
>>>
>>

-- 
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/5ef9c0c5-8a7a-4752-8d06-6f14e3b80e2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: in datastore, how can i write long text over 1500 byte

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

You'll need to save the text as an unindexed property. To do this, you need 
to store the value explicitly as an array to specify excludeFromIndexes: 
true, eg.

var entity = { key: datastore.key('Company'), data: [ { name: 'description', 
value: "Some long text greater than 1500 bytes ...", excludeFromIndexes: 
true } ] };

More details can be found in the documentation for google-cloud-node 

.

On Sunday, April 16, 2017 at 12:06:09 PM UTC-4, 김진형 wrote:
>
> i wonder how to save longtext data in node.js
>
>
> when datastore web page
> i can select 'text' type
>
> but in nodejs i can't find how to string to text type
>
> please help
>
>
> i do not want to see that error message:
> Error: The value of property "content" is longer than 1500 bytes.
>

-- 
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/79de866b-f70c-42e5-8e4d-d1ee4eb61112%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App engine flex deployment fail

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

Does deployment still fail when deploying to a new version, rather than 
over an existing version?

On Sunday, April 16, 2017 at 12:06:30 PM UTC-4, Roy Lee wrote:
>
>
> Hello,
>
> I'm trying to deploy a nodejs app to app engine flex env, but I'm 
> constantly getting the following message.
>
> ERROR: (gcloud.app.deploy) Error Response: [13] Unexpected Error. ()
>
> I'm attaching the full output with --verbosity debug and a screen shot of 
> app engine activity. Please help!
>
> Thank you,
> Roy
>

-- 
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/a3a22011-bef5-4cc2-9851-8736f3cd304d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: java.security.AccessControlException: Multithreading in App engine

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

Not all third-party libraries can be used with App Engine Java standard 
runtime, due to the limitations imposed by the sandbox 
. If 
the library will accept a ThreadFactory 
,
 
you can pass it one that you get from 
com.google.appengine.api.ThreadManager.currentRequestThreadFactory() 
.
 
Otherwise, the library will need to be modified in such a way as to make 
use of App Engine's ThreadManager.

On Saturday, April 15, 2017 at 10:03:37 AM UTC-4, Manish Sharma wrote:
>
> Hello,
>
>
> This is my first post here.
>
>
> I am using GAE for my backend(module created through Android Studio). I 
> added a library that helps in sending FCM messages to FCM Cloud Connection 
> Server but this library spawns threads to handle things which is where I am 
> getting this exception for trying to spawn threads.
>
> Now, I know that TaskQueue API is provided for this purpose but the 
> library is not under my control.
>
> How can I get around problems with using 3rd party libs that use 
> concurrency?
>
>
> Any help is truly appreciated.
>

-- 
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/fcdc7cba-7278-4ffa-9793-c44a27eff4a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Call to pubsub publish hangs

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

Is this still occurring? If so, please file an issue on the Issue Tracker 
if you can provide a 
way to reproduce the issue.

On Saturday, April 15, 2017 at 12:23:24 AM UTC-4, Vinay Chitlangia wrote:
>
> All our calls to do a publish are hanging.
> Our servers are running on flex (non-compat) running pubsub 0.9.4-alpha 
> jars.
>
> Attached are logs...Just before doing the publishing..we log out 
> "Publishing..." and just after log "Published".
> The logs only have Publishing...they never make it to Published.
>
> The snippets of the pubsub code is:
>
> public class PubSubNugget extends FinalTouchNugget {
>   @Override
>   public void work() {
> try {
>   PubsubMessage pubsubMessage = 
> PubsubMessage.newBuilder().setData("payload".getBytes).build();
>   logger.warning("Publishing!!");
>   Publisher publisher = publisher();
>   publisher.publish(pubsubMessage).get();
>   publisher.shutdown();
>   logger.warning("Published");
> } catch (Exception e) {
>   logger.warning(ExceptionUtils.getFullStackTrace(e));
> }
>   }
>
>   private static TopicName initTopicName() {
> return TopicName.create(YConfiguration.get().applicationId(), 
> YConfiguration.get().pubsubTopic());
>   }
>   private static Publisher publisher() {
> try {
>   return Publisher.newBuilder(topicName).build();
> } catch (IOException e) {
>   logger.warning(ExceptionUtils.getFullStackTrace(e));
>   return null;
> }
>   }
>
>   private static TopicName topicName = initTopicName();
>   private static final Logger logger = 
> Logger.getLogger(PubSubNugget.class.getName());
> }
>
>

-- 
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/409bb3a6-322e-4206-8e97-7ccc79aa36a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: ApiProxy$UnknownException

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

Usually 'Error code 204' relates to an issue in the appserver, so its 
possible it was caused by ApiProxy$UnknownException as it was thrown in 
package com.google.apphosting.runtime. If you still see these errors, you 
might try deploying to a new version.  Otherwise you might want to report 
this on the Issue Tracker 
.

On Friday, April 14, 2017 at 12:21:31 PM UTC-4, Sven Reinck wrote:
>
> Hi there...
>
> I have a cron job that is running once per day... Three days ago there was 
> an error in the Log Console:
>
> "A problem was encountered with the process that handled this request, 
> causing it to exit. This is likely to cause a new process to be used for 
> the next request to your application. (Error code 204)"
>
> Since then I'm getting an ApiProxy$UnknownException every day not caused 
> by any of my code lines. So I do not know where to start looking. My app-id 
> is fluxparticle-de. Can anyone give me a hint where to start? Or is my App 
> Engine broken?
>
> Here is the stacktrace:
>
> com.google.apphosting.api.ApiProxy$UnknownException: An error occurred 
> for the API request datastore_v3.Get().
> at com.google.apphosting.runtime.ApiProxyImpl.statusException(A
> piProxyImpl.java:651)
> at com.google.apphosting.runtime.ApiProxyImpl$AsyncApiFuture.se
> tRpcError(ApiProxyImpl.java:604)
> at com.google.apphosting.runtime.ApiProxyImpl$AsyncApiFuture.fa
> ilure(ApiProxyImpl.java:592)
> at com.google.apphosting.runtime.stubby.StubbyCallbackAdapter.f
> ailure(StubbyCallbackAdapter.java:25)
> at com.google.net.rpc3.client.RpcStub$RpcCallbackDispatcher$1.
> runInContext(RpcStub.java:853)
> at com.google.tracing.TraceContext$TraceContextRunnable$1.run(T
> raceContext.java:460)
> at com.google.tracing.CurrentContext.runInContext(CurrentContex
> t.java:293)
> at com.google.tracing.TraceContext$AbstractTraceContextCallback
> .runInInheritedContextNoUnref(TraceContext.java:319)
> at com.google.tracing.TraceContext$AbstractTraceContextCallback
> .runInInheritedContext(TraceContext.java:311)
> at com.google.tracing.TraceContext$TraceContextRunnable.run(Tra
> ceContext.java:457)
> at com.google.net.rpc3.client.RpcStub$RpcCallbackDispatcher.run
> Callback(RpcStub.java:889)
> at com.google.net.rpc3.client.RpcStub$RpcCallbackDispatcher.rpc
> Finished(RpcStub.java:899)
> at com.google.net.rpc3.client.RpcStub$RpcCallbackDispatcher.fai
> lure(RpcStub.java:884)
> at com.google.net.rpc3.impl.client.RpcClientInternalContext.run
> Callbacks(RpcClientInternalContext.java:1243)
> at com.google.net.rpc3.impl.client.RpcClientInternalContext.fin
> ishRpcAndNotifyApp(RpcClientInternalContext.java:1137)
> at com.google.net.rpc3.impl.client.RpcNetChannel.afterFinishing
> ActiveRpc(RpcNetChannel.java:1694)
> at com.google.net.rpc3.impl.client.RpcNetChannel.finishRpc(
> RpcNetChannel.java:1508)
> at com.google.net.rpc3.impl.client.RpcNetChannel.handleResponse
> (RpcNetChannel.java:3366)
> at com.google.net.rpc3.impl.client.RpcNetChannel.messageReceive
> d(RpcNetChannel.java:3100)
> at com.google.net.rpc3.impl.client.RpcNetChannel.access$2900(
> RpcNetChannel.java:184)
> at com.google.net.rpc3.impl.client.RpcNetChannel$TransportCallb
> ack.receivedMessage(RpcNetChannel.java:4314)
> at com.google.net.rpc3.impl.client.RpcChannelTransportData$Tran
> sportCallback.receivedMessage(RpcChannelTransportData.java:688)
> at com.google.net.rpc3.impl.wire.RpcBaseTransport.receivedMessa
> ge(RpcBaseTransport.java:463)
> at com.google.apphosting.runtime.udrpc.UdrpcTransport$ClientAda
> pter.receivedMessage(UdrpcTransport.java:350)
> at com.google.apphosting.runtime.udrpc.UdrpcTransport.dispatchP
> acket(UdrpcTransport.java:196)
> at com.google.apphosting.runtime.udrpc.AbstractUdrpcTransport.r
> eadPackets(AbstractUdrpcTransport.java:202)
> at com.google.apphosting.runtime.udrpc.AbstractUdrpcTransport.a
> ccess$000(AbstractUdrpcTransport.java:30)
> at com.google.apphosting.runtime.udrpc.AbstractUdrpcTransport$1
> .run(AbstractUdrpcTransport.java:57)
> at com.google.net.eventmanager.AbstractFutureTask$Sync.innerRun
> (AbstractFutureTask.java:260)
> at com.google.net.eventmanager.AbstractFutureTask.run(AbstractF
> utureTask.java:121)
> at com.google.net.eventmanager.EventManagerImpl.runTask(EventMa
> nagerImpl.java:594)
> at com.google.net.eventmanager.EventManagerImpl.internalRunWork
> erLoop(EventManagerImpl.java:1012)
> at com.google.net.eventmanager.EventManagerImpl.runWorkerLoop(E
> ventManagerImpl.java:892)
> at com.google.net.eventmanager.WorkerThreadInfo.runWorkerLoop(W
> orkerThreadInfo.java:161)
> at com.google.net.eventmanager.EventManagerImpl$WorkerThread.ru
> n(EventManagerImpl.java:1877)
>

-- 
You 

[google-appengine] Re: gcloud vs. goapp for GO appengine

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

The downloads page 
<https://cloud.google.com/appengine/docs/standard/go/download> actually 
does say "The preferred tooling for managing your App Engine applications 
in Go is now the Google Cloud SDK'. This seems to be further reinforced by 
the fact that the standalone SDK is a few version behind, which I didn't 
notice before. 

I see that gcloud does nag about specifically 'dev_appserver.py' and 
'endpointscfg.py' being in your path when you run 'gcloud components 
update'. To avoid conflicts by invoking the older versions of these tools, 
it should be sufficient to keep the Cloud SDK first in your $PATH. 

Regarding Go 1.6, this is the version the 'goapp' toolchain is based on as 
well as the version used by the production runtime (Go 1.8 on GAE is coming 
soon 
<https://groups.google.com/forum/#!msg/google-appengine-go/sOg4eaEpst0/MqqC4FH4CAAJ>
 
though). There's no clean way to run different Go versions in parallel (I 
use a symlink that switches between two different install roots) so it 
would be difficult to document (though that's not to say there isn't room 
for improving the docs).

On Sunday, April 9, 2017 at 8:05:47 AM UTC-4, Tim Becker wrote:
>
> Hi Adam,
>
> thanks for the quick & great answers! 
>
> The documentation does provide a bit of guidance of how to use the three 
> (!) different tools that may be used to deploy, but it leaves me confused 
> as to which method is prefered, or what benefits of one method compared to 
> the others is. I hope the following doesn't seem to whiny, but just some 
> observations that are still fresh in my mind in the hope of helping improve 
> the docs:
>
> > You can still keep the standalone SDK installed alongside gcloud and use 
> the goapp workflow if you prefer. 
>
> At the end of the `install.sh` routines of `gcloud`, one is explicitly 
> encouraged to purge existing SDK intallations as not to conflict... Also, 
> the standalone SDK is not available in the latest version (1.9.48 vs. 
> 1.9.50 installed with gcloud) leaving me weary of conflicts.
>
> > The 'goapp' installed by gcloud resides in a directory outside of the 
> PATH on purpose so as not to conflict with the standalone SDK, and is meant 
> to be invoked only by gcloud. 
>
> From using goapp previously, it seemed `goapp` was intended to be a 
> replacement for all `go` tool invocations. `gcloud` takes care of 
> deployment, but that leaves me unsure what to do about `goapp 
> test|get|install` etc. The `gcloud` installation instructions (
> https://cloud.google.com/appengine/docs/standard/go/download) mention you 
> should install Go 1.6, so perhaps, the goapp isn't necessary. But, a.) 
> installing 1.6 is not actually  necessary as 1.6 seems to come together 
> with the app-engine-go component and b.) it offers no guidance of how to 
> install 1.6 and a newer version in parallel. As 1.6 is so outdated that 
> it's not even presented among he standard downloads in the Go download 
> archive page, I think it's safe to assume that many developers will not 
> want to use it as their default Go SDK.
>
> Again, hope I'm not being to negative and thanks once more for your 
> support!
> -tim
>
> On Saturday, 8 April 2017 22:18:15 UTC+2, Adam (Cloud Platform Support) 
> wrote:
>>
>> You can still keep the standalone SDK installed alongside gcloud and use 
>> the goapp workflow if you prefer. The 'goapp' installed by gcloud resides 
>> in a directory outside of the PATH on purpose so as not to conflict with 
>> the standalone SDK, and is meant to be invoked only by gcloud. The 'goroot' 
>> directory is the same goroot that is included in the standalone SDK. It's 
>> best not to try and mash parts of the SDKs together or expose internal bits 
>> of gcloud and try to use them like the standalone SDK.
>>
>> The different ways to deploy a standard environment Go app (goapp, 
>> gcloud, or appcfg) are given in the documentation Deploying a Go App. 
>> <https://cloud.google.com/appengine/docs/standard/go/tools/uploadinganapp> 
>> As 
>> to where your app should reside, you should always keep your app sources 
>> outside of the SDK directory tree, so which SDK you use should not matter.
>>
>> On Saturday, April 8, 2017 at 11:57:29 AM UTC-4, Tim Becker wrote:
>>>
>>> Sorry if I'm missing something obvious, but it seems that the 
>>> documenation is very unclear about this and was just recently changed with 
>>> no clear migration instructions:
>>>
>>>- since recently (~ last week sometime) the prefered way to install 
>>>Golang support seems to be via the "Google Cloud SDK" (vs the "original 
>>> App 
>>>Engine SDK for Go&

Re: [google-appengine] Recommended configuration for a java based App Engine standard application?

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

The 'com.google.appengine' development server works without issues with 
endpoints management in all of the v2 projects I've tested it with. The 
only changes I've needed are the following:

1) In the pom.xml for the project, change 'com.google.cloud.tools' to 
'com.google.appengine' and change the  to the appropriate App 
Engine SDK version (eg. 1.9.51) in the 'appengine-maven-plugin'  
section.

2) Replace the new maven goals on the command line with the old ones (eg. 
'mvn appengine:devserver' instead of 'mvn appengine:run').

The Endpoints tooling and managment is handled by the separate JARs 
'com.google.endpoints.endpoints:framework' and 
'com.google.endpoints:endpoints-management-control-appengine-all' which 
don't have a dependency on the specific devserver you're using.

The Java parts of the two devservers in fact are virtually identical, it's 
the Python layer that is different (and the primary source of the issues in 
the Cloud SDK devserver).

On Friday, April 7, 2017 at 5:23:14 PM UTC-4, Þórir Gunnarsson wrote:
>
> I didn't encounter any specific issues with the endpoints management 
> functionality as such, didn't go that far, the documentation is just all 
> referencing the com.google.cloud.com tools and I wanted to get some 
> feedback on where these things are at before going into implementation. 
> From what I could glimpse from the documentation (
> https://cloud.google.com/endpoints/docs/frameworks/java/generate-client-libraries-android)
>  
> of the configuration it seemed that I need to be more explicit about what 
> java classes implement endpoints, at least when generating the client 
> library. At the moment I have 35 different classes with around 300 
> different @ApiMethods so listing them all up and maintaining the list is 
> something I need to do in a sustainable way. You could probably argue that 
> I'm just lazy wanting reassurance before moving into new tech and writing 
> scripts to support it :-)
>
> Which development server should I use if I enable the endpoints management 
> functionality? Does the one in com.google.appengine work?
>
> ÞG
>
> On Friday, April 7, 2017 at 8:50:49 PM UTC, Adam (Cloud Platform Support) 
> wrote:
>>
>> You can still use Endpoints v2 tooling with the 'com.google.appengine' 
>> plugin as it is handled by endpoints-framework-tools and gcloud 
>> service-management. The only difference should be the version of the dev 
>> server you launch for local development. What specific issues with 
>> endpoints management did you encounter when switching back to the 
>> 'com.google.appengine' plugin?
>>
>> On Thursday, April 6, 2017 at 4:57:37 AM UTC-4, Þórir Gunnarsson wrote:
>>>
>>> Does anyone have any insights into endpoints v1 vs. endpoints v2? Any 
>>> real life success stories perhaps?
>>>
>>> We recently switched to endpoints v2 but without the endpoints 
>>> management functionality, I'm hesitant to go all in if this isn't being 
>>> used in production systems by at least a few people, or if it is not 
>>> production ready in general.
>>>
>>> ÞG
>>>
>>>
>>> On Tuesday, April 4, 2017 at 4:42:25 PM UTC, Jeff Schnitzer wrote:
>>>>
>>>> You’re not crazy, I have also seen that problem. Use the 
>>>> com.google.appengine 
>>>> maven plugin for the dev server for now. 
>>>>
>>>> I think this is the most relevant (albeit cryptic) issue that tracks 
>>>> that particular problem: 
>>>> https://github.com/GoogleCloudPlatform/app-maven-plugin/issues/158
>>>>
>>>> The com.google.tools plugin is the future, but the future isn’t quite 
>>>> here yet :-(
>>>>
>>>> Jeff
>>>>
>>>> On Tue, Apr 4, 2017 at 6:49 AM, Þórir Gunnarsson <
>>>> thorirgu...@goodlifeme.com> wrote:
>>>>
>>>>> I am currently using Maven and IntelliJ which in itself is fine. Most 
>>>>> of my issues are with the Maven plugins and recently endpoints versions.
>>>>> The com.google.cloud.tools plugin is not entirely there it seems, but 
>>>>> in a lot of documentation from Google it is the go-to plugin.
>>>>>
>>>>> I tried to switch to the com.google.cloud.tools plugin the other day 
>>>>> but ran into an issue with the local dev server (
>>>>> https://issuetracker.google.com/u/1/issues/36589995) which prompted 
>>>>> this thread here.
>>>>>
>>>>> ÞG
>>>>>
>>>>>
>>>>> On Tuesday, April 4, 2017 at 1:24:52 PM UTC, Jeff Schnitzer wrote:
>>>

[google-appengine] Re: devserver urlfetch and self-signed certificates...

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

There is no escalation process for bugs. The best course of action is to 
star the issue for visibility. Note that while annoying, it is possible to 
work around this particular bug through monkey patching 

.

On Sunday, April 9, 2017 at 9:48:06 AM UTC-4, Tim Becker wrote:
>
>
>
> After spending a good part of my weekend pulling my hair out trying to 
> access an API test endpoint which uses a self-signed certificate, I 
> discovered this:
>
> Devserver checks SSL certificates even when disabling it 
> https://issuetracker.google.com/issues/35899295
>
> almost two (!) year old bug. Is there any procedure to escalate bugs like 
> this or request an update, or should I just add a "me too" comment on the 
> issue?
>
>
>
>
>
>
>  
>

-- 
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/ef24b28a-37f6-4fab-8d1e-7d45c8e5a41c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Python Toolkit

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

Personally my usage tends to cascade as Eclipse (PyDev) -> Pluma/Gedit -> 
Vim depending on where I am focused on at the moment. I use Eclipse because 
I also do a lot of stuff in Java, but I've been leaning towards Atom more 
for non-Java stuff. Plugins  give 
Atom full IDE-like functionality (it's better than Eclipse for Python and 
JavaScript).

All of these tools are free and open source.

On Sunday, April 9, 2017 at 5:51:01 AM UTC-4, Johan Mutsaerts wrote:
>
> I am retooling for Python development on GAE, having used MS Visual Studio 
> before. I looked through the forum but the most recent thread on Python 
> IDE's dates from 2013, so I thought I'd ask for an update ...
>
> Toolkit choices I have made so far: GAE Standard Environment, Datastore 
> (NDB), Flask/Jinja2 framework. Now looking for the right IDE: Atom ? PyDev, 
> IntelliJ  or PyCharm ? Eclipse ? IntelliJ ? 
>
> Open Source (free) is what I am looking for to get things started, that is 
> before the money comes rolling in ... ;-)  Can I use the 'community 
> editions' of the commercial tools with the choices I have made earlier ? 
> and then upgrade later ? or are they just 'teasers' and you need to buy 
> them anyway to be productive ? From the web pages, I can see that e.g 
>  frameworks are only supported in the commercial editions ?   
>
> What's the practical benefit of using a full IDE over e.g. Atom when 
> developing in Python for GAE ? 
>
> TIA & BR,
> Johan
>

-- 
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/e6089f8e-02b5-40c4-acfb-f58bc5a2310e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: gcloud vs. goapp for GO appengine

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

You can still keep the standalone SDK installed alongside gcloud and use 
the goapp workflow if you prefer. The 'goapp' installed by gcloud resides 
in a directory outside of the PATH on purpose so as not to conflict with 
the standalone SDK, and is meant to be invoked only by gcloud. The 'goroot' 
directory is the same goroot that is included in the standalone SDK. It's 
best not to try and mash parts of the SDKs together or expose internal bits 
of gcloud and try to use them like the standalone SDK.

The different ways to deploy a standard environment Go app (goapp, gcloud, 
or appcfg) are given in the documentation Deploying a Go App. 
 As 
to where your app should reside, you should always keep your app sources 
outside of the SDK directory tree, so which SDK you use should not matter.

On Saturday, April 8, 2017 at 11:57:29 AM UTC-4, Tim Becker wrote:
>
> Sorry if I'm missing something obvious, but it seems that the documenation 
> is very unclear about this and was just recently changed with no clear 
> migration instructions:
>
>- since recently (~ last week sometime) the prefered way to install 
>Golang support seems to be via the "Google Cloud SDK" (vs the "original 
> App 
>Engine SDK for Go")
>- previously, the `goapp` tool was a central part of my workflow in 
>order to deal with the dependency on the completely outdated 1.6 version 
> of 
>Go required by appengine
>- using gcloud and installing go support via `gcloud components 
>install app-engine-go` gets me two `goapp`s:
>-  ./google-cloud-sdk/platform/google_appengine/goapp
>   -  ./google-cloud-sdk/platform/google_appengine/goroot/bin/goapp
>- the first of which is a python script with no executable bit set, 
>and neither of which are in the PATH set up by the install.sh script
>- running, eg. 
>`./google-cloud-sdk/platform/google_appengine/goroot/bin/goapp test` 
>results in the following error:
>   - `go: cannot find GOROOT directory: 
>   
> /private/var/folders/bs/nn10qt5j32g25qwgd77wkcyh00d7l1/T/appengine/go_appengine/goroot
>
> Now there are `gopath` and `goroot` dirs in the 
> `plattform/google_appengine` directory and I'm tempted to set the 
> corresponding environment variables to point to those directories, because 
> at least `goroot` seems to have all the necessary appengine dependencies 
> install in it. But this leaves me wondering, where my app should reside. 
> And dealing with appengine/gcloud/whatever it's called today in this manner 
> feels just like "trying out random stuff"
>
> The README contains completely outdated info from 2008. And the online 
> docs only seems to focus on using the "classic" SDK (e.g. 
> https://cloud.google.com/appengine/docs/standard/go/tools/localunittesting/
> )
>
> Is there any obvious documenation that I'm missing? Am I the only person 
> encountering these problems?
>
>
> (btw. I'm using OSX)
>

-- 
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/8574323f-6e5e-46cc-929b-0771dde866e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: The New version of App Engine?

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

The lwip library is failing to build libpng, which it depends on. The error 
mentions "see the notes in pngpriv.h". If you check the comments in that 
source file 
 
they say this:

#  error ZLIB_VERNUM != PNG_ZLIB_VERNUM \
  "-I (include path) error: see the notes in pngpriv.h"
   /* This means that when pnglibconf.h was built the copy of zlib.h that it
* used is not the same as the one being used here.  Because the build of
* libpng makes decisions to use inflateInit2 and inflateReset2 based on 
the
* zlib version number and because this affects handling of certain 
broken
* PNG files the -I directives must match.
*
* The most likely explanation is that you passed a -I in CFLAGS. This 
will
* not work; all the preprocessor directories and in particular all the 
-I
* directives must be in CPPFLAGS.
*/

Do you get this error when running 'npm install' and testing locally, or 
does it only occur when running 'gcloud app deploy'?


On Saturday, April 8, 2017 at 8:40:28 AM UTC-4, Petr Pololáník wrote:
>
> I use Google App Engine for me nodejs project. Today I tried deploy the 
> new version, but app engine throw error. After that I tried deploy the 
> previous version (worked in past), steel throw error.
>
> I do not understand it. It worked before, but now doesn't. The new version 
> of App Engine? Could you help me please?
>
> In log I see problem with lwip library. After remove it works, but I need 
> the library.
>
> In file included from ../src/lib/png/png.c:14:0: 
>> ../src/lib/png/pngpriv.h:805:4: error: #error ZLIB_VERNUM != 
>> PNG_ZLIB_VERNUM "-I (include path) error: see the notes in pngpriv.h" # 
>> error ZLIB_VERNUM != PNG_ZLIB_VERNUM \ ^ lwip_decoder.target.mk:165: 
>> recipe for target 'Release/obj.target/lwip_decoder/src/lib/png/png.o' failed
>>
>  
> Thank you.
>
>

-- 
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/a2582138-3990-4d30-916c-adee8505696c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: My custom domain redirect user to https://applicationid.appspot.com when i enable ssl

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

You'd want to troubleshoot one thing at a time. Forgetting the  'secure: 
always' redirect, what happens when you just try to access your domain via 
HTTPS directly after configuring SSL? If that doesn't work, there's a 
problem with your SSL config, not the redirect.

Remember that you actually need to add specific DNS records to your 
domain's DNS configuration at the step 'Configure resource records for your 
domain' (see step 5 and 6 in the documentation 
).
 
If you've done this, DNS records also need time to propagate. You can check 
propagation by using a tool like https://www.whatsmydns.net.

On Saturday, April 8, 2017 at 9:11:54 AM UTC-4, pankaj arora wrote:
>
> I have already set up my custom domain on google app engine and it works 
> fine .. i am using python standard environment.
> yesterday I add SSL certificate and add 'secure: always' to app.yml file  .
>
> 1- now when i try to access my custom domain it redirect user to sub 
> domain of appspot.com.
>
> 2- One more issue when i called naked domain .. it says page is not 
> redirect properly 
>
> if i remove  'secure: always'  from app.yml file  .every thing works fine 
> but without https 
>
> Any one can help me in this case.
>

-- 
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/60a2989b-575f-4b81-a268-b3ddfc63c9cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine NodeJS log severity

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

Actually, when browsing the sources for google-cloud-node I discovered 
there is now a new winston transport being developed - 
*@google-cloud/logging-winston 
<https://github.com/GoogleCloudPlatform/google-cloud-node/tree/master/packages/logging-winston>*.
 
Usage is greatly simplified:

var winston = require('winston');var transport = 
require('@google-cloud/logging-winston');
winston.add(transport);

winston.error('warp nacelles offline');winston.verbose('sheilds at 99%');



On Wednesday, April 5, 2017 at 3:32:00 AM UTC-4, Marco Galassi wrote:
>
> Hi Adam,
> thank you for your answer.
> I am probably just dumb, but I can't make the Cloud Logging APIs work.
> I have installed @google-cloud/logging through
>
> *npm install --save @google-cloud/logging*
>
> as pointed out in the documentation, put a random 
>
> *logging.log('this is a log')*
>
> in the / root handler, before sending back a response to the client, and 
> still, when I access the page,
> I only get an internal server error. The corresponding log in Stackdriver 
> is simply: "TypeError: logging.log is not a function at app.get"
> My code currently looks as simple as this:
> const express = require('express');
> var logging = require('@google-cloud/logging');
> const app = express();
>
> app.get('/', (req, res) => {
>   logging.log('this is a super cool log'); // Shouldn't this log?
>   res.status(200).send('Hello, world!');
> });
>
> if (module === require.main) {
>   const server = app.listen(process.env.PORT || 8080, () => {
> const port = server.address().port;
> console.log(`App listening on port ${port}`);
>   })
> }
> module.exports = app;
>
>
> I can't understand very well how to use it nor I can find a complete 
> example.
>
> Any help would be really appreciated.
>
>
>
> On Tuesday, April 4, 2017 at 9:56:55 PM UTC+2, Adam (Cloud Platform 
> Support) wrote:
>>
>> I see you'd already opened an issue 
>> <https://issuetracker.google.com/36851656> but it was closed. The reason 
>> being is that Google does not maintain the winston-gae project, which is an 
>> open source project. We do provide access to the Cloud Logging APIs via 
>> google-cloud-node 
>> <https://googlecloudplatform.github.io/google-cloud-node/#/docs/logging/0.9.0/logging/log>
>>  
>> though which you can use to implement your own logger or use directly in 
>> your code (or which can be referenced to update winston-gae, or implement a 
>> different solution).
>>
>> On Monday, April 3, 2017 at 3:00:19 AM UTC-4, Marco Galassi wrote:
>>>
>>> Yes, but that basically is just the same as doing 
>>> console.log('stdout');
>>> console.error('stderr');
>>>
>>> It would be nice to open an issue to ask google to implement it. Where 
>>> could I do this?
>>>
>>> Marco
>>>
>>>
>>> On Saturday, April 1, 2017 at 12:25:40 AM UTC+2, Adam (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> I've also been unable to get winston-gae working. It hasn't been 
>>>> updated in over 2 years and is not an official Google library, so for now 
>>>> it seems it's in need of a maintainer.
>>>>
>>>> The standard winston <https://www.npmjs.com/package/winston> logger 
>>>> does work, but only outputs to stdout and as such you don't get proper 
>>>> severity in the Logs Viewer.
>>>>
>>>> On Friday, March 31, 2017 at 11:03:20 AM UTC-4, Marco Galassi wrote:
>>>>>
>>>>>
>>>>> I am using nodejs on App Engine and I would like to have the ability 
>>>>> to log my application in an easy manner.
>>>>> Possibily, I would like to be able to log as easy as in python 
>>>>> standard environment 
>>>>> <https://cloud.google.com/appengine/docs/standard/python/logs/>:
>>>>>
>>>>> import logging
>>>>>> import webapp2
>>>>>> class MainPage(webapp2.RequestHandler):
>>>>>>   def get(self):
>>>>>> logging.debug('This is a debug message')
>>>>>> logging.info('This is an info message')
>>>>>> logging.warning('This is a warning message')
>>>>>> logging.error('This is an error message')
>>>>>> logging.critical('This is a critical message')
>>>>>> try:
>>>>>>   raise ValueError('This is a sample value error.')
>>>>>> except ValueError:
>>>>>>   logging.excep

Re: [google-appengine] Recommended configuration for a java based App Engine standard application?

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

You can still use Endpoints v2 tooling with the 'com.google.appengine' 
plugin as it is handled by endpoints-framework-tools and gcloud 
service-management. The only difference should be the version of the dev 
server you launch for local development. What specific issues with 
endpoints management did you encounter when switching back to the 
'com.google.appengine' plugin?

On Thursday, April 6, 2017 at 4:57:37 AM UTC-4, Þórir Gunnarsson wrote:
>
> Does anyone have any insights into endpoints v1 vs. endpoints v2? Any real 
> life success stories perhaps?
>
> We recently switched to endpoints v2 but without the endpoints management 
> functionality, I'm hesitant to go all in if this isn't being used in 
> production systems by at least a few people, or if it is not production 
> ready in general.
>
> ÞG
>
>
> On Tuesday, April 4, 2017 at 4:42:25 PM UTC, Jeff Schnitzer wrote:
>>
>> You’re not crazy, I have also seen that problem. Use the 
>> com.google.appengine 
>> maven plugin for the dev server for now. 
>>
>> I think this is the most relevant (albeit cryptic) issue that tracks that 
>> particular problem: 
>> https://github.com/GoogleCloudPlatform/app-maven-plugin/issues/158
>>
>> The com.google.tools plugin is the future, but the future isn’t quite 
>> here yet :-(
>>
>> Jeff
>>
>> On Tue, Apr 4, 2017 at 6:49 AM, Þórir Gunnarsson <
>> thorirgu...@goodlifeme.com> wrote:
>>
>>> I am currently using Maven and IntelliJ which in itself is fine. Most of 
>>> my issues are with the Maven plugins and recently endpoints versions.
>>> The com.google.cloud.tools plugin is not entirely there it seems, but in 
>>> a lot of documentation from Google it is the go-to plugin.
>>>
>>> I tried to switch to the com.google.cloud.tools plugin the other day but 
>>> ran into an issue with the local dev server (
>>> https://issuetracker.google.com/u/1/issues/36589995) which prompted 
>>> this thread here.
>>>
>>> ÞG
>>>
>>>
>>> On Tuesday, April 4, 2017 at 1:24:52 PM UTC, Jeff Schnitzer wrote:

 Your path of least resistance is to use Maven (as opposed to Gradle or 
 Ant/Ivy). If you’re working in Java, you definitely want an IDE - Eclipse 
 and IntelliJ both have their following. I think most people will be 
 happier 
 with IntelliJ but you have to pay for it.

 There are two viable maven plugins right now:

 com.google.appengine:appengine-maven-plugin is the older and more 
 mature plugin
 com.google.cloud.tools:appengine-maven-plugin is the newer and not yet 
 perfect plugin

 I would say we are on the cusp of the newer plugin being ready for 
 default use. It currently has trouble deploying the queue/cron configs, 
 but 
 it looks like it’s getting fixed fast. I actually have both enabled in my 
 project right now.

 You also have the choice of “older vs newer” plugin for 
 Eclipse/IntelliJ. I would go with the newer one.

 Someone else will have to give you endpoints advice.

 Jeff

 On Tue, Apr 4, 2017 at 2:16 AM, Þórir Gunnarsson <
 thorirgu...@goodlifeme.com> wrote:

> Lately I have been getting some mixed signals about what should be the 
> configuration for a java based App Engine standard backend using 
> endpoints. 
> What I'm looking for is guidelines from Google or the group what would be 
> best practices. The recommended configuration should be production ready 
> and support local development and debugging.
>
> As I see it there are several options (please add if I'm missing some 
> options)
>   - Environment
> - Maven
> - Eclipse
> - Maven project in Eclipse
> - Maven project in IntelliJ
>
>   - Build plugin (assuming Maven is the way to go)
>  - com.google.cloud.tools -> appengine-maven-plugin
>  - com.google.appengine -> appengine-maven-plugin
>  - com.google.appengine -> gcloud-maven-plugin
>
>   - Endpoints
>  - Endpoints v1
>  - Endpoints v2
>
> Some reference material:
> https://cloud.google.com/appengine/docs/standard/java/
>
> https://cloud.google.com/endpoints/docs/frameworks/java/quickstart-frameworks-java
>
> https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine/endpoints-frameworks-v2
>
> https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine/helloworld
>
> https://github.com/GoogleCloudPlatform/java-docs-samples/blob/master/appengine/helloworld-new-plugins
>
> -- 
> 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-appengi...@googlegroups.com.
> To post to this group, send email to google-a...@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.

[google-appengine] Re: Is TOKENIZED_PREFIX supported in Appengine search?

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

It looks like this is an issue specifically affecting the Java runtime. I'd 
recommend reporting this on the issue tracker 
 so we can link it to 
the internal issue and provide updates. Other users may star the issue to 
receive updates as well and increase visibility.

On Tuesday, April 4, 2017 at 8:14:39 AM UTC-4, Anand Srinivasan wrote:
>
> While looking through the java docs for Field in Document Index (
> https://cloud.google.com/appengine/docs/standard/java/javadoc/com/google/appengine/api/search/Field),
>  
> we noticed the presence of the "TOKENIZED_PREFIX" type which seems to match 
> closely with the search capability that we want. Unfortunately, when we try 
> to index a field with that type, we are running into an "Unsupported field 
> type" error. Is the documentation incorrect? Or am I using this 
> incorrectly? The indexing code does something like the following.
> 
> doc.addField(Field.newBuilder().setName(key).setTokenizedPrefix(valueStr));
> The exception occurs at the line index.put(doc.build());
>
> Unfortunately, our tests are running fine and as expected. The indexing 
> succeeds in the test and the query also works as expected. But we are 
> seeing this exception when the code is deployed to appengine.
>
> Any help to resolve this is greatly appreciated.
>
> 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/3692450b-d4f6-4c95-b8c0-227ef30f0dbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine NodeJS log severity

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

I see you'd already opened an issue 
<https://issuetracker.google.com/36851656> but it was closed. The reason 
being is that Google does not maintain the winston-gae project, which is an 
open source project. We do provide access to the Cloud Logging APIs via 
google-cloud-node 
<https://googlecloudplatform.github.io/google-cloud-node/#/docs/logging/0.9.0/logging/log>
 
though which you can use to implement your own logger or use directly in 
your code (or which can be referenced to update winston-gae, or implement a 
different solution).

On Monday, April 3, 2017 at 3:00:19 AM UTC-4, Marco Galassi wrote:
>
> Yes, but that basically is just the same as doing 
> console.log('stdout');
> console.error('stderr');
>
> It would be nice to open an issue to ask google to implement it. Where 
> could I do this?
>
> Marco
>
>
> On Saturday, April 1, 2017 at 12:25:40 AM UTC+2, Adam (Cloud Platform 
> Support) wrote:
>>
>> I've also been unable to get winston-gae working. It hasn't been updated 
>> in over 2 years and is not an official Google library, so for now it seems 
>> it's in need of a maintainer.
>>
>> The standard winston <https://www.npmjs.com/package/winston> logger does 
>> work, but only outputs to stdout and as such you don't get proper severity 
>> in the Logs Viewer.
>>
>> On Friday, March 31, 2017 at 11:03:20 AM UTC-4, Marco Galassi wrote:
>>>
>>>
>>> I am using nodejs on App Engine and I would like to have the ability to 
>>> log my application in an easy manner.
>>> Possibily, I would like to be able to log as easy as in python standard 
>>> environment 
>>> <https://cloud.google.com/appengine/docs/standard/python/logs/>:
>>>
>>> import logging
>>>> import webapp2
>>>> class MainPage(webapp2.RequestHandler):
>>>>   def get(self):
>>>> logging.debug('This is a debug message')
>>>> logging.info('This is an info message')
>>>> logging.warning('This is a warning message')
>>>> logging.error('This is an error message')
>>>> logging.critical('This is a critical message')
>>>> try:
>>>>   raise ValueError('This is a sample value error.')
>>>> except ValueError:
>>>>   logging.exception('A example exception log.')
>>>> self.response.out.write('Logging example.') 
>>>
>>>  
>>>
>>> app = webapp2.WSGIApplication([ 
>>>
>>> ('/', MainPage)
>>>> ], debug=True)
>>>
>>>
>>> This is very useful since it shows the logs with the corresponding 
>>> logging severity in the Stackdriver Logging console.
>>> Unfortunately, it doesn't look that something like this is possible on 
>>> NodeJS.
>>>
>>> I have tried to follow what the documentation says 
>>> <https://cloud.google.com/appengine/docs/flexible/nodejs/writing-application-logs>
>>>  
>>> on logging on NodeJS, which says that I can use winston-gae 
>>> <https://www.npmjs.com/package/winston-gae>, but it doesn't work at all.
>>>
>>> Any help is very appreciated.
>>>
>>

-- 
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/f2a36e28-d982-47ef-9d26-40534606e6d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Please give me my quick links back!

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

We've linked this thread to the team currently working on the new UI as 
feedback. For additional visibility I'd also recommend posting a bug report 
to the Cloud Console Issue Tracker 
, 
where you can star the issue and request others to do the same. One the 
issue is created I can link it to the internal issue tracking the UI 
updates as well.

On Wednesday, March 29, 2017 at 5:03:47 AM UTC-4, Gwyn Howell wrote:
>
> The cloud platform console app has recently been updated, adding nested 
> menus (awesome), and removed the customizable quick link icons (not so 
> awesome).
> It had become second nature to switch between components of the cloud 
> platform that were relevant to each specific project by using these quick 
> links. Now I have to go through the menu system, which a) is an extra click 
> and b) is much slower.
>
> OLD UI (awesome customizable quick link bar)
>
>
> 
>
>
> NEW UI (awesome nested menus, but no quick links)
>
>
> 
>
>
>
>
> Sorry to beef over something so seemingly petty, but this is really 
> slowing me down (and other devs in my team). It just doesn't make sense why 
> such a useful feature would be removed.
>
> Anyone else share my pain?
>
> Google - any chance of getting the quick links back?
>
>
> Cheers :)
> Gwyn
>

-- 
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/608fbde7-3935-4a54-84b1-58254accc6c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine NodeJS log severity

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

I've also been unable to get winston-gae working. It hasn't been updated in 
over 2 years and is not an official Google library, so for now it seems 
it's in need of a maintainer.

The standard winston  logger does 
work, but only outputs to stdout and as such you don't get proper severity 
in the Logs Viewer.

On Friday, March 31, 2017 at 11:03:20 AM UTC-4, Marco Galassi wrote:
>
>
> I am using nodejs on App Engine and I would like to have the ability to 
> log my application in an easy manner.
> Possibily, I would like to be able to log as easy as in python standard 
> environment 
> :
>
> import logging
>> import webapp2
>> class MainPage(webapp2.RequestHandler):
>>   def get(self):
>> logging.debug('This is a debug message')
>> logging.info('This is an info message')
>> logging.warning('This is a warning message')
>> logging.error('This is an error message')
>> logging.critical('This is a critical message')
>> try:
>>   raise ValueError('This is a sample value error.')
>> except ValueError:
>>   logging.exception('A example exception log.')
>> self.response.out.write('Logging example.') 
>
>  
>
> app = webapp2.WSGIApplication([ 
>
> ('/', MainPage)
>> ], debug=True)
>
>
> This is very useful since it shows the logs with the corresponding logging 
> severity in the Stackdriver Logging console.
> Unfortunately, it doesn't look that something like this is possible on 
> NodeJS.
>
> I have tried to follow what the documentation says 
> 
>  
> on logging on NodeJS, which says that I can use winston-gae 
> , but it doesn't work at all.
>
> Any help is very appreciated.
>

-- 
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/9189dabe-b09a-4e24-bc7a-be68f0fb1142%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Understanding java.util.ConcurrentModificationException: too much contention on these datastore entities. please try again.

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

Yes, actually you can ignore my post as I misread your original issue.

On Tuesday, March 28, 2017 at 2:58:35 AM UTC-4, Louise Elmose Hedegaard 
wrote:
>
> Hi Adam,
>
> Why do you mention timeout - ConcurrentModificationException is not 
> related to timeouts is it?
>
> Thanks,
> -Louise
>
> Den lørdag den 25. marts 2017 kl. 00.02.05 UTC+1 skrev Adam (Cloud 
> Platform Support):
>>
>> A great article that explains this is 'Timeouts due to write contention 
>> <https://cloud.google.com/appengine/articles/handling_datastore_errors#timeouts-due-to-write-contention>
>> ': 
>>
>> *Writes to a single entity group are serialized by the App Engine 
>>> datastore, and thus there's a limit on how quickly you can update one 
>>> entity group. In general, this works out to somewhere between 1 and 5 
>>> updates per second.*
>>
>>
>> Writing to the same entity twice successively is enough to cause a 
>> ConcurrentModificationException. Strategies to avoid this are discussed in 
>> 'Avoiding 
>> datastore contention 
>> <https://cloud.google.com/appengine/articles/scaling/contention>'.  
>>
>> On Friday, March 24, 2017 at 3:18:28 AM UTC-4, Louise Elmose Hedegaard 
>> wrote:
>>>
>>> Hi,
>>>
>>> In my app I have the following logic (pseudoCode):
>>>
>>> List nonSentMails= getNonSentMails();//1) datastore read
>>>
>>> List sendNow = new ArrayList(); 
>>> for each nonSentMail in nonSentMails
>>>if (sendNow(nonSentMail)){
>>>sendNow.add(nonSentMail);
>>>}
>>>
>>> for each nonSentMail in sendNow
>>> SentStatus sentStatus = sendMailViaRestApi();
>>> create maillog in datastore with sent status//2) datastore write - 
>>> new entry
>>> nonSentMail.setSentStatus(sentStatus);
>>>
>>> update(sendNow) //3) datastore write
>>>
>>>
>>> When comitting the above I get:
>>> java.util.ConcurrentModificationException: too much contention on these 
>>> datastore entities. please try again.
>>>
>>> This is a problem, as the operation is not idempotent - when I send a 
>>> mail via a REST API the mail is sent immediately, and I want the status of 
>>> my maillog and NonSentMail objects to reflect this.
>>>
>>> I do not understand why this error occurs. 
>>> There are only three operations on the datastore:
>>> 1) The initial read of non sent mails
>>> 2) The creation of new mail log entries
>>> 3) The update of the status of non sent mails
>>>
>>> 2) should never lead to ConcurrentModificationException as far as I 
>>> understand it. 1) and 3) operates on the same entities, but 1) only reads, 
>>> so I cannot see any problem here either.
>>> Furthermore there is currently only one user of my app, so there should 
>>> be no other threads accessing the data.
>>> Note that the elements in sendNow might have the same parents, but again 
>>> I do not believe this should be a problem?
>>>
>>> Can you please help me understand why the above code can lead to a 
>>> ConcurrentModificationException?
>>>
>>> Thanks,
>>> -Lull
>>>
>>>

-- 
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/27250a3f-2e9c-4928-aa12-03478279f243%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Problems getting started with App Engine free trial

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

I've requested for a member of our billing team to reach out to you to help 
get this resolved.

On Monday, March 27, 2017 at 2:29:16 PM UTC-4, Carl Caulkett wrote:
>
> Please read my initial description of the problem. The main problem was 
> NOT the description of the page at the top.
>
> On Monday, March 27, 2017 at 7:27:30 PM UTC+1, Carl Caulkett wrote:
>>
>> I have supplied both bank account details and debit card details, and 
>> despite not being alerted to any specific problem, both applications were 
>> rejected. I do not have the necessary account credentials for a billing 
>> support ticket, and the items described in the Free Trial Troubleshooter 
>> rather suggest that they are intended for those lucky soles who have got 
>> past the bank verification mechanism. I repeat my details are perfectly 
>> valid - would it be heretical to suggest that the verification mechanism is 
>> broken. 
>>
>> On Monday, March 27, 2017 at 6:20:00 PM UTC+1, Adam (Cloud Platform 
>> Support) wrote:
>>>
>>> The page is labeled "Google Cloud Platform" because the free trial is for 
>>> Google Cloud Platform <https://cloud.google.com/free/>, of which App 
>>> Engine is just one part. Free trial verification requires either a credit 
>>> card or bank account details 
>>> <https://cloud.google.com/free/docs/frequently-asked-questions> for 
>>> verification. If you have further issues or questions you may open a 
>>> billing 
>>> support ticket 
>>> <https://support.google.com/cloud/contact/cloud_platform_billing>, or 
>>> use the Free Trial Troubleshooter 
>>> <https://support.google.com/cloud/troubleshooter/6275061?hl=en>.
>>>
>>> On Monday, March 27, 2017 at 12:02:43 PM UTC-4, Carl Caulkett wrote:
>>>>
>>>> Hello, I am trying to get started with the App Engine free trial but I 
>>>> cannot get the page (Labelled confusingly Google Cloud Platform) to accept 
>>>> either my Debit card or my bank details. The card details do not show any 
>>>> errant items and the bank details show no errors when the verify button is 
>>>> pressed. Yet when I press "Start my Free Trial" I am told to Verify. And 
>>>> if 
>>>> I have chosen the Debit card method, I am informed that the "Transaction 
>>>> was declined due to an Invalid Payment" method. Frankly this is appalling 
>>>> and doesn't fill one with confidence to build "Financial Apps of the 
>>>> Future" if it cannot get a freaking Debit card payment mechanism sorted. 
>>>> How do I start my App Engine Free Trial?
>>>>
>>>

-- 
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/1a168b68-bc55-4541-95de-7e4cced5d38f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error 403 with Android restricted Cloud Platform API key and Cloud Endpoints

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

Provided that you are using the Endpoints client library that you generated 
for Android 
,
 
it's not necessary to manually add the headers yourself. You need to 
configure the client library to authenticate, and the full instructions for 
this are provided in the documentation Calling Backend APIs from an Android 
Client 

.

On Monday, March 27, 2017 at 2:20:46 PM UTC-4, Cristina De Rito wrote:
>
> I have a problem restricting a Google Cloud Platform API key usage to an 
> Android app: I have added its package name and certificate SHA-1 
> fingerprint (the debug one to get started) but it doesn't work.
>
> 
>
>
> The error I get when calling any API is
>
> 403 Requests from this Android client application  are blocked.
>
> I'm calling the APIs by using a Cloud Endpoints generated client lib, and 
> I've not been able to find any method that I can use at initialisation time 
> to set the app credentials, nor does it do it by itself (as I can guess 
> from the "" in the error). I can't find any useful info in any 
> documentation as well, as far as I've red it seems like it should do it by 
> itself.
>
> This is my init code:
>
> MyApi.Builder builder = new MyApi.Builder(new NetHttpTransport(), new 
> AndroidJsonFactory(), null)
> .setApplicationName("")
> .setRootUrl()
> .setGoogleClientRequestInitializer(new 
> MyApiRequestInitializer());
>
> I've also tried what suggested in this answer 
>  but nothing changed.
>
> Is there any passage I'm missing? How should it be done?
>

-- 
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/5ffe2acf-1437-48b2-832a-2c278ed37ed7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Problems getting started with App Engine free trial

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

The page is labeled "Google Cloud Platform" because the free trial is for 
Google Cloud Platform , of which App Engine 
is just one part. Free trial verification requires either a credit card or 
bank account details 
 for 
verification. If you have further issues or questions you may open a billing 
support ticket 
, or use 
the Free Trial Troubleshooter 
.

On Monday, March 27, 2017 at 12:02:43 PM UTC-4, Carl Caulkett wrote:
>
> Hello, I am trying to get started with the App Engine free trial but I 
> cannot get the page (Labelled confusingly Google Cloud Platform) to accept 
> either my Debit card or my bank details. The card details do not show any 
> errant items and the bank details show no errors when the verify button is 
> pressed. Yet when I press "Start my Free Trial" I am told to Verify. And if 
> I have chosen the Debit card method, I am informed that the "Transaction 
> was declined due to an Invalid Payment" method. Frankly this is appalling 
> and doesn't fill one with confidence to build "Financial Apps of the 
> Future" if it cannot get a freaking Debit card payment mechanism sorted. 
> How do I start my App Engine Free Trial?
>

-- 
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/36f1e3bc-87d8-4a4a-8aa4-6dbdfdc1f881%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: webapp2 pgoram!Client computers generate a large time_wait_connect！

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

I'm not sure why you'd want to do this, except maybe to hide the fact that 
your site does not have a valid SSL certificate. One cause of latency is 
the fact that you're buffering the entire response in App Engine before 
sending it along to the client, but really what you're doing is a hack and 
not good practice. You can get a real cert for free at 
https://letsencrypt.org and save yourself the trouble. 

On Thursday, March 23, 2017 at 9:13:50 AM UTC-4, bruce lee wrote:
>
> I use GAE platform to forward HTTP SSL data.(python webapp2)
> why?use ssl client make large time_wait connect?
> But HTTP is normal.
>
>
>
>
> code:
>
>
> #!/usr/bin/env python
> #
> # Copyright 2007 Google Inc.
> #
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> #
>
> import base64, logging
> import webapp2
> from google.appengine.api import urlfetch
>
> class MainHandler(webapp2.RequestHandler):
> def get(self):
> useSSL = 0
> _url = self.request.url.lower()
> if _url.find('https://')==0:
> useSSL = 1
>
> _url = self.request.url #restore
> 
> _path = self.request.path
> 
> if _path=="/": #for test
> self.response.headers["Content-Type"] = "text/html; 
> charset=utf-8"
> self.response.write("Hello, guys")
> else:  
> nPos = _url.find(_path)
> sub_url = _url[nPos:len(_url)]
>
> if useSSL==1:
> url = "https://198.52.119.103:443"+sub_url
> else:
> url = "http://198.52.119.103"+sub_url
>
> rpc = urlfetch.create_rpc()
> urlfetch.make_fetch_call(rpc, url, validate_certificate=False)
>
>
> # ... do other things ..
> try:
> result = rpc.get_result()
> if result.status_code == 200:
> text = result.content
> self.response.write(text)
> else:
> self.response.status_int = result.status_code
> self.response.write('URL returned status code 
> {}'.format(result.status_code))
> except urlfetch.DownloadError:
> self.response.status = 500
> self.response.write('Error fetching URL')
>
> def post(self):
> useSSL = 0
> _url = self.request.url.lower()
> if _url.find('https://')==0:
> useSSL = 1
>
> _url = self.request.url #restore
> 
> _path = self.request.path
> 
> if _path=="/": #for test
> self.response.headers["Content-Type"] = "text/html; 
> charset=utf-8"
> self.response.write("Hello, guys")
> else:  
> nPos = _url.find(_path)
> sub_url = _url[nPos:len(_url)]
> 
>
> if useSSL==1:
> url = "https://test.server.com:443"+sub_url
> else:
> url = "http://test.server.com"+sub_url
>
> 
> #def make_fetch_call(rpc, url, payload=None, method=GET, 
> headers={},
> #allow_truncated=False, follow_redirects=True,
> #validate_certificate=None):
>
> _headers = {'Content-Type': 'application/octet-stream', 
> 'Content-Length': self.request.headers['Content-Length']}
> rpc = urlfetch.create_rpc()
> urlfetch.make_fetch_call(rpc, url, self.request.body, 2, 
> _headers, validate_certificate=False)
>
>
> # ... do other things ..
> try:
> result = rpc.get_result()
> if result.status_code == 200:
> text = result.content
> self.response.write(text)
> else:
> self.response.status_int = result.status_code
> self.response.write('URL returned status code 
> {}'.format(result.status_code))
> except urlfetch.DownloadError:
> self.response.status = 500
> self.response.write('Error fetching URL')
>   
> app = webapp2.WSGIApplication([
> ('.*', MainHandler)
> ], debug=True)
>
>

-- 
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] Re: https ssl redir program program?

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

Posting your entire uncommented code and asking the community to debug it 
for you isn't likely to result in much feedback. If you can narrow it down 
to a specific succinct question I'd recommend posting a question to Stack 
Overflow . It's a good 
idea to first read the guide 'How do I ask a good question? 
' before posting.

If all you need to do is ensure some of your app's handlers are secured by 
HTTPS via redirect, you can do this with the 'secure: always' 
element
 
in your app.yaml configuration.

On Friday, March 24, 2017 at 3:11:06 AM UTC-4, bruce lee wrote:
>
> i am newbie..
> i make program...redir https.eveyone thing success.
> After the client accesses, a large amount of time_wait is generated.
> please help me?
>
> code:
> import base64, logging
> import webapp2
> from google.appengine.api import urlfetch
>
> class MainHandler(webapp2.RequestHandler):
> def get(self):
> useSSL = 0
> _url = self.request.url.lower()
> if _url.find('https://')==0:
> useSSL = 1
>
> _url = self.request.url #restore
> 
> _path = self.request.path
> 
> if _path=="/": #for test
> self.response.headers["Content-Type"] = "text/html; 
> charset=utf-8"
> self.response.write("Hello, guys")
> else:  
> nPos = _url.find(_path)
> sub_url = _url[nPos:len(_url)]
>
> if useSSL==1:
> url = "https://my.ip:443"+sub_url
> else:
> url = "http://my.ip"+sub_url
>
> rpc = urlfetch.create_rpc()
> urlfetch.make_fetch_call(rpc, url, validate_certificate=False)
>
>
> # ... do other things ..
> try:
> result = rpc.get_result()
> if result.status_code == 200:
> text = result.content
> self.response.write(text)
> else:
> self.response.status_int = result.status_code
> self.response.write('URL returned status code 
> {}'.format(result.status_code))
> except urlfetch.DownloadError:
> self.response.status = 500
> self.response.write('Error fetching URL')
>
> def post(self):
> useSSL = 0
> _url = self.request.url.lower()
> if _url.find('https://')==0:
> useSSL = 1
>
> _url = self.request.url #restore
> 
> _path = self.request.path
> 
> if _path=="/": #for test
> self.response.headers["Content-Type"] = "text/html; 
> charset=utf-8"
> self.response.write("Hello, guys")
> else:  
> nPos = _url.find(_path)
> sub_url = _url[nPos:len(_url)]
> 
>
> if useSSL==1:
> url = "https://test.server.com:443"+sub_url
> else:
> url = "http://test.server.com"+sub_url
>
> 
> #def make_fetch_call(rpc, url, payload=None, method=GET, 
> headers={},
> #allow_truncated=False, follow_redirects=True,
> #validate_certificate=None):
>
> _headers = {'Content-Type': 'application/octet-stream', 
> 'Content-Length': self.request.headers['Content-Length']}
> rpc = urlfetch.create_rpc()
> urlfetch.make_fetch_call(rpc, url, self.request.body, 2, 
> _headers, validate_certificate=False)
>
>
> # ... do other things ..
> try:
> result = rpc.get_result()
> if result.status_code == 200:
> text = result.content
> self.response.write(text)
> else:
> self.response.status_int = result.status_code
> self.response.write('URL returned status code 
> {}'.format(result.status_code))
> except urlfetch.DownloadError:
> self.response.status = 500
> self.response.write('Error fetching URL')
>   
> app = webapp2.WSGIApplication([
> ('.*', MainHandler)
> ], debug=True)
>
>
>

-- 
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/e023dc0b-b611-443c-ab81-f065a752f0dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Understanding java.util.ConcurrentModificationException: too much contention on these datastore entities. please try again.

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

A great article that explains this is 'Timeouts due to write contention 

': 

*Writes to a single entity group are serialized by the App Engine 
> datastore, and thus there's a limit on how quickly you can update one 
> entity group. In general, this works out to somewhere between 1 and 5 
> updates per second.*


Writing to the same entity twice successively is enough to cause a 
ConcurrentModificationException. Strategies to avoid this are discussed in 
'Avoiding 
datastore contention 
'.  

On Friday, March 24, 2017 at 3:18:28 AM UTC-4, Louise Elmose Hedegaard 
wrote:
>
> Hi,
>
> In my app I have the following logic (pseudoCode):
>
> List nonSentMails= getNonSentMails();//1) datastore read
>
> List sendNow = new ArrayList(); 
> for each nonSentMail in nonSentMails
>if (sendNow(nonSentMail)){
>sendNow.add(nonSentMail);
>}
>
> for each nonSentMail in sendNow
> SentStatus sentStatus = sendMailViaRestApi();
> create maillog in datastore with sent status//2) datastore write - new 
> entry
> nonSentMail.setSentStatus(sentStatus);
>
> update(sendNow) //3) datastore write
>
>
> When comitting the above I get:
> java.util.ConcurrentModificationException: too much contention on these 
> datastore entities. please try again.
>
> This is a problem, as the operation is not idempotent - when I send a mail 
> via a REST API the mail is sent immediately, and I want the status of my 
> maillog and NonSentMail objects to reflect this.
>
> I do not understand why this error occurs. 
> There are only three operations on the datastore:
> 1) The initial read of non sent mails
> 2) The creation of new mail log entries
> 3) The update of the status of non sent mails
>
> 2) should never lead to ConcurrentModificationException as far as I 
> understand it. 1) and 3) operates on the same entities, but 1) only reads, 
> so I cannot see any problem here either.
> Furthermore there is currently only one user of my app, so there should be 
> no other threads accessing the data.
> Note that the elements in sendNow might have the same parents, but again I 
> do not believe this should be a problem?
>
> Can you please help me understand why the above code can lead to a 
> ConcurrentModificationException?
>
> Thanks,
> -Lull
>
>

-- 
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/aec47937-549f-4de2-899d-b59da5163ad8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions still running (flexible environment)

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

Are you using manual scaling or automatic scaling in your app.yaml? If 
you're using manual scaling, App Engine will try to keep instances alive 
indefinitely 

 
until you manually shut them down.

On Thursday, March 16, 2017 at 3:10:07 PM UTC-4, Alan deLespinasse wrote:
>
> I'm not sure if this is a bug or expected behavior. It's not what I 
> expected, but I'm still somewhat confused by the Cloud Console.
>
> I have several services for which I noticed there were still some old 
> versions running, although the old versions were serving 0% of traffic. 
> Example:
>
>
> 
>
> The two selected versions were made obsolete by the top version. Normally 
> when I deploy a new version, the previously running version is shut down. 
> In these cases, I think a new version never succeeded in starting up, 
> because I had a bug that would simply crash every time. So here's what 
> apparently happens:
>
>1. Version A is running
>2. I try to deploy version B; it repeatedly fails to start up. My 
>"gcloud app deploy" command eventually returns an error, telling me that 
>deployment failed. Version A is still serving all traffic. Version B is 
>apparently still running, though I didn't know that until just now.
>3. I fix the bug and deploy version C. It starts up, version A is 
>correctly stopped. Apparently version B is still running, though.
>
> So, is this a bug or expected? Is it costing us money? I'm finding it a 
> bit hard to tell what our recent charges are for, although they are a bit 
> higher than expected (still looking into that). I'd submit a billing ticket 
> if I was sure.
>

-- 
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/e4dc55fc-95e3-4c4d-8d75-a5b7fc4c3012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: What whas wrong with these instances?

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

If you can provide a method to reproduce this issue I'd advise posting to 
the issue tracker . There 
aren't any reported issues with sys.path or endpoints of a similar nature 
to what you're describing, and it's not likely much info can be gleaned 
from an instance ID for a deleted instance.

On Friday, March 17, 2017 at 5:39:47 AM UTC-4, Ivo Bellin Salarin wrote:
>
> Hi all,
>
> I am stuck on a curious problem.
>
> My application is getting a AttributeError: 'module' object has no 
> attribute 'users_id_token'.
> (The ‘module’ is endpoints. You certainly know that there are several 
> versions of endpoints, certains including users_id_token, others not.For 
> this reason, the problem loooks very similar to a sys.path issue.)
>
> The full stack is pretty similar to:
>
> AttributeError: 'module' object has no attribute 'users_id_token'
> at  
> (/base/data/home/apps/s~project/frontprocess:3-24.399581252568876895/server/authentication/custom_bearer.py:173)
> at  
> (/base/data/home/apps/s~project/frontprocess:3-24.399581252568876895/server/authentication/authentication_manager.py:2)
> at  
> (/base/data/home/apps/s~project/frontprocess:3-24.399581252568876895/server/base_handler.py:53)
> at  
> (/base/data/home/apps/s~project/frontprocess:3-24.399581252568876895/server/content/community/community_task.py:8)
> at  
> (/base/data/home/apps/s~project/frontprocess:3-24.399581252568876895/server/main.py:12)
>
> What’s strange, with such stack, is its statistical distribution. In the 
> last 10 days, more than 3200 instances have successfully processed more 
> than 6.5M requests having a similar stack. On this set, 9 instances have 
> failed processing about 5k requests (the 80% of the requests they processed)
>
> The instances failing those requests were:
>
> 00c61b117cff0b098bf102c264f02fed721dc3914cb9b6f989b0febfea8a8609b3ecb07922
> 00c61b117c9db2974268ab5c147236fbe41640a3c1cf526ce93aa8072eb683cbef9c38c4740236
> 00c61b117cd8f7454ef9756c275a9e7b522c7a35920a462ef6770a99a29439ab3dcd434462dd05
> 00c61b117cf67bff1251a6baaef4d398923c6aef0cf668a24edf04c3628a2e0c5e8f042e6c335636
> 00c61b117cb382e1d3e301c42754c742977859cd66b4c62cd8caf1072611a4eb3bc6a7fbca56b001
> 00c61b117c575699b48ea66920ac9b04c7b928fb6d4ecac51c30db4489bb90d456e7d90567c2c4
> 00c61b117c4277b3ad1c978bbee348f7b57507b33d3213265f4a46f4224a17dbeeb892b1f9c172
> 00c61b117cb4fef51ceef5852aa20183d1539961c35dcd79077c24c2c88f04abe493d171e8b139
> 00c61b117cdd6c72dccb980afbb00d58229128beaf2166bfc1b307517492b74daeef26089b99
>
> Well, those instances do not exist anymore. The issue is not happening 
> anymore since 3/16/17 @ 1h17.
>
>
> But, what did have in common all the instances above? Why were they 
> failing?
> ​
>

-- 
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/5d4a7a25-8066-4bd6-a48a-0819b82dae6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Have been using Firebase for 6months, completely unreliable, holding our prod system hostage

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

You might have better luck posting in the Firebase Google Group 
 rather than on 
Google App Engine, as that is where Firebase support are active.

On Friday, March 17, 2017 at 8:43:42 AM UTC-4, Shubham Maheshwari wrote:
>
> The following was working perfectly for months. 
> The code has recently started to break for the past few days without any 
> changes on app side. Most probably Firebase broke something on their end 
> and already logged in users have started to throw the following errors. 
>
> Firebase support is completely unresponsive, so asking it here. 
> Anybody still stuck on Firebase Please Help. 
>
>
> Code Used: 
>
> FirebaseUser user = FirebaseAuth.getInstance().getCurrentUser(); 
> if(user == null && 
> !OAuth2Utilities.isBlocked(context)){   
> OAuth2Utilities.initAnonymousFirebaseAccount(context.getApplicationContext());
>  
>
> return null; 
> } 
> String userId = user.getUid(); 
> Task z1 = user.getToken(false);//true means it 
> force refreshes the token, false means will update only if expired-- token 
> by default expires in an hour 
> try { 
> Tasks.await(z1); 
> } catch (Exception e) { 
> e.printStackTrace(); 
> } 
> final String z2 = z1.getResult().getToken(); 
>
>
>
>
>
>
>
> W/DynamiteModule: Local module descriptor class for 
> com.google.firebase.auth not found. 
> W/DynamiteModule: Local module descriptor class for 
> com.google.firebase.auth not found. 
> W/System.err: java.util.concurrent.ExecutionException: 
> com.google.firebase.auth.FirebaseAuthInvalidUserException: The user's 
> credential is no longer valid. The user must sign in again. 
> W/System.err: at com.google.android.gms.tasks.Tasks.zzb(Unknown 
> Source) 
> W/System.err: at com.google.android.gms.tasks.Tasks.await(Unknown 
> Source) 
> W/System.err: at 
> *private*.OAuth2Utilities.getFundaForOAuth2(OAuth2Utilities.java:52) 
> W/System.err: at 
> *private*.AsyncTask.PostFetchAsyncTask.doInBackground(PostFetchAsyncTask.java:60)
>  
>
> W/System.err: at 
> *private*.AsyncTask.PostFetchAsyncTask.doInBackground(PostFetchAsyncTask.java:48)
>  
>
> W/System.err: at android.os.AsyncTask$2.call(AsyncTask.java:288) 
> W/System.err: at 
> java.util.concurrent.FutureTask.run(FutureTask.java:237) 
> W/System.err: at 
> android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231) 
> W/System.err: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
>  
>
> W/System.err: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
>  
>
> W/System.err: at java.lang.Thread.run(Thread.java:818) 
> W/System.err: Caused by: 
> com.google.firebase.auth.FirebaseAuthInvalidUserException: The user's 
> credential is no longer valid. The user must sign in again. 
> W/System.err: at com.google.android.gms.internal.zzago.zzew(Unknown 
> Source) 
> W/System.err: at com.google.android.gms.internal.zzagl$zzg.zza(Unknown 
> Source) 
> W/System.err: at com.google.android.gms.internal.zzagw.zzex(Unknown 
> Source) 
> W/System.err: at 
> com.google.android.gms.internal.zzagw$zza.onFailure(Unknown Source) 
> W/System.err: at 
> com.google.android.gms.internal.zzagr$zza.onTransact(Unknown Source) 
> W/System.err: at android.os.Binder.execTransact(Binder.java:446)
>

-- 
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/5b6d9344-74aa-454e-aa36-21ac747af7b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

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

Try adding -Duser.timezone=UTC to your list of Maven command line arguments 
when starting the development server. If the timezone is different this 
looks like it could be a recurrence of an issue that was reported 4 years 
ago on Stack Overflow <http://stackoverflow.com/a/13271024/3953357>, but 
should have been fixed since then. It may also help to know what version of 
the Cloud SDK and App Engine SDK you're using.

On Friday, March 10, 2017 at 11:58:32 PM UTC-5, Yashavanta S B wrote:
>
> The issue is still there, even without setting the default time zone to 
> GMT+00:00 in the ServletContextLIstener. Servlet is showing different 
> timezone in development server.
>
> On Wednesday, March 8, 2017 at 12:59:54 AM UTC+5:30, Adam (Cloud Platform 
> Support) wrote:
>>
>> The development server time zone also defaults to UTC, so the solution is 
>> to not try to change it to anything and instead write your code to work the 
>> same way in production and development (that is, to deal with times that 
>> are in UTC).
>>
>> On Tuesday, March 7, 2017 at 12:30:20 AM UTC-5, Yashavanta S B wrote:
>>>
>>> Thank you for the information. But my question is - why it is showing 
>>> the different time zone in servlets and filters, even when we are setting 
>>> the default time zone to GMT+00:00. The issue is with the local development 
>>> server. But in the production server it is fine.
>>>
>>> On Monday, March 6, 2017 at 1:01:11 PM UTC+5:30, Anastasios Hatzis wrote:
>>>>
>>>> There are really good reasons why an app should not change timezones on 
>>>> the server and why to store all datetimes in UTC. This is especially true 
>>>> in all distributed systems. The app must be designed in a way that it can 
>>>> convert from/to UTC while exchanging data with the outside world or only 
>>>> where it really needs to calculate with local timezones. I don't 
>>>> understand, why you would want to test a different date behavior in 
>>>> development server. Even if it would be possible in dev server, you can be 
>>>> sure that the app will break once it is deployed.
>>>>
>>>> On Monday, 6 March 2017 06:20:22 UTC+1, Yashavanta S B wrote:
>>>>>
>>>>> Thanks for the reply.
>>>>>
>>>>> What about in development server? Can we change the app-engine time 
>>>>> zone in development server? Because we want to test date behavior for 
>>>>> different time zones and we are facing the difficulties in testing the 
>>>>> different time zone dates.
>>>>>
>>>>> On Sunday, March 5, 2017 at 3:44:33 AM UTC+5:30, Adam (Cloud Platform 
>>>>> Support) wrote:
>>>>>>
>>>>>> The timezone in App Engine is always set to UTC and cannot be 
>>>>>> changed. You'll need to convert between UTC and the timezone you wish to 
>>>>>> use. You can refer to one of the numerous existing threads 
>>>>>> <https://www.google.ca/search?q=app+engine+set+timezone> on the 
>>>>>> subject for more background.
>>>>>>
>>>>>> On Friday, March 3, 2017 at 11:48:41 PM UTC-5, Yashavanta S B wrote:
>>>>>>>
>>>>>>> Hey,
>>>>>>>
>>>>>>> In ServletContextListener initialization method we are setting the 
>>>>>>> JVM Time Zone as
>>>>>>>
>>>>>>> public void contextInitialized(ServletContextEvent event) {
>>>>>>> TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
>>>>>>> }
>>>>>>>
>>>>>>> But when i check the Time Zone information in servlets and filters 
>>>>>>> the Time Zone got changed.
>>>>>>>
>>>>>>> log.info("TimeZone : " + TimeZone.getDefault());
>>>>>>>
>>>>>>> What might be the reason? 
>>>>>>>
>>>>>>> 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/2e509b12-714d-443e-901f-e4ba5d205b4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to configure IP and Port in App engine Java Environment, And How to Receive Data on that Port in GAE Application.

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

This question suggests you're just starting out, so I'd advise before 
trying to build anything to first familiarize yourself with the 
documentation  to understand 
how App Engine works. App Engine does not have a single instance 
with
 
a static IP address, and you cannot listen on a socket 

 
in App Engine, only connect to outbound sockets. All inbound traffic to App 
Engine is HTTP(S) traffic which is directed through a front-end 
(appspot.com or via your own custom domain name).

If you're looking for an environment where you have a single machine with a 
static IP which you can connect you, I'd suggest looking at Google Compute 
Engine .

On Saturday, March 11, 2017 at 11:11:02 AM UTC-5, sandeep negi wrote:
>
> How to configure IP and Port in App engine Java Environment, And How to 
> Receive Data on that Port in GAE Application.
>

-- 
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/f1836c80-2b52-4cf7-91fb-85c0ad0ed5cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: HTTP Cloud load Balancer 502 intermittent responses , doesn’t let request reach our backend services

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

I've posted a response to the public issue you filed 
at https://issuetracker.google.com/36144028, please feel free to direct any 
replies there.

On Friday, March 10, 2017 at 8:00:37 AM UTC-5, Jorge Barrachina wrote:
>
> Description of the problem :
>
> HTTP Cloud load Balancer 502 intermittent responses ,  doesn’t let request 
> reach our backend services. It seems that this problem rise up randomly . 
> Maybe related with 
> https://groups.google.com/forum/#!topic/google-appengine-downtime-notify/C_fCwHb73wc
>
> issued on February, 4th? 
>
> Also, we were looking for alternative solutions and we’ve found this post 
> , that maybe has some correlation with this issue, and bring some light to 
> find what happened
>
>
> https://blog.percy.io/tuning-nginx-behind-google-cloud-platform-http-s-load-balancer-305982ddb340#.rw4tbv6gl
>
>
>
> Issue date periods:
>
> March 9th, from 14:12:29.697 ( UTC/GMT +1 hour ) till  March 10th, 
> 09:28:36.085 ( UTC/GMT +1 hour )
>
> Projects affected : 
>
> oa-staging
>
> Services affected:
>
> clientaccount ( versions:  release-2017-10-a , release-2017-8-a , 
> release-2017-07-a)
>
>
> Service url :
>
> https://clientaccount-dot-oa-staging.appspot-preview.com
>
>
> Deployment Details of our stack :
>
>
> app.yaml 
>
> api_version: 1
>
> service: clientaccount
>
> runtime: python
>
> env: flex
>
> entrypoint: gunicorn 'client_account.wsgi:load_app("prod")'
>
> runtime_config:
>
>  python_version: 3
>
> automatic_scaling:
>
>  min_num_instances: 1
>
>  max_num_instances: 5
>
>  cool_down_period_sec: 120 # default value
>
>  cpu_utilization:
>
>target_utilization: 0.8
>
>
> requirements.txt
>
> bingads==v10.4.11
>
> boto3==1.3.0
>
> botocore==1.4.10
>
> docutils==0.12
>
> Flask==0.10.1
>
> Flask-Cors==2.1.2
>
> Flask-Security==1.7.5
>
> flask-swagger==0.2.12
>
> gcloud==0.13.0
>
> google-api-python-client==1.5.0
>
> googleads==5.0.0
>
> gunicorn==19.4.1
>
> itsdangerous==0.24
>
> Jinja2==2.8
>
> jmespath==0.9.0
>
> MarkupSafe==0.23
>
> mongoengine==0.10.6
>
> pymongo==3.2.2
>
> python-dateutil==2.5.2
>
> PyYAML==3.11
>
> recurly==2.4.2
>
> requests==2.9.1
>
> sendgrid==3.0.1
>
> six==1.10.0
>
> Werkzeug==0.11.4
>
> wheel==0.24.0
>
>
> Transaction Example Details :
>
>
> If you want to check the transaction on Google Cloud Console , here is the 
> link to check it out :
>
>
>
> https://console.cloud.google.com/logs/viewer?project=oa-staging=es=0=false=http_load_balancer=resource.type%3D%22http_load_balancer%22%0Aresource.labels.zone%3D%22global%22%0Aresource.labels.project_id%3D%22oa-staging%22%0Atimestamp%3D%222017-03-09T15:35:43.842872262Z%22%0AinsertId%3D%221snolhbg22kclfq%22=2017-03-09T15:35:43.842872262Z
>
> GET  
> https://clientaccount-dot-oa-staging.appspot-preview.com/check_token/**LONG_TOKEN*
>
>
> This request arrives to the HTTP Cloud Load Balancer  at : 16:35:43.842 
> (Madrid Time)
>
>
> Trace Log of the HTTP Cloud Balancer
>
> {
>
> insertId: "1snolhbg22kclfq"   
>
> jsonPayload: {
>
>  statusDetails: "failed_to_connect_to_backend"
>
>  @type: "
> type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry" 
>
>
> }
>
> httpRequest: {
>
>  requestMethod: "GET"
>
>  requestUrl: "
> https://clientaccount-dot-oa-staging.appspot-preview.com/check_token/*LONG_TOKEN*;
>  
>
>
>  requestSize: "1370"
>
>  status: 502
>
>  responseSize: "421"
>
>  remoteIp: "34.197.229.75"
>
> }
>
> resource: {
>
>  type: "http_load_balancer"
>
>  labels: {
>
>   url_map_name: "" 
>
>   forwarding_rule_name: "" 
>
>   backend_service_name: "" 
>
>   target_proxy_name: "" 
>
>   zone: "global" 
>
>   project_id: "oa-staging" 
>
>  }
>
> }
>
> timestamp: "2017-03-09T15:35:43.842872262Z"   
>
> severity: "WARNING"   
>
> logName: "projects/oa-staging/logs/requests"   
>
> }
>
>
> The connection with our backend ( 
> https://clientaccount-dot-oa-staging.appspot-preview.com ) stopped . If 
> you look into the jsonPayload of the trace provided , it says 
> “failed_to_connect_to_backend” so it means that our backend seems to be 
> not processing the request arriving from the http load balancer. 
>
> This is weird , because we didn’t change our stack and it was working days 
> before of the date reported.
>
> Could you tell us what happened , our provide some logs to review with our 
> team.
>
> Thanks for your support
>
>

-- 
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/76d8a4b1-52cf-4423-9261-4b1bfef8127a%40googlegroups.com.
For more options, visit 

[google-appengine] Re: Is cron.yaml supported with custom runtimes?

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

There's another doc which goes into more detail about these steps for the 
flexible runtime, Scheduling Jobs with cron.yaml 
<https://cloud.google.com/appengine/docs/flexible/java/scheduling-jobs-with-cron-yaml>
.

On Wednesday, March 8, 2017 at 6:30:22 AM UTC-5, Ben Rometsch wrote:
>
> Ah thats what I needed - that works now. Thanks. Feels like the 
> custom/flex VM documentation could do with being fleshed out a bit? 
>
> On Tuesday, 7 March 2017 23:47:15 UTC, Adam (Cloud Platform Support) wrote:
>>
>> I've tested this on an openjdk test app and it works fine, using a 
>> cron.yaml similar to yours (hitting an endpoint on the default 
>> version/service every 1 minute).
>>
>> Make sure that you're actually deploying your cron configuration with 
>> 'gcloud 
>> app deploy /path/to/cron.yaml'. Also make sure that you're targeting the 
>> correct version / service. If your endpoint exists on a different version / 
>> service that the default you'll need to specify the 'target: ' 
>> <https://cloud.google.com/appengine/docs/flexible/go/scheduling-jobs-with-cron-yaml#about>
>>  
>> definition in your cron.yaml.
>>
>> On Monday, March 6, 2017 at 5:44:08 PM UTC-5, Adam (Cloud Platform 
>> Support) wrote:
>>>
>>> The docs 
>>> <https://cloud.google.com/appengine/docs/flexible/java/dev-java-only> 
>>> do suggest that cron.yaml should work on the OpenJDK runtime. I'll 
>>> investigate this more and update the thread once I've finished testing. 
>>>
>>> On Sunday, March 5, 2017 at 4:03:23 AM UTC-5, Ben Rometsch wrote:
>>>>
>>>> Hmm I tried extending FROM gcr.io/google_appengine/openjdk but it's 
>>>> still not working. Any ideas? How does the cron.yaml get processed 
>>>> included 
>>>> into the Appengine backend?
>>>>
>>>> On Saturday, 4 March 2017 14:19:23 UTC, Ben Rometsch wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm running a custom Docker runtime on flexible VMs. I have an 
>>>>> cron.yaml file in my root dir that looks like:
>>>>>
>>>>> cron:
>>>>> - description: daily summary job
>>>>>   url: /tasks/test
>>>>>   schedule: every 1 minutes
>>>>>
>>>>> It's not being run. Is cron.yaml supported in custom Docker runtimes? 
>>>>> The documentation doesn't make any reference. 
>>>>>
>>>>> 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/1193d204-fc4a-4ba4-b203-17e983617cc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Is cron.yaml supported with custom runtimes?

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

I've tested this on an openjdk test app and it works fine, using a 
cron.yaml similar to yours (hitting an endpoint on the default 
version/service every 1 minute).

Make sure that you're actually deploying your cron configuration with 'gcloud 
app deploy /path/to/cron.yaml'. Also make sure that you're targeting the 
correct version / service. If your endpoint exists on a different version / 
service that the default you'll need to specify the 'target: ' 
<https://cloud.google.com/appengine/docs/flexible/go/scheduling-jobs-with-cron-yaml#about>
 
definition in your cron.yaml.

On Monday, March 6, 2017 at 5:44:08 PM UTC-5, Adam (Cloud Platform Support) 
wrote:
>
> The docs 
> <https://cloud.google.com/appengine/docs/flexible/java/dev-java-only> do 
> suggest that cron.yaml should work on the OpenJDK runtime. I'll investigate 
> this more and update the thread once I've finished testing. 
>
> On Sunday, March 5, 2017 at 4:03:23 AM UTC-5, Ben Rometsch wrote:
>>
>> Hmm I tried extending FROM gcr.io/google_appengine/openjdk but it's 
>> still not working. Any ideas? How does the cron.yaml get processed included 
>> into the Appengine backend?
>>
>> On Saturday, 4 March 2017 14:19:23 UTC, Ben Rometsch wrote:
>>>
>>> Hi,
>>>
>>> I'm running a custom Docker runtime on flexible VMs. I have an cron.yaml 
>>> file in my root dir that looks like:
>>>
>>> cron:
>>> - description: daily summary job
>>>   url: /tasks/test
>>>   schedule: every 1 minutes
>>>
>>> It's not being run. Is cron.yaml supported in custom Docker runtimes? 
>>> The documentation doesn't make any reference. 
>>>
>>> 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/c9113141-cc14-443d-a19f-f17fc2488d7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

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

The development server time zone also defaults to UTC, so the solution is 
to not try to change it to anything and instead write your code to work the 
same way in production and development (that is, to deal with times that 
are in UTC).

On Tuesday, March 7, 2017 at 12:30:20 AM UTC-5, Yashavanta S B wrote:
>
> Thank you for the information. But my question is - why it is showing the 
> different time zone in servlets and filters, even when we are setting the 
> default time zone to GMT+00:00. The issue is with the local development 
> server. But in the production server it is fine.
>
> On Monday, March 6, 2017 at 1:01:11 PM UTC+5:30, Anastasios Hatzis wrote:
>>
>> There are really good reasons why an app should not change timezones on 
>> the server and why to store all datetimes in UTC. This is especially true 
>> in all distributed systems. The app must be designed in a way that it can 
>> convert from/to UTC while exchanging data with the outside world or only 
>> where it really needs to calculate with local timezones. I don't 
>> understand, why you would want to test a different date behavior in 
>> development server. Even if it would be possible in dev server, you can be 
>> sure that the app will break once it is deployed.
>>
>> On Monday, 6 March 2017 06:20:22 UTC+1, Yashavanta S B wrote:
>>>
>>> Thanks for the reply.
>>>
>>> What about in development server? Can we change the app-engine time zone 
>>> in development server? Because we want to test date behavior for different 
>>> time zones and we are facing the difficulties in testing the different time 
>>> zone dates.
>>>
>>> On Sunday, March 5, 2017 at 3:44:33 AM UTC+5:30, Adam (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> The timezone in App Engine is always set to UTC and cannot be changed. 
>>>> You'll need to convert between UTC and the timezone you wish to use. You 
>>>> can refer to one of the numerous existing threads 
>>>> <https://www.google.ca/search?q=app+engine+set+timezone> on the 
>>>> subject for more background.
>>>>
>>>> On Friday, March 3, 2017 at 11:48:41 PM UTC-5, Yashavanta S B wrote:
>>>>>
>>>>> Hey,
>>>>>
>>>>> In ServletContextListener initialization method we are setting the JVM 
>>>>> Time Zone as
>>>>>
>>>>> public void contextInitialized(ServletContextEvent event) {
>>>>> TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
>>>>> }
>>>>>
>>>>> But when i check the Time Zone information in servlets and filters the 
>>>>> Time Zone got changed.
>>>>>
>>>>> log.info("TimeZone : " + TimeZone.getDefault());
>>>>>
>>>>> What might be the reason? 
>>>>>
>>>>> 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/d79d9e67-76af-4f4e-b127-4557115a5e61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

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

Datastore query times are not guaranteed to be consistent, as Datastore is 
a shared, distributed service. Since you're performing 4 equality filters 
this can add to the variation.

The question of how to optimize for speed is a bit broad and depends on 
your data model. With that being said I can offer a few general suggestions:

1) You can speed up queries, trading extra storage and write costs, by 
defining manual indexes on properties which are frequently queried. See 
Datastore 
Indexes 
 
for more details on this as well as the related document Index Selection 
and Advanced Search 
. .

2) Related to the above, if you only need to fetch a subset of properties 
instead of the whole entity you can define indexes on those properties and 
use Projection Queries 
,
 
which improves speed by fetching from the index instead of the entity.

3) Use Objectify 
.
 
Objectify will automatically cache entities in Memcache 
, and will 
perform a keys-only query + cached get-by-key when possible (also called a 
"hybrid" query 
). 
Initial queries will be slower with this method but subsequent queries will 
be significantly faster as the entities will be pulled from Memcache.

4) Try to reduce the actual number of queries to the Datastore if possible. 
There are a pair of answers on Stack Overflow asked by the same user which 
mention two strategies for this. One is denormalization 
,
 
which refers to intentionally duplicating properties across different 
entities (trading more storage for speed). Another is to prefetch and store 
in memory 

 
the results of a query on one kind and use it as a lookup for another 
(which offloads some of the filtering from the Datastore to your 
application, which can be faster in certain situations).

5) If possible, alter your data model to reduce the number of filters 
required for a query. For example, you may not need to have one entity with 
several foreign key relationships and instead be able split it into 
different entities / queries.

On Sunday, March 5, 2017 at 11:12:53 AM UTC-5, Arjunkumar Udainath wrote:
>
> My replies take a long time to get posted here since I'm new. 
>
> My application is written in Java and instance class of my app is F4. 
> There are a total of 922,758 entities of that Kind in the Datastore.
>
> Here's the function:
>
> public static Map  getEntitiesUsingQueryCursor( String kind 
> , int limit , int chunkSize , String currentCursor, String account, String 
> user, Boolean status, String dept ) throws Exception
> {
>
> String nextCursor = null;
>
> Entity entity = null;
>
> List  listOfEntity = new ArrayList ();
>
> Map  result = new HashMap ();
>
>
> DatastoreService datastore = 
> DatastoreServiceFactory.getDatastoreService();
> com.google.appengine.api.datastore.Query q = new 
> com.google.appengine.api.datastore.Query( kind );
>
> List  listOfFilter = new ArrayList ();
> Filter filter1 = new FilterPredicate( "accountID" , FilterOperator.EQUAL ,  
> account);
> Filter filter2 = new FilterPredicate( "assigneeID" , FilterOperator.EQUAL ,  
> user);
> Filter filter3 = new FilterPredicate( "departmentID" , FilterOperator.EQUAL , 
>  dept);
> Filter filter4 = new FilterPredicate( "open" , FilterOperator.EQUAL ,  
> status); //Boolean
> listOfFilter.add( filter1 );
> listOfFilter.add( filter2 );
> listOfFilter.add( filter3 );
> listOfFilter.add( filter4 );
> Filter filterParams1 = filterParams = CompositeFilterOperator.and( 
> listOfFilter );
> q.setFilter( filter );
>
> PreparedQuery pq = datastore.prepare( q );
> FetchOptions fetchOptions = 
> FetchOptions.Builder.withLimit(limit).prefetchSize( chunkSize ).chunkSize( 
> chunkSize );// limit & chunksize - 500
>
> if ( !StringUtil.isBlank( currentCursor ) )
> fetchOptions.startCursor( Cursor.fromWebSafeString( 
> currentCursor ) );
>
> QueryResultIterable  results = pq.asQueryResultIterable( 
> fetchOptions );
> QueryResultIterator  iterator = results.iterator();
>
> while ( iterator.hasNext() )
> {
> entity = iterator.next();
> listOfEntity.add( entity );
> }
>
> if(listOfEntity.size() == limit)
> nextCursor 

[google-appengine] Re: Is cron.yaml supported with custom runtimes?

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

The docs 
 do 
suggest that cron.yaml should work on the OpenJDK runtime. I'll investigate 
this more and update the thread once I've finished testing. 

On Sunday, March 5, 2017 at 4:03:23 AM UTC-5, Ben Rometsch wrote:
>
> Hmm I tried extending FROM gcr.io/google_appengine/openjdk but it's still 
> not working. Any ideas? How does the cron.yaml get processed included into 
> the Appengine backend?
>
> On Saturday, 4 March 2017 14:19:23 UTC, Ben Rometsch wrote:
>>
>> Hi,
>>
>> I'm running a custom Docker runtime on flexible VMs. I have an cron.yaml 
>> file in my root dir that looks like:
>>
>> cron:
>> - description: daily summary job
>>   url: /tasks/test
>>   schedule: every 1 minutes
>>
>> It's not being run. Is cron.yaml supported in custom Docker runtimes? The 
>> documentation doesn't make any reference. 
>>
>> 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/51600a75-ed39-4b23-ab9f-9b0d9380ca02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore String length limit of 1,500 bytes when using JDO

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

There's no special JDO extension for Datastore that will automatically 
treat a String as Text, unfortunately. Even if there was, setting 
'unindexed' for a String property wouldn't be a big enough hint to treat it 
as Text, because there's still a difference in Datastore between an 
unindexed String property and a Text property. If you want to persist a 
Text property in JDO, the way to do it is:

@Persistent
private Text meterOptions;

On Friday, March 3, 2017 at 1:15:26 PM UTC-5, Jim wrote:
>
> Nick,
>
> When I'm using the Datastore Console to manually update the table it will 
> throw an error related to the index if I have the indexing turned on for 
> the field and try to store a large value.  When I turn indexing off I am 
> able to store large strings through the console.
>
> In my Java/JDO code I am unable to store large values under either 
> indexing condition.  I have my class annotated to turn indexing off like 
> this:
>
> @Persistent
> @Extension(vendorName="datanucleus", key="gae.unindexed", value="true")
> private String meterOptions;
>
> Jim
>
>
>
> On Thursday, March 2, 2017 at 5:57:41 PM UTC-6, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Jim,
>>
>> Do I understand correctly that you only see the issue when you attempt to 
>> index the field - or what's the same thing - it doesn't occur when you turn 
>> the field's indexing off? 
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, March 2, 2017 at 1:26:02 PM UTC-5, Jim wrote:
>>>
>>> When I attempt to write a Datastore string longer than 1,500 bytes via 
>>> JDO I get the following error:   "String properties must be 1500 bytes or 
>>> less.  Instead, use com.google.appengine.api.datastore.Text, which can 
>>> store strings of any length."
>>>
>>> I've annotated my class to turn indexing off on this field, and I can 
>>> manually insert strings (much) longer than 1,500 bytes manually via the 
>>> Datastore Console.  
>>>
>>> Is there any way to store larger String values via JDO?  It seems like 
>>> an arbitrary limitation given the fact that I can manually insert larger 
>>> values into the Datastore, and Datastore doc says Strings can be up to ~1MB 
>>> in size.  I know I can convert these to Text but I'd rather not do that if 
>>> I can avoid it.
>>>
>>

-- 
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/8c1bda79-a473-4507-985e-521a76ae8d45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

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

Can you let us know what language runtime you're using, preferably with a 
sample of code which shows your query and fetch options?

On Saturday, March 4, 2017 at 12:01:57 PM UTC-5, Arjunkumar Udainath wrote:
>
> I have an app that's sort of like a to-do application. Any given user 
> would have "Tasks" that are pending at any given time. The number of tasks 
> pending for a user can range from 0 to 5000. I need to fetch the pending 
> tasks (or at least a small batch) for each user when they load the page.
>
> How do I make sense of these latencies:
>
> *Scenario 1:*
>
> User A: Has 2500 pending tasks. The query limit is 500 and results fetched 
> on the first request are obviously 500. Time taken: 5767 milliseconds (5.7 
> seconds).
>
> User B: Has 2 pending tasks. The query limit is 500 and results fetched on 
> the first request are obviously 2. Time taken: 7124 milliseconds (7.1 
> seconds).
>
> *Scenario 2:*
>
> User A: Has 2500 pending tasks. The query limit is 10 and results fetched 
> on the first request are obviously 10. Time taken: ~400 milliseconds (1/2 
> second).
>
> User B: Has 2 pending tasks. The query limit is 10 and results fetched on 
> the first request are obviously 2. Time taken: 5-6 seconds.
> I thought I could speed up the query if I knew what the limit would be for 
> users with fewer than 500. So there is a user with 551 tasks. Here's what 
> happened:
>
> *Scenario 3:*
>
> User A: Has 2500 pending tasks. The query limit is 551 and results fetched 
> on the first request are obviously 551. Time taken: 6251 milliseconds (6 
> seconds).
>
> User B: Has 551 pending tasks. The query limit is 551 and results fetched 
> on the first request are obviously 551. Time taken: 13053 milliseconds (13 
> seconds).
>
> I can't find a pattern here. How do I optimize my queries so that users 
> with less data can get their pages loaded quickly.
>

-- 
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/c70e9915-3c0a-46bb-912d-48ab1877063e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Is cron.yaml supported with custom runtimes?

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

Are you using a base image in your Dockerfile that is an App Engine 
runtime? If you use a non-App Engine base image, the App Engine Cron 
Service will not be available.

On Saturday, March 4, 2017 at 2:55:11 PM UTC-5, Ben Rometsch wrote:
>
> Its a Java/Docker/FlexVM app not a standard Python appengine app...?
>
> On Saturday, 4 March 2017 14:46:41 UTC, Nickolas Daskalou wrote:
>>
>> Have you updated your crons with something like this?
>>
>> > appcfg.py update_cron dir_with_cron_file?
>>
>> See here for more info:
>>
>>
>> https://cloud.google.com/appengine/docs/standard/python/tools/appcfg-arguments#update_cron
>>
>> You'll also need to ensure the /tasks/test URL is routed to your Flex 
>> environment service, either as the "default" service or via routing rules 
>> in dispatch.yaml (which you can upload with appcfg.py also).
>>
>> Nick
>> On 05/03/2017 1:19 AM, "Ben Rometsch"  wrote:
>>
>>> Hi,
>>>
>>> I'm running a custom Docker runtime on flexible VMs. I have an cron.yaml 
>>> file in my root dir that looks like:
>>>
>>> cron:
>>> - description: daily summary job
>>>   url: /tasks/test
>>>   schedule: every 1 minutes
>>>
>>> It's not being run. Is cron.yaml supported in custom Docker runtimes? 
>>> The documentation doesn't make any reference. 
>>>
>>> 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-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@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/fb9f299d-0f96-45d7-864f-513cffc4f70d%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/ad591ef8-e37d-4c7a-977b-f887b89bbdff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

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

The timezone in App Engine is always set to UTC and cannot be changed. 
You'll need to convert between UTC and the timezone you wish to use. You 
can refer to one of the numerous existing threads 
 on the subject for 
more background.

On Friday, March 3, 2017 at 11:48:41 PM UTC-5, Yashavanta S B wrote:
>
> Hey,
>
> In ServletContextListener initialization method we are setting the JVM 
> Time Zone as
>
> public void contextInitialized(ServletContextEvent event) {
> TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
> }
>
> But when i check the Time Zone information in servlets and filters the 
> Time Zone got changed.
>
> log.info("TimeZone : " + TimeZone.getDefault());
>
> What might be the reason? 
>
> 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/654a561f-3af9-46e0-9e7a-ac303a6fae8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Uploading large image files and video to Google Cloud Storage

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

Glad to hear you got it working. Regarding my last response, it's not an 
issue in that its a bug that needs to be fixed, I meant that it's an issue 
that people encounter when doing resumable uploads with the JSON API. The 
behavior is mentioned in the callout in the CORS documentation 
 as well as in point 8 in the troubleshooting 
section, though perhaps it can be more clear for example mentioning that it 
expects an OPTIONS preflight request which is normally gets sent by the 
browser for the initial upload, and for this reason (and the fact that the 
origins will be different) it isn't possible to make the initial request on 
the server and pass the resulting location back to the client.

On Wednesday, March 1, 2017 at 4:46:49 PM UTC-5, Richard Cheesmar wrote:
>
> Was just about to turn the computer off after winding down reading some 
> non tech stuff.
>
> I had everything the origin idea. Wow, see what blind crazy fuzzy stress 
> does to the beautiful mind...Messes it right up.
>
> Thanks, appreciated. It works. phew.
>
> On Monday, February 20, 2017 at 6:47:26 PM UTC+3, Richard Cheesmar wrote:
>>
>> I am using the standard python app engine environment and currently 
>> looking at how one goes about uploading multiple large media files to 
>> Google Cloud Storage (Public Readable) using App Engine or the Client 
>> directly (preferred).
>>
>> I currently send a bunch of smaller images (max 20 - between 30 and 100k 
>> on average), at the same time directly via a POST to the server. These 
>> images are provided by the client and put in my projects default bucket. I 
>> handle the requests images using a separate thread and write them one at a 
>> time to the cloud and then associate them with an ndb object. This is all 
>> fine and dandy when the images are small and do not cause the request to 
>> run out of memory or invoke a DeadlineExceededError. 
>>
>> But what is the best approach for large image files of 20mb+ a piece or 
>> video files of up to 1GB in size? Are there efficient ways to do this from 
>> the client directly, would this be possible via the Json api ,a resumable 
>> upload, for example? If so, are there any clear examples of how to do this 
>> purely in javascript on the client? I have looked at the docs but it's not 
>> intuitively obvious at least to me.
>>
>> I have been looking at the possibilities for a day or two but nothing 
>> hits you with a clear linear description or approach. I notice in the 
>> Google Docs there is a way using PHP to upload via a POST direct from the 
>> client...
>> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is 
>> this just relevant to using PHP on app engine or is there an equivalent to 
>> createUploadUrl 
>> for python or javascript?
>>
>>
>> Anyway, I'll keep exploring but any pointers would be greatly appreciated.
>>
>>
>> Cheers
>>
>>

-- 
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/9ab71080-7352-4caf-89c3-a50d7c358b34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Uploading large image files and video to Google Cloud Storage

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

Have a look at this Stack Overflow answer 

 
for more details. This is an issue specific to the JSON API. In your case, 
does the 'Origin: ' header differ from the initial POST and subsequent PUT 
requests?

On Tuesday, February 28, 2017 at 11:40:33 AM UTC-5, Richard Cheesmar wrote:
>
> Update:
>
> Ok, so after much deliberation about how to simplify the approach, finally 
> I get a method together that I think I can live with, but there is still 
> one problem.
>
> What I am doing to upload a video from the client direct (via localhost) 
> is:
>
> 1. I generate an access token and build a POST request for the initial 
> upload request to the JSON api.
> 2. I make the POST call which successfully returns a location.
> 3. I return the location to the client via a json object
> 4. I make the PUT call in the returned location which starts the upload - 
> this is done using standard ajax via Jquery.
> 5. The video is actually arriving at the bucket but the ajax call returns 
> with an error at the end of the upload
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading 
> the remote resource at https://
> www.googleapis.com/upload/storage/v1/b/my-bucket/o?uploadType=resumable=test-vid_id=generate-id.
>  
> (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
>
>
> Seems strange to me as the video actually gets to the bucket...
>
> For the time being I have added the * to CORS headers on the bucket by 
> using the Google Cloud shell and some instructions from here 
> https://bitmovin.com/faq/how-do-i-set-up-cors-for-my-google-cloud-storage-bucket/
> and this all seems fine. Well it must be otherwise the PUT wouldn't put 
> the video, if the CORS headers were not in place.
>
> I have no idea why this is, can someone enlighten me?
>
>
> On Monday, February 20, 2017 at 6:47:26 PM UTC+3, Richard Cheesmar wrote:
>>
>> I am using the standard python app engine environment and currently 
>> looking at how one goes about uploading multiple large media files to 
>> Google Cloud Storage (Public Readable) using App Engine or the Client 
>> directly (preferred).
>>
>> I currently send a bunch of smaller images (max 20 - between 30 and 100k 
>> on average), at the same time directly via a POST to the server. These 
>> images are provided by the client and put in my projects default bucket. I 
>> handle the requests images using a separate thread and write them one at a 
>> time to the cloud and then associate them with an ndb object. This is all 
>> fine and dandy when the images are small and do not cause the request to 
>> run out of memory or invoke a DeadlineExceededError. 
>>
>> But what is the best approach for large image files of 20mb+ a piece or 
>> video files of up to 1GB in size? Are there efficient ways to do this from 
>> the client directly, would this be possible via the Json api ,a resumable 
>> upload, for example? If so, are there any clear examples of how to do this 
>> purely in javascript on the client? I have looked at the docs but it's not 
>> intuitively obvious at least to me.
>>
>> I have been looking at the possibilities for a day or two but nothing 
>> hits you with a clear linear description or approach. I notice in the 
>> Google Docs there is a way using PHP to upload via a POST direct from the 
>> client...
>> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is 
>> this just relevant to using PHP on app engine or is there an equivalent to 
>> createUploadUrl 
>> for python or javascript?
>>
>>
>> Anyway, I'll keep exploring but any pointers would be greatly appreciated.
>>
>>
>> Cheers
>>
>>

-- 
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/26350cef-7d03-4f43-9f1f-b1f08a42f579%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: from .appspot.com to .appspot-preview.com

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

Please see the main Groups thread 
<https://groups.google.com/forum/#!msg/google-appengine/4_2oVbRhMKY/trl938Z1DQAJ>
 
for updates on the redirect issue which provides more details. Traffic will 
be redirected back to "appspot.com" and is only going to 
"appspot-preview.com" on a temporary basis.

On Monday, February 20, 2017 at 1:20:47 PM UTC-5, Zip Zit wrote:
>
> Adam.   that word "preview" makes me very nervous.  It implies that there 
> are limited services, or that the object viewed is not production ready, or 
> the object viewed in this guise is for temporary use only...
>
> What is the catch?  Why did they choose that word? 
>
>
>
>
>
> . On Saturday, February 18, 2017 at 11:25:33 AM UTC-8, Adam (Cloud 
> Platform Support) wrote:
>>
>> A change was made causing some App Engine Flexible apps to redirect to 
>> appspot-preview.com. If you have any client applications that point to 
>> the old domain, you'll need to update them to use the new URL.
>>
>>
>>>

-- 
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/7ac3595d-4e6f-43dd-8c1c-d76e4601969e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Issues with Google Cloud Storage (GCS) client in GAE standard dev environment

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

The current appengine-maven-plugin version is 1.2.0 
, not 
1.1.0-beta1. Do you still experience the same issue on that version?

On Monday, February 27, 2017 at 11:25:32 AM UTC-5, Paul Mazzuca wrote:
>
> After updating to the new appengine-maven-plugin (1.1.0-beta) with groupId 
> com.google.cloud.tools, I am unable to get the GCS client to work in dev 
> mode.  I followed the short documentation @ 
> https://cloud.google.com/appengine/docs/standard/java/googlecloudstorageclient/setting-up-cloud-storage,
>  
> however have been unsuccessful.  This previously worked in the older 
> appengine-maven-plugin.
>
> The error I receive:
>
> [java.io.IOException: java.lang.NoSuchMethodException: 
> com.google.appengine.tools.development.devappserver2.DevAppServer2Delegate.getService(java.lang.String)]
>
>
> This is also mentioned on GitHub 
> https://github.com/GoogleCloudPlatform/app-maven-plugin/issues/106.  
>
>
> Has anyone been able to get gcs to work using the new mvn appengine plugin?
>
>
> Is it true as the documentation suggests that "there is no local emulation 
> of gcs"?  I thought the previous plugin supported local emulation (though I 
> might not have realized it was reaching out to Internet)
>
>
>

-- 
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/73a1c103-24b1-42ea-a9b4-2c2da23055f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Help troubleshooting running under the development server

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

We've seen this error occasionally but reproducing it has been hit or miss. 
I'd advise filing an issue on the googleappengine issue tracker  
and uploading a 
sample app which exhibits the problem. If you provide a link to the issue I 
will pick it up from there.

On Saturday, February 25, 2017 at 12:07:47 PM UTC-5, Kevin Wise wrote:
>
> I have an exceptionally strange situation. My web app, running on Guice in 
> a app engine standard environment, works fine in a development environment 
> on Linux or Mac, but doesn't work on Windows. The symptom is that when I 
> try to run the application, it appears to startup, but then always responds 
> with a 500 error. The log reports:
>
> ERROR2017-02-24 15:06:29,865 http_proxy.py:116] bad runtime process 
> port ['']
> INFO 2017-02-24 15:06:29,964 module.py:806] default: "GET / HTTP/1.1" 
> 500 4379
>
> Even stranger, the server returns *the log file contents to the browser*.  
> Here is a sample of the browser output:
>
> bad runtime process port ['']
>
> Feb 24, 2017 3:04:52 PM 
> com.google.appengine.tools.development.AbstractContainerService configure
> WARNING: Null value for 
> containerConfigProperties.get(devappserver.portMappingProvider)
> Feb 24, 2017 3:04:52 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Logging to JettyLogger(null) via 
> com.google.apphosting.utils.jetty.JettyLogger
> Feb 24, 2017 10:04:52 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: jetty-6.1.x
> Feb 24, 2017 10:05:15 PM org.hibernate.validator.internal.util.Version 
> 
> INFO: HV01: Hibernate Validator 5.2.4.Final
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider as a 
> provider class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.health.HealthCheckResource as a root resource 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.example.appengine.helloworld.HelloResource as a root 
> resource class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.exception.ConflictExceptionMapper as a provider 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.exception.IllegalArgumentExceptionMapper as a 
> provider class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.webjars.JaxRsWebjarsServlet as a root resource 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.19.3 10/24/2016 03:43 
> PM'
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.exception.ConflictExceptionMapper to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.exception.IllegalArgumentExceptionMapper to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.health.HealthCheckResource to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.example.appengine.helloworld.HelloResource to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.webjars.JaxRsWebjarsServlet to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Started SelectChannelConnector@localhost:54117
> Feb 24, 2017 10:05:19 PM 
> com.google.appengine.tools.development.AbstractModule startup
> INFO: Module instance default is running at http://localhost:54117/
> Feb 24, 2017 10:05:19 PM 
> com.google.appengine.tools.development.AbstractModule startup
> INFO: The admin console is running at http://localhost:54117/_ah/admin
> Feb 24, 2017 3:05:55 PM 
> 

[google-appengine] Re: Error When trying to retreive access token from 'https://www.googleapis.com/auth/cloud-platform'

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

Apologies for the frustration. We're aware that docs are a pain point for 
developers and are always working on improving them. Be assured we're 
monitoring threads like these and making note of feedback for future 
iterations of our documentation. Having more recipe style solutions is 
something I'd like to see more of as well (dispense with the verbage and 
show me the code, it will usually explain it much more concisely).

As a general suggestion, a lot of issues and corner cases end up getting 
documented outside of the official docs on the other sites we're active on 
 such as Stack Exchange, 
GitHub, Reddit and the official issue trackers (and of course Google 
Groups). Frequent and targeted use of our namesake search engine is 
encouraged (for instance Googling the two error messages for me leads 
straight to the relevant sources of information on the first hits via Stack 
Overflow). 

On Saturday, February 25, 2017 at 12:26:25 PM UTC-5, Richard Cheesmar wrote:
>
> Update: The fix for the  
>
> HTTPException: Invalid and/or missing SSL certificate for URL:
>
> solution here: 
> https://code.google.com/p/googleappengine/issues/detail?id=13477
>
> was correct, but the cacerts.pem file was corrupted somehow, replacing 
> that again sorted that out properly but didn't resolve the first issue. The 
> first issue noted was because the server time and computer times were out 
> of sync. In my case it is because my computer is in Turkey and Turkey did 
> not change from summertime this year, hence it is out of sync with the rest 
> of the planet! 
>
> Set this to automatic with asian time server and it's ok. 
>
> None, of the reasons above negate my comments on Google Docs though. 
>
> Off to have the other half of the bottle of zanax now.
>  
>
>
> On Saturday, February 25, 2017 at 5:31:22 PM UTC+3, Richard Cheesmar wrote:
>>
>> I have been experimenting with some of the Google Examples, which I have 
>> to say is a bit of a nightmare!
>>
>> I'm following the example here 
>> https://cloud.google.com/appengine/docs/standard/python/appidentity/ to 
>> retrieve an access token on the develoment server (MacOS Sierra) using 
>> Pycharm.
>>
>> I have indeed setup a service account on the Cloud Console, something you 
>> have to scrape around to find out for yourself and it is being retrieved 
>> correctly via 
>>
>> app_identity.get_service_account_name()
>>
>>
>> However, I am getting this error: 
>>
>> *** InternalError: Error getting access token. Response code: 400, 
>> Content: {
>>   "error" : "invalid_grant",
>>   "error_description" : "Invalid JWT: Token must be a short-lived token 
>> and in a reasonable timeframe"
>> }
>>
>> I assume I have provided the service account with the correct permissions 
>> for what I want, which are:
>>
>> Storage Object Creator
>> Storage Object Viewer
>> Service Account Actor which I assume I need to access the token, not 
>> really sure.
>>
>>
>> I would appreciate some direct Google help here or any help from someone 
>> that can give me an answer not a choice of paradigms. I have to say that 
>> the Google Docs are failing dramatically. It is near impossible without 
>> pouring over the stuff for hours to get clear recipe style format for 
>> performing simple tasks. When there is smidgeon of hope it goes down the 
>> toilet fast with an error for example, you set up the service accounts get 
>> your key sorted  run your code and wham:
>>
>> HTTPException: Invalid and/or missing SSL certificate for URL:
>>
>>
>> arrives like a big fat palm to smack you across the kisser. You Google and 
>> Stackoverflow some more, and find out it's a bug with outdated certificates 
>> in the sdk. Great, you fix that, try not to bang your head 
>> against the nearest hard object, because then you won't have a computer to 
>> work on, take a deep breath and run again. The bug above is where you 
>> arrive. 
>>
>> Do us techs a favour Google, if you are going to create software you want us 
>> to use, provide adequate documentation to allow us to use them without 
>> reaching for the damn zanax. Recipies, 
>> and more recipes with clear cut examples. I'm not a technical mystery 
>> detective, I'm a simple minded developer that is fed up to the back teeth of 
>> having to trawl through your min
>> efield of documents just to do some simple
>>
>>

-- 
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/a28305db-c48a-4c0e-854f-e223aa88ea29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Switching from Backends to Modules

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

In your case to deploy the 'reporting' service you would use:

appcfg.py update reporting.yaml

You can list any number of .yaml files for services to deploy after 
'appcfg.py update'. The usage is given in the documentation under *Deploying 
multiple service applications* 

.

On Friday, February 24, 2017 at 10:46:40 AM UTC-5, Joshua Smith wrote:
>
> I have a process I need to let run longer than 10 minutes, and I have been 
> using “backends” for this.
>
> I saw the deprecation warning, so I decided to try making it into a module 
> instead. The documentation on this is a complete mess. Hey google: You need 
> to go clean this up. There are a whole lot of different pages that describe 
> bits and pieces of the puzzle, but I can’t find anything that tells me what 
> I actually need to do. It doesn’t help that backends became modules became 
> services. SMDH.
>
> Anyway, I found the article that told me how to generate a .yaml for my 
> module based on my old backends.yaml and my app.yaml. My module is called 
> “reporting” so I have reporting.yaml.
>
> After making that and deleting my backends.yaml, I clicked deploy on the 
> GAE launcher, but that didn’t do anything about my module.
>
> So I guess I need to run appcfg.py manually? But I have no idea what 
> arguments to give it.
>
> I just want to push the latest code up, and then I will hit the module 
> with a URL.
>
> I used to do this with: appcfg.py backends  update
>
> What command should I issue to get the same result with my “reporting” 
> module?
>
>
> -Joshua
>
>

-- 
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/697eccc5-b17a-4852-8b09-12627d347d10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore connection problem

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

You'd want to ensure that you are correctly setting the emulator 
environment variables with $(gcloud beta emulators datastore env-init) 
after starting it according to the docs 
, however 
even when I do that the bookshelf sample app crashes for me after writing 
one entity. It looks like the sample app doesn't work with the emulator at 
this time (note that nowhere in the tutorial does it actually mention that 
it does).

The tutorial itself is in need of an update in any case, as you see from the 
list of open issues 
on 
its GitHub page. I also needed to manually update the dependencies to get npm 
install to even work.

On Friday, February 24, 2017 at 9:44:32 AM UTC-5, Alexey Gromov wrote:
>
> Hi,
>
> I'm new in the GCP. Now I'm trying to setup my local dev env using Google 
> tutorials.
> I've got a problem with Datastore example 
> "/nodejs-getting-started/2-structured-data". It doesn't work both 
> with/without Datastore Emulator.
> Does anybody know anything about 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 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/f65a414b-1024-4f70-be5f-649c924668ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Uploading large image files and video to Google Cloud Storage

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

To answer your other questions:

1) Does that mean the JSON API will be deprecated at some point?
The documentation mentions using the Google Cloud Storage Client libraries, 
which themselves use the JSON API, so no.

2) Why there is not an equivalent to the CloudStorageTools file upload for 
other languages?
The best answer to this is that the PHP standard runtime was developed 
last, after GCS had a mature API, so better support for GCS was baked in. 
It was never back-ported to the other runtimes.

The docs I linked to originally also mentioned signed URLs, and yes this is 
the only way to upload to GCS directly using an auth scheme that is not not 
Google OAuth (unless you want everything to be public writable).

On Friday, February 24, 2017 at 11:15:38 AM UTC-5, Richard Cheesmar wrote:
>
> Ok, looks like you can only do this with signed requests
>
> On Monday, February 20, 2017 at 5:47:26 PM UTC+2, Richard Cheesmar wrote:
>>
>> I am using the standard python app engine environment and currently 
>> looking at how one goes about uploading multiple large media files to 
>> Google Cloud Storage (Public Readable) using App Engine or the Client 
>> directly (preferred).
>>
>> I currently send a bunch of smaller images (max 20 - between 30 and 100k 
>> on average), at the same time directly via a POST to the server. These 
>> images are provided by the client and put in my projects default bucket. I 
>> handle the requests images using a separate thread and write them one at a 
>> time to the cloud and then associate them with an ndb object. This is all 
>> fine and dandy when the images are small and do not cause the request to 
>> run out of memory or invoke a DeadlineExceededError. 
>>
>> But what is the best approach for large image files of 20mb+ a piece or 
>> video files of up to 1GB in size? Are there efficient ways to do this from 
>> the client directly, would this be possible via the Json api ,a resumable 
>> upload, for example? If so, are there any clear examples of how to do this 
>> purely in javascript on the client? I have looked at the docs but it's not 
>> intuitively obvious at least to me.
>>
>> I have been looking at the possibilities for a day or two but nothing 
>> hits you with a clear linear description or approach. I notice in the 
>> Google Docs there is a way using PHP to upload via a POST direct from the 
>> client...
>> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is 
>> this just relevant to using PHP on app engine or is there an equivalent to 
>> createUploadUrl 
>> for python or javascript?
>>
>>
>> Anyway, I'll keep exploring but any pointers would be greatly appreciated.
>>
>>
>> Cheers
>>
>>

-- 
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/05eed687-b105-4f2b-8679-5da96475fbdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: App Engine Flex Environment custom domain forwarded to appspot-preview.com

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

You can use 'Reply privately to author' from the dropdown to send a private 
message from the thread.

On Wednesday, February 22, 2017 at 9:23:53 AM UTC-5, Nickolas Daskalou 
wrote:
>
> Adam what is your private email address so I can PM you our app details?
>
>
> On 22 February 2017 at 06:30, 'Adam (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> A change was made that caused some App Engine Flexible apps to redirect 
>> to appspot-preview.com. If you're affected please sent me a private 
>> message with your project ID and I'll look into it. 
>>
>> On Tuesday, February 21, 2017 at 1:40:52 AM UTC-5, seongjoo wrote:
>>>
>>> My app setup a custom domain on App Engine Flex Environment. The domain 
>>> is forwarded to appspot-preview.com. Clearly, I don't want this to 
>>> happen.
>>>
>>> I have another with same runtime (nodejs) setup a custom domain but it 
>>> didn't have the problem.
>>>
>>>
>>> -- 
>> 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/0fe3e5bb-77ea-4f0d-a775-cc2f2c3dc70a%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/0fe3e5bb-77ea-4f0d-a775-cc2f2c3dc70a%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> 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/cf401428-b1fa-469a-8fd2-53fccf964fa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine - Inbound Mail Issues/Delays?

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

You should be able to use the 'Reply privately to author' option from the 
dropdown. This issue has already been addressed though. This appeared to be 
caused by mail processing being queued due to a transient load spike. No 
messages were actually lost, and this falls within expected behavior as no 
guarantee is made that the mail handler will always be hit immediately when 
an inbound message is received.

On Friday, February 24, 2017 at 2:45:11 AM UTC-5, Nickolas Daskalou wrote:
>
> Adam how do we get your private email address?
>
> Google Groups is masking it.
>
> Thanks,
> Nick
>
> On Monday, 20 February 2017, 'Adam (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Feel free to send me a private message with your project id and I can 
>> take a look.
>>
>> On Friday, February 17, 2017 at 5:50:30 PM UTC-5, Will Reiher wrote:
>>>
>>> Alex,
>>>
>>> My issue is still not fully resolved today - I've had a couple instances 
>>> today of delayed delivery. 
>>> It's not related to the API it's that mail being sent to the inbound 
>>> @appspotmail address is being delayed before showing up on /_ah/mail and 
>>> hitting my request handler.
>>>
>>> I've triple confirmed that there is no delay from the source but it's 
>>> definitely not getting to my app as quickly as it should. I have logs 
>>> showing when the mail that was "delayed" finally hits my handler I get a 
>>> ton of requests all at once (which is not the way it would have been sent). 
>>> It seems to be an infrastructure issue.
>>>
>>> On Friday, February 17, 2017 at 1:50:00 PM UTC-8, Alex (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> Hi Will,
>>>>
>>>> Glad to hear that your issue was resolved and thanks for updating the 
>>>> thread. For tracking purposes, can you confirm that your issue was related 
>>>> with the App Engine Mail API 
>>>> <https://cloud.google.com/appengine/docs/java/mail/>? Also, it would 
>>>> be great if you could indicate which language was used in the process.
>>>>
>>>> Thanks,
>>>>
>>>> Alex
>>>>
>>> -- 
>> 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/4aea8582-d8a5-46ad-a3c3-0b2dcad73c46%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/4aea8582-d8a5-46ad-a3c3-0b2dcad73c46%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> 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/eebf2003-7974-4431-b88c-b39f59b8e816%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine Flex Environment custom domain forwarded to appspot-preview.com

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

A change was made that caused some App Engine Flexible apps to redirect to 
appspot-preview.com. If you're affected please sent me a private message 
with your project ID and I'll look into it. 

On Tuesday, February 21, 2017 at 1:40:52 AM UTC-5, seongjoo wrote:
>
> My app setup a custom domain on App Engine Flex Environment. The domain is 
> forwarded to appspot-preview.com. Clearly, I don't want this to happen.
>
> I have another with same runtime (nodejs) setup a custom domain but it 
> didn't have the problem.
>
>
>

-- 
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/0fe3e5bb-77ea-4f0d-a775-cc2f2c3dc70a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Uploading large image files and video to Google Cloud Storage

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

The simplest upload option is the POST object call to the XML API 
, which accepts 
form data and allows you to upload a file without any JavaScript using just 
a  tag with the 'action=' attribute set to the Cloud Storage API 
Endpoint, eg.


...

You can of course use an XHR in JavaScript to post the form as well. 
Authentication for this type of upload is done using a policy document, 
which is described in the Usage and Examples 
 
section of the documentation along with Python code examples and an example 
HTML form.

A cleaner approach is to use the Google API JavaScript Client Library 
 
to upload the file using the JSON API 
. There's a JavaScript 
example on the googlearchive GitHub page  
called storage-getting-started-javascript 

 
which I still use as a reference, and is still updated. This will show you 
how to do a multipart upload 
, 
which is sufficient for most files under 5MB. Authentication for this is 
done using OAuth and is handled by the GAPI client.

If you need resumable uploads, it's not too much work to adapt the concepts 
in Performing a Resumable Upload 
, 
which give raw HTTP examples, to the above code example. If you need to do 
some kind of authentication outside of Google OAuth, you can look into Signed 
URLs . 
The documentation also provides Python code samples for generating them 
.
 
Uploading to a signed URL works mostly the same way as for regular GCS 
URLs, with some differences that are covered in the docs.

On Monday, February 20, 2017 at 10:47:26 AM UTC-5, Richard Cheesmar wrote:
>
> I am using the standard python app engine environment and currently 
> looking at how one goes about uploading multiple large media files to 
> Google Cloud Storage (Public Readable) using App Engine or the Client 
> directly (preferred).
>
> I currently send a bunch of smaller images (max 20 - between 30 and 100k 
> on average), at the same time directly via a POST to the server. These 
> images are provided by the client and put in my projects default bucket. I 
> handle the requests images using a separate thread and write them one at a 
> time to the cloud and then associate them with an ndb object. This is all 
> fine and dandy when the images are small and do not cause the request to 
> run out of memory or invoke a DeadlineExceededError. 
>
> But what is the best approach for large image files of 20mb+ a piece or 
> video files of up to 1GB in size? Are there efficient ways to do this from 
> the client directly, would this be possible via the Json api ,a resumable 
> upload, for example? If so, are there any clear examples of how to do this 
> purely in javascript on the client? I have looked at the docs but it's not 
> intuitively obvious at least to me.
>
> I have been looking at the possibilities for a day or two but nothing hits 
> you with a clear linear description or approach. I notice in the Google 
> Docs there is a way using PHP to upload via a POST direct from the client...
> https://cloud.google.com/appengine/docs/php/googlestorage/user_upload...Is 
> this just relevant to using PHP on app engine or is there an equivalent to 
> createUploadUrl 
> for python or javascript?
>
>
> Anyway, I'll keep exploring but any pointers would be greatly appreciated.
>
>
> Cheers
>
>

-- 
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/5e237918-875f-46b6-b18f-133968af5bc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine - Inbound Mail Issues/Delays?

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

Feel free to send me a private message with your project id and I can take 
a look.

On Friday, February 17, 2017 at 5:50:30 PM UTC-5, Will Reiher wrote:
>
> Alex,
>
> My issue is still not fully resolved today - I've had a couple instances 
> today of delayed delivery. 
> It's not related to the API it's that mail being sent to the inbound 
> @appspotmail address is being delayed before showing up on /_ah/mail and 
> hitting my request handler.
>
> I've triple confirmed that there is no delay from the source but it's 
> definitely not getting to my app as quickly as it should. I have logs 
> showing when the mail that was "delayed" finally hits my handler I get a 
> ton of requests all at once (which is not the way it would have been sent). 
> It seems to be an infrastructure issue.
>
> On Friday, February 17, 2017 at 1:50:00 PM UTC-8, Alex (Cloud Platform 
> Support) wrote:
>>
>> Hi Will,
>>
>> Glad to hear that your issue was resolved and thanks for updating the 
>> thread. For tracking purposes, can you confirm that your issue was related 
>> with the App Engine Mail API 
>> ? Also, it would be 
>> great if you could indicate which language was used in the process.
>>
>> Thanks,
>>
>> Alex
>>
>

-- 
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/4aea8582-d8a5-46ad-a3c3-0b2dcad73c46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Play Service Cloud Saving - Reading data

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

You'd probably want to ask this on the Google Play Help Forum 
, as Cloud Saving is 
not part of Google App Engine.

On Friday, February 17, 2017 at 7:51:48 PM UTC-5, Joe Man wrote:
>
>
> I implemented GPS Cloud Save to my game, I was wondering if it is possible 
> to access the user's save data outside of the app?
>
> ie:
> I have a backend server which and I would like to access those save files, 
> is it possible?
>

-- 
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/2bb656aa-7727-4828-ab67-6f5b85a6ea38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Play Service Cloud Saving - Reading data

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

You'd probably want to ask this on the Google Play Help Forum 
, as Cloud Saving is 
not a part of Google App Engine.

On Friday, February 17, 2017 at 7:51:48 PM UTC-5, Joe Man wrote:
>
>
> I implemented GPS Cloud Save to my game, I was wondering if it is possible 
> to access the user's save data outside of the app?
>
> ie:
> I have a backend server which and I would like to access those save files, 
> is it possible?
>

-- 
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/db78ce6d-838a-46e7-b0d9-2dfc86b04fc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: from .appspot.com to .appspot-preview.com

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

A change was made causing some App Engine Flexible apps to redirect to 
appspot-preview.com. If you have any client applications that point to the 
old domain, you'll need to update them to use the new URL.

On Saturday, February 18, 2017 at 4:15:10 AM UTC-5, Kriti das wrote:
>
> My project was having the domain name -
>
> https://transm-157601.appspot.com/
>
> Today I suddenly notice the domain has changed to :
>
> https://transm-157601.appspot-preview.com/
>
> As a result of this I think I am getting the following error while I try 
> to log in into my application -
>
> XMLHttpRequest cannot load https://transm-157601.appspot.com/users/login. 
> Response for preflight is invalid (redirect)
>
> Can you please let me know what I need to change? 
>
>
>

-- 
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/311dcdde-b1f2-4fa9-8d68-a215ded19320%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: URLFetchServiceStreamHandler$Connection cannot be cast to HttpsURLConnection

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

I should have mentioned this is specific to the App Engine *standard 
*environment 
- there aren't any sandbox restrictions on the flexible environment, so 
migrating 
<https://cloud.google.com/appengine/docs/flexible/go/migrating#url_fetch> 
to that is an option. 

On Wednesday, February 15, 2017 at 2:11:33 AM UTC-5, Shachar Grembek wrote:
>
> Thanks, but apparently it is used by a library that I using and therefore 
> it makes things more complicated. Is there a workaround in matters of the 
> technology stack that I am using that I can change so that the current 
> implementation of that library wouldn't be an issue with the other stack. 
> For example moving from Servlet based API to Google Endpoints or moving 
> from App Engine to VM or Container?
> BTW: I tried to edit the library code and update their usage
>
> On Wednesday, February 15, 2017 at 12:49:56 AM UTC+2, Adam (Cloud Platform 
> Support) wrote:
>>
>> URLFetchServiceStreamHandler extends HttpURLConnection, not 
>> HttpsURLConnection. You can use HttpURLConnection to connect to https:// 
>> URLs though. 
>>
>> The issue is that zendesk-java-client relies on Ning's AsyncHttpClient 
>> 1.9.x which is doing things like this 
>> <https://github.com/AsyncHttpClient/async-http-client/blob/1.9.x/src/main/java/com/ning/http/client/providers/jdk/JDKAsyncHttpProvider.java#L184>
>> :
>>
>>   if (request.getUri().getScheme().equals("https")) {
>> HttpsURLConnection secure = (HttpsURLConnection) 
>> urlConnection;
>>
>> It would not work on App Engine without some modifications to the source 
>> code to avoid casting HttpURLConnection to HttpsURLConnection. Not all 
>> libraries will work on App Engine out of the box due to some quirks such as 
>> these
>>
>> On Tuesday, February 14, 2017 at 4:03:28 PM UTC-5, Shachar Grembek wrote:
>>>
>>> Hi,
>>>
>>>
>>> I am using the Zendesk java client (
>>> https://github.com/cloudbees/zendesk-java-client) on my Google App 
>>> Engine server and I have a runtime issue that prevents me from using the 
>>> SDK. Can you please advise:
>>>
>>> When I call the Zendesk SDK, I get on the server:
>>>
>>>
>>> I am using JDK 7 with App Engine SDK 1.9.49
>>>
>>>
>>> Uncaught exception from servlet java.lang.ClassCastException: com.google
>>> .apphosting.utils.security.urlfetch.
>>> URLFetchServiceStreamHandler$Connection cannot be cast to javax.net.ssl.
>>> HttpsURLConnection 
>>> at com.ning.http.client.providers.jdk.JDKAsyncHttpProvider.
>>> createUrlConnection(JDKAsyncHttpProvider.java:184)
>>> at com.ning.http.client.providers.jdk.JDKAsyncHttpProvider.execute(
>>> JDKAsyncHttpProvider.java:147)
>>> at com.ning.http.client.providers.jdk.JDKAsyncHttpProvider.execute(
>>> JDKAsyncHttpProvider.java:118)
>>> at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.
>>> java:506) 
>>> at org.zendesk.client.v2.Zendesk.submit(Zendesk.java:1751) 
>>> at org.zendesk.client.v2.Zendesk.access$1300(Zendesk.java:90)
>>>
>>

-- 
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/f873cf52-948c-42fc-8849-f58e4591c1d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.