[google-appengine] Re: Managed VM old docs anywhere ?

[pdknsk]

I agree with you on most points, but want to point out that this has 
already been discussed quite a bit with the Google Cloud SDK developers.

To read up on (and join) the discussion I recommend to read comment #27 in 
the following bug report, and the forum discussion mentioned a few comments 
later.

https://code.google.com/p/google-cloud-sdk/issues/detail?id=163#c27

-- 
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/7cb3c823-a7d4-4653-aded-5f6bd4a21a80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Problem with "Deploy module to backend": Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=app-name&version=1& 404 Not Fo

[Rizwan Choudrey]

Yeah my project was API only. I have deleted and recreated. I think that
has worked. Thanks!

On Wed, 9 Mar 2016 19:31 'Zeehad (Cloud Platform Support)' via Google App
Engine,  wrote:

> Also, there used to be a way to create only API projects. If your project
> is an API project, an App Engine application cannot be added to it. You can
> solve this by deleting the project and creating a new one.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/VqNulscLNnI/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/35c5fd4b-a9f1-47a3-ad88-10514930e1c9%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/CAD1Ewoh6pxz8eUbzc6JFt8F66kXkVj%2BQuVpGp3FK2pfk_L3X%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Managed VM old docs anywhere ?

[Su-Au Hwang]

Thanks for the link!
I've seen Appstart before and it looks like a great solution, albeit not 
officially supported.

I'm just disappointed that they almost gave us a nice solution and then 
removed it again. Although the Image Service and Cloud Storage has never 
been implemented anyways, not even on classic.
For now I'll write clean code and abstract away the datastore/taskqueue 
other google services completely and replace it with a different 
implementation for testing locally. More work, but the result would be more 
portable and nicer code.

Any hints for making working with MVMs simpler/easier are welcome.


On Thursday, March 10, 2016 at 4:06:19 PM UTC+8, pdknsk wrote:
>
> I agree with you on most points, but want to point out that this has 
> already been discussed quite a bit with the Google Cloud SDK developers.
>
> To read up on (and join) the discussion I recommend to read comment #27 in 
> the following bug report, and the forum discussion mentioned a few comments 
> later.
>
> https://code.google.com/p/google-cloud-sdk/issues/detail?id=163#c27
>

-- 
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/2f76b351-b208-4454-bf65-ca146b8fb055%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] New Log Viewer - Unusable

[Rajesh Gupta]

New Log viewer is slow with many issues.
It is just not usable for production logs.
I was examining the logs that are 10 days old.
I am using the advance filter.
- Don't know if I am scrolling down, wheather the logs are shown older or
newer
- When given the date, don't know, the logs are searching older than the
given date or later than
the given date.
- Too slow,
- Some times does not fetch the logs even after waiting for 1-2 min.
- The menu link 'view - show new logs at the top'.  Don't know which state
that it is, and it does not store the state. There should be a checkmark,
saying it is showing the new logs at top or at the bottom.

Request appengine team, to fix the log viewer and make it more pleasant to
use.


-- 
Rajesh
*www.VeersoftSolutions.com *
*www.AccountingGuru.net *
*Accounting/Inventory/Orders 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/CA%2BS7ijZLVKK_Ayd6%3DM%2BX8j2eTG8sJLadtxWyk7ie3M7h_K03fw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cannot send mail

[Marek Dusek]

Hello,

may I ask how you solved the issue (as the link is no longer valid and the 
ticket ID disappeared from the public ticket listing)?

We are facing similar issue on our GAE application - emails suddenly 
(within last days) stopped being delivered, although no change was made to 
the settings or code (and the mail quota in dev console is being updated 
properly).

I believe there are similar posts on SO without any conclusion.

Thank you,
Marek Dusek

On Friday, March 4, 2016 at 9:58:57 PM UTC+1, Nick (Cloud Platform Support) 
wrote:
>
> Hey Rob,
>
> Thanks for the link, and for posting in the right place :) We'll be active 
> on that thread shortly. 
>
> On Friday, March 4, 2016 at 10:56:02 AM UTC-5, Rob Williams wrote:
>>
>> Hi Nick,
>>
>> I've created 
>> https://code.google.com/p/googleappengine/issues/detail?id=12786
>>
>> Thanks.
>>
>> On Thursday, March 3, 2016 at 6:38:11 PM UTC-5, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Rob,
>>>
>>> The best way to get us to look at a potential issue is to make a report 
>>> in the Public Issue Tracker 
>>> . Feel free to 
>>> do so, with as much technical information as possible, and you'll find that 
>>> the responses are quick and the issue will make progress. Posting in a 
>>> forum meant for general discussion (such as this one) is far less likely to 
>>> find its way to people who can help.
>>>
>>> Best wishes,
>>>
>>> Nick
>>>
>>>
>>>
>>> On Wednesday, March 2, 2016 at 12:49:42 PM UTC-5, Rob Williams wrote:

 Hi,

 I've seen the same since yesterday, 1-March-2015. Existing code queues 
 mails to not send too fast. Test case has a small number of receivers.

 Have found that:

- Logs indicate mail was sent
- Quota is updated to show mail being sent
- Only a small random subset of the sent mails are received by 
remote hosts
   - Have tested with multiple receiving domains
   - Emails are not in junk folders
   - The few emails that are delivered arrive instantly
- No bounce backs have been delivered


 Several people are seeing similar behaviour on stack overflow. 
 http://stackoverflow.com/questions/35727054/google-app-engine-python-mail-sent-but-not-received
   

 http://stackoverflow.com/questions/35737937/sending-email-stopped-working-using-anythingtestapp-appspotmail-com


 Is email transmission broken? Is email being radically queued?

 Thanks!


 On Tuesday, March 1, 2016 at 6:14:20 PM UTC-5, Petr Balogh wrote:
>
> Hello, 
>
> I've met problem in my application.. problem is that I cannot send 
> email.. or behaviour seems weird..
>
> First time I've got email.. but after that haven't..  if app was 
> running day, maybe two it started sending email.. but after I sent some 
> changes to app, it stopped sending mails again..
>
> I tried create different testing page but doesn't work :( :
>
> from google.appengine.api import mail 
>   
> import webapp2 
>  
>   
>   
>
> [code] 
>
> class emailTest(webapp2.RequestHandler):   
>  
> def get(self): 
>  
> message = mail.EmailMessage(   
>  
> sender="noreply ", 
>  
> subject="Testing email"   
>   
> ) 
>   
>   
>   
> message.to = "My Name "  
> message.body = """ 
>  
> Dear Albert:   
>  
>   
>   
> Your example.com account has been approved.  You can now 
> visit  
> http://www.example.com/ and sign in using your Google Account 
> to
> access new features.   
>  
>   
>   
> Please let us know if you have any questions. 
>   
>   
>   
> The e

[google-appengine] Re: Cannot send mail

[Rob Williams]

Hi,

The issue is still being investigated. The google team made it private.

I'm supposed to hear back from their investigation by/on tomorrow, Friday 
10/March/2016.

Thanks.


On Thursday, March 10, 2016 at 8:15:46 AM UTC-5, Marek Dusek wrote:
>
> Hello,
>
> may I ask how you solved the issue (as the link is no longer valid and the 
> ticket ID disappeared from the public ticket listing)?
>
> We are facing similar issue on our GAE application - emails suddenly 
> (within last days) stopped being delivered, although no change was made to 
> the settings or code (and the mail quota in dev console is being updated 
> properly).
>
> I believe there are similar posts on SO without any conclusion.
>
> Thank you,
> Marek Dusek
>
> On Friday, March 4, 2016 at 9:58:57 PM UTC+1, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Rob,
>>
>> Thanks for the link, and for posting in the right place :) We'll be 
>> active on that thread shortly. 
>>
>> On Friday, March 4, 2016 at 10:56:02 AM UTC-5, Rob Williams wrote:
>>>
>>> Hi Nick,
>>>
>>> I've created 
>>> https://code.google.com/p/googleappengine/issues/detail?id=12786
>>>
>>> Thanks.
>>>
>>> On Thursday, March 3, 2016 at 6:38:11 PM UTC-5, Nick (Cloud Platform 
>>> Support) wrote:

 Hey Rob,

 The best way to get us to look at a potential issue is to make a report 
 in the Public Issue Tracker 
 . Feel free to 
 do so, with as much technical information as possible, and you'll find 
 that 
 the responses are quick and the issue will make progress. Posting in a 
 forum meant for general discussion (such as this one) is far less likely 
 to 
 find its way to people who can help.

 Best wishes,

 Nick



 On Wednesday, March 2, 2016 at 12:49:42 PM UTC-5, Rob Williams wrote:
>
> Hi,
>
> I've seen the same since yesterday, 1-March-2015. Existing code queues 
> mails to not send too fast. Test case has a small number of receivers.
>
> Have found that:
>
>- Logs indicate mail was sent
>- Quota is updated to show mail being sent
>- Only a small random subset of the sent mails are received by 
>remote hosts
>   - Have tested with multiple receiving domains
>   - Emails are not in junk folders
>   - The few emails that are delivered arrive instantly
>- No bounce backs have been delivered
>
>
> Several people are seeing similar behaviour on stack overflow. 
> http://stackoverflow.com/questions/35727054/google-app-engine-python-mail-sent-but-not-received
>   
>
> http://stackoverflow.com/questions/35737937/sending-email-stopped-working-using-anythingtestapp-appspotmail-com
>
>
> Is email transmission broken? Is email being radically queued?
>
> Thanks!
>
>
> On Tuesday, March 1, 2016 at 6:14:20 PM UTC-5, Petr Balogh wrote:
>>
>> Hello, 
>>
>> I've met problem in my application.. problem is that I cannot send 
>> email.. or behaviour seems weird..
>>
>> First time I've got email.. but after that haven't..  if app was 
>> running day, maybe two it started sending email.. but after I sent some 
>> changes to app, it stopped sending mails again..
>>
>> I tried create different testing page but doesn't work :( :
>>
>> from google.appengine.api import mail 
>>   
>> import webapp2   
>>
>>   
>>   
>>
>> [code]   
>>  
>> class emailTest(webapp2.RequestHandler): 
>>
>> def get(self):   
>>
>> message = mail.EmailMessage( 
>>
>> sender="noreply ", 
>>  
>> subject="Testing email"   
>>   
>> ) 
>>   
>>   
>>   
>> message.to = "My Name "  
>> message.body = """   
>>
>> Dear Albert: 
>>
>>   
>>   
>> Your example.com account has been approved.  You can now 
>> visit  
>> http://www.example.com/ and sign in using your Google 
>> Account to  

[google-appengine] Re: Cannot send mail

[Rob Williams]

:D That's twice in this thread I've got the date wrong. Friday 
11/March/2016.

On Thursday, March 10, 2016 at 9:15:57 AM UTC-5, Rob Williams wrote:
>
> Hi,
>
> The issue is still being investigated. The google team made it private.
>
> I'm supposed to hear back from their investigation by/on tomorrow, Friday 
> 10/March/2016.
>
> Thanks.
>
>
> On Thursday, March 10, 2016 at 8:15:46 AM UTC-5, Marek Dusek wrote:
>>
>> Hello,
>>
>> may I ask how you solved the issue (as the link is no longer valid and 
>> the ticket ID disappeared from the public ticket listing)?
>>
>> We are facing similar issue on our GAE application - emails suddenly 
>> (within last days) stopped being delivered, although no change was made to 
>> the settings or code (and the mail quota in dev console is being updated 
>> properly).
>>
>> I believe there are similar posts on SO without any conclusion.
>>
>> Thank you,
>> Marek Dusek
>>
>> On Friday, March 4, 2016 at 9:58:57 PM UTC+1, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Rob,
>>>
>>> Thanks for the link, and for posting in the right place :) We'll be 
>>> active on that thread shortly. 
>>>
>>> On Friday, March 4, 2016 at 10:56:02 AM UTC-5, Rob Williams wrote:

 Hi Nick,

 I've created 
 https://code.google.com/p/googleappengine/issues/detail?id=12786

 Thanks.

 On Thursday, March 3, 2016 at 6:38:11 PM UTC-5, Nick (Cloud Platform 
 Support) wrote:
>
> Hey Rob,
>
> The best way to get us to look at a potential issue is to make a 
> report in the Public Issue Tracker 
> . Feel free to 
> do so, with as much technical information as possible, and you'll find 
> that 
> the responses are quick and the issue will make progress. Posting in a 
> forum meant for general discussion (such as this one) is far less likely 
> to 
> find its way to people who can help.
>
> Best wishes,
>
> Nick
>
>
>
> On Wednesday, March 2, 2016 at 12:49:42 PM UTC-5, Rob Williams wrote:
>>
>> Hi,
>>
>> I've seen the same since yesterday, 1-March-2015. Existing code 
>> queues mails to not send too fast. Test case has a small number of 
>> receivers.
>>
>> Have found that:
>>
>>- Logs indicate mail was sent
>>- Quota is updated to show mail being sent
>>- Only a small random subset of the sent mails are received by 
>>remote hosts
>>   - Have tested with multiple receiving domains
>>   - Emails are not in junk folders
>>   - The few emails that are delivered arrive instantly
>>- No bounce backs have been delivered
>>
>>
>> Several people are seeing similar behaviour on stack overflow. 
>> http://stackoverflow.com/questions/35727054/google-app-engine-python-mail-sent-but-not-received
>>   
>>
>> http://stackoverflow.com/questions/35737937/sending-email-stopped-working-using-anythingtestapp-appspotmail-com
>>
>>
>> Is email transmission broken? Is email being radically queued?
>>
>> Thanks!
>>
>>
>> On Tuesday, March 1, 2016 at 6:14:20 PM UTC-5, Petr Balogh wrote:
>>>
>>> Hello, 
>>>
>>> I've met problem in my application.. problem is that I cannot send 
>>> email.. or behaviour seems weird..
>>>
>>> First time I've got email.. but after that haven't..  if app was 
>>> running day, maybe two it started sending email.. but after I sent some 
>>> changes to app, it stopped sending mails again..
>>>
>>> I tried create different testing page but doesn't work :( :
>>>
>>> from google.appengine.api import mail   
>>> 
>>> import webapp2   
>>>
>>> 
>>> 
>>>
>>> [code]   
>>>  
>>> class emailTest(webapp2.RequestHandler): 
>>>
>>> def get(self):   
>>>
>>> message = mail.EmailMessage( 
>>>
>>> sender="noreply ",   
>>>
>>> subject="Testing email" 
>>> 
>>> )   
>>> 
>>> 
>>> 
>>> message.to = "My Name " 
>>>  
>>> message.body = """   
>>>
>>> Dear Albert:

[google-appengine] Make local appengine use remote datastore (Python)

[Danny Tran]

I'm attempting to make my appengine application running locally use a 
remote datastore.

In appengine_config.py I'm adding the following lines.

from google.appengine.ext.remote_api import remote_api_stub
remote_api_stub.ConfigureRemoteApiForOAuth('MyApp.appspot.com','/_ah/remote_api')
 
# name removed

Per the instructions here:
https://cloud.google.com/appengine/docs/python/tools/remoteapi

However, when I try to send a basic HTTP request to my local app, it 
results in an infinite recursion loop between a url fetcher and a logger.

Am I missing something?

-- 
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/dc594b12-1da8-4513-9e11-0dc66e59917a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Make local appengine use remote datastore (Python)

[George-Cristian Bîrzan]

We had a very similar issue: refresh token -> memcache -> refresh token. It
was because we initialised the testbed beforehand.

On 10 March 2016 at 18:32, Danny Tran  wrote:

> I'm attempting to make my appengine application running locally use a
> remote datastore.
>
> In appengine_config.py I'm adding the following lines.
>
> from google.appengine.ext.remote_api import remote_api_stub
> remote_api_stub.ConfigureRemoteApiForOAuth('MyApp.appspot.com','/_ah/remote_api')
> # name removed
>
> Per the instructions here:
> https://cloud.google.com/appengine/docs/python/tools/remoteapi
>
> However, when I try to send a basic HTTP request to my local app, it
> results in an infinite recursion loop between a url fetcher and a logger.
>
> Am I missing something?
>
> --
> 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/dc594b12-1da8-4513-9e11-0dc66e59917a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
George-Cristian Bîrzan

-- 
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/CA%2B3w0iUB%3DP8cr_w8EoHB588Ls_14fNMSNc7xP0tFeBYWvZM%3D_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Trying to create an App Inventor custom TinyWebDB - error You do not have permission to modify this app

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

Hello Paul,

I've tested the sample application provided at the link above and despite 
throwing a warning for deprecated Python 2.5 runtime, it deploys 
successfully. So the issue you're facing is indeed with project permission.

At first make sure the user account you're deploying with has either 
'Owner' or 'Editor' permission for the project by visiting the permissions 
page 
.
 
If you need to add a user account, make sure to accept the invitation by 
logging into the invited account.

You can then open App Engine Launcher and select 'Control' -> 'Clear 
Deployment Credential' to delete any saved credentials. The next deployment 
attempt should prompt you for granting access to the launcher. Before you 
hit 'Allow', make sure you're logged in with the correct user account (top 
right corner).

I hope that helps. 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/bb91cbf5-8247-4e58-b035-b46a418687e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Trying to create an App Inventor custom TinyWebDB - error You do not have permission to modify this app

[Paul Brown]

I have no idea how that fixed it (I already had the right permissions), but
for whatever reason that has indeed fixed it. Thank you soo much!!!

On Thu, Mar 10, 2016 at 1:54 PM, 'Zeehad (Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Paul,
>
> I've tested the sample application provided at the link above and despite
> throwing a warning for deprecated Python 2.5 runtime, it deploys
> successfully. So the issue you're facing is indeed with project permission.
>
> At first make sure the user account you're deploying with has either
> 'Owner' or 'Editor' permission for the project by visiting the permissions
> page
> .
> If you need to add a user account, make sure to accept the invitation by
> logging into the invited account.
>
> You can then open App Engine Launcher and select 'Control' -> 'Clear
> Deployment Credential' to delete any saved credentials. The next deployment
> attempt should prompt you for granting access to the launcher. Before you
> hit 'Allow', make sure you're logged in with the correct user account (top
> right corner).
>
> I hope that helps. Cheers!
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/CQ4VNhUzr8s/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/bb91cbf5-8247-4e58-b035-b46a418687e2%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/CALJymmr23zhz-rnZa8eJ-z6TiE4DAzFAWALrDvApt47YRfW0zQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Managed VM old docs anywhere ?

['Jon Parrott' via Google App Engine]

We'd love to hear feedback on how we can make the extending runtime and 
building custom runtime pages better as well.

On Thursday, March 10, 2016 at 1:15:59 AM UTC-8, Su-Au Hwang wrote:
>
> Thanks for the link!
> I've seen Appstart before and it looks like a great solution, albeit not 
> officially supported.
>
> I'm just disappointed that they almost gave us a nice solution and then 
> removed it again. Although the Image Service and Cloud Storage has never 
> been implemented anyways, not even on classic.
> For now I'll write clean code and abstract away the datastore/taskqueue 
> other google services completely and replace it with a different 
> implementation for testing locally. More work, but the result would be more 
> portable and nicer code.
>
> Any hints for making working with MVMs simpler/easier are welcome.
>
>
> On Thursday, March 10, 2016 at 4:06:19 PM UTC+8, pdknsk wrote:
>>
>> I agree with you on most points, but want to point out that this has 
>> already been discussed quite a bit with the Google Cloud SDK developers.
>>
>> To read up on (and join) the discussion I recommend to read comment #27 
>> in the following bug report, and the forum discussion mentioned a few 
>> comments later.
>>
>> https://code.google.com/p/google-cloud-sdk/issues/detail?id=163#c27
>>
>

-- 
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/059082cc-9e46-441d-8eb0-8d0708a8e0f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] I cannot verify my domain name on Developers Console

[Ian Anderson]

I think it's a bug. I'm able to do so on the Webmaster Tool/Search Console. 
But on the Developer Console. With the DNS TXT record verification, it 
still does not verify despite everything being correct. I even added the 
record for 2 days so I know it's not a propagation issue. 

The domain I need to verify is poz.com. I'm already verified on Webmaster 
Tools but not in Developer Console. Any ideas? Where can I set in a bug 
report?

-- 
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/8a9e47d5-0001-4914-a580-d2929b0e8cbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: python managed VMs success story! (so far...)

['Jon Parrott' via Google App Engine]

Hey Adam, thanks for the great feedback.

Can you give me a bit more details on PIL not working for you? Which 
runtime are you using?

On Tuesday, March 8, 2016 at 8:14:14 PM UTC-8, Adam Sah wrote:
>
> quick followup and a good example of how it's easy to run components 
> side-by-side:
>  - Image processing (PIL) doesn't work yet - bummer because my app resizes 
> its images.
>  - but no problem!  I just setup a 302 redirect back to the old app 
> version, which still runs on demand! (or use urlfetch or ...)
>
> adam
>
>
> On Tuesday, March 8, 2016 at 12:35:01 PM UTC-8, Adam Sah wrote:
>>
>> My 5+ year old GAE/Python app migrated to Managed VMs (MVM) flawlessly! 
>>  (enterprise app with 15,000+ users doing all sorts of different things - 
>> not a simple website)
>>
>> easy upgrade:
>>  - minimal code changes - just changed app.yaml and our deploy scripts
>>  - deploys into a new "version" of the same dev/staging/production 
>> instances as non-MVM GAE, i.e. share backup/restore, one click to 
>> split/migrate traffic, etc
>>  - one click to rollback
>>  - can upgrade some modules and not others; if you're still using 
>> backends, they can stay on native GAE.  Example: cron.yaml jobs can still 
>> run on GAE native if you want.
>>
>> lots of immediate wins:
>>  - 30-300% performance boost (depending on the activity, of course - I/O 
>> bound not so much)
>>  - immediate $$$ savings 
>>  - not limited to 1GB RAM and in fact it starts with 1.7GB.
>>  - not limited to slow or single core CPUs
>>
>> lots of roadmap wins:
>>  - native libraries
>>  - python3
>>  - can SSH into live instance(s) -- though admittedly, I haven't figured 
>> out the value yet...
>>
>> wrinkles:
>>  - deploy time is much slower -- 8+ mins
>>  - auto-scaling is a lot slower, i.e. in practice users may get 502 
>> errors if you don't provision correctly - even with auto-scaling
>>  - logs are more detailed but harder to read - native GAE had nice simple 
>> stack traces
>>  - deploys to one zone/region for now -- native GAE was multi-homed
>>  - docs were incomplete, e.g. didn't mention needing to push cron.yaml, 
>> index.yaml
>>  - error messages are incomplete, e.g. queue.yaml needs to be precisely 
>> named that (where other yaml files can have any name)
>>
>> hope this helps,   (and feedback welcome)
>> 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/393706de-3e45-4bfa-bdfb-c2c5e9074fbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: another wrinkle with GAE/Python Managed VMs: timezone set to local deploy location, not UTC like in GAE

[Adam Sah]

Here's what I've tried so far...
 - set os.environ['TZ'] to 'UTC' on startup - failed because GAE overwrites 
this.
 - set os.environ['TZ'] to 'UTC' on each call by creating a child class to 
webapp.WSGIApplication and adding it to __call__() - failed because GAE 
overwrites this.
 - monkeypatching datetime.datetime.now() to use a specially hacked 
function - failed because GAE disallows modifying now()

I'm currently trying a hack to rewrite all calls (100+) 
to datetime.datetime.now() to instead use an app-specific implementation 
which returns the UTC time - this won't work for third party libraries, but 
that maybe OK for my app, which uses pylint custom rules to migrate 
engineers to using app-specific replacement functions (e.g. we disallow 
direct calls to gc.collect() so we can track stats better).  If this works, 
I'll post.

adam


On Wednesday, March 9, 2016 at 1:45:54 PM UTC-8, Adam Sah wrote:
>
> e.g. os.environ['TZ'] changed to America/Chicago when before it was UTC.
>
> The docs don't mention this difference anywhere.
>
> If anyone has a workaround, pls reply - I'm working on a workaround now, 
> will post if successful.
>
> hope this helps,
> 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/f4c00a8f-e491-4fbe-ad0d-81d748916541%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: python managed VMs success story! (so far...)

[Adam Sah]

Actually, I misspoke - it's the Images API that's the trouble, which was 
covered 
elsewhere: https://groups.google.com/forum/#!topic/google-appengine/jdwYig9smJI
   (just need to update the GAE/MVM docs to mention this explicitly, and 
ideally detect if an app might be using this 

Currently, I'm fighting with the timezone 
issue: https://groups.google.com/forum/#!topic/google-appengine/8vob1UfnRpY

adam


On Thursday, March 10, 2016 at 12:04:17 PM UTC-8, Jon Parrott wrote:
>
> Hey Adam, thanks for the great feedback.
>
> Can you give me a bit more details on PIL not working for you? Which 
> runtime are you using?
>
> On Tuesday, March 8, 2016 at 8:14:14 PM UTC-8, Adam Sah wrote:
>>
>> quick followup and a good example of how it's easy to run components 
>> side-by-side:
>>  - Image processing (PIL) doesn't work yet - bummer because my app 
>> resizes its images.
>>  - but no problem!  I just setup a 302 redirect back to the old app 
>> version, which still runs on demand! (or use urlfetch or ...)
>>
>> adam
>>
>>
>> On Tuesday, March 8, 2016 at 12:35:01 PM UTC-8, Adam Sah wrote:
>>>
>>> My 5+ year old GAE/Python app migrated to Managed VMs (MVM) flawlessly! 
>>>  (enterprise app with 15,000+ users doing all sorts of different things - 
>>> not a simple website)
>>>
>>> easy upgrade:
>>>  - minimal code changes - just changed app.yaml and our deploy scripts
>>>  - deploys into a new "version" of the same dev/staging/production 
>>> instances as non-MVM GAE, i.e. share backup/restore, one click to 
>>> split/migrate traffic, etc
>>>  - one click to rollback
>>>  - can upgrade some modules and not others; if you're still using 
>>> backends, they can stay on native GAE.  Example: cron.yaml jobs can still 
>>> run on GAE native if you want.
>>>
>>> lots of immediate wins:
>>>  - 30-300% performance boost (depending on the activity, of course - I/O 
>>> bound not so much)
>>>  - immediate $$$ savings 
>>>  - not limited to 1GB RAM and in fact it starts with 1.7GB.
>>>  - not limited to slow or single core CPUs
>>>
>>> lots of roadmap wins:
>>>  - native libraries
>>>  - python3
>>>  - can SSH into live instance(s) -- though admittedly, I haven't figured 
>>> out the value yet...
>>>
>>> wrinkles:
>>>  - deploy time is much slower -- 8+ mins
>>>  - auto-scaling is a lot slower, i.e. in practice users may get 502 
>>> errors if you don't provision correctly - even with auto-scaling
>>>  - logs are more detailed but harder to read - native GAE had nice 
>>> simple stack traces
>>>  - deploys to one zone/region for now -- native GAE was multi-homed
>>>  - docs were incomplete, e.g. didn't mention needing to push cron.yaml, 
>>> index.yaml
>>>  - error messages are incomplete, e.g. queue.yaml needs to be precisely 
>>> named that (where other yaml files can have any name)
>>>
>>> hope this helps,   (and feedback welcome)
>>> 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/68bbd936-0393-4972-a1da-9ce2283fe220%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: another wrinkle with GAE/Python Managed VMs: timezone set to local deploy location, not UTC like in GAE

[Adam Sah]

oops, to be specific here's what I'm seeing:

   datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 14:57:31 2016   
 (i.e. timestamp is in CST with no timezone info)
   os.environ['TZ'] ==> America/Chicago

where dev_appserver and standard GAE return:

   datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 21:00:14 2016   
 (i.e. timestamp is in UTC with no timezone info)
   os.environ['TZ'] ==> 'UTC'

adam

On Thursday, March 10, 2016 at 12:32:07 PM UTC-8, Adam Sah wrote:
>
> Here's what I've tried so far...
>  - set os.environ['TZ'] to 'UTC' on startup - failed because GAE 
> overwrites this.
>  - set os.environ['TZ'] to 'UTC' on each call by creating a child class to 
> webapp.WSGIApplication and adding it to __call__() - failed because GAE 
> overwrites this.
>  - monkeypatching datetime.datetime.now() to use a specially hacked 
> function - failed because GAE disallows modifying now()
>
> I'm currently trying a hack to rewrite all calls (100+) 
> to datetime.datetime.now() to instead use an app-specific implementation 
> which returns the UTC time - this won't work for third party libraries, but 
> that maybe OK for my app, which uses pylint custom rules to migrate 
> engineers to using app-specific replacement functions (e.g. we disallow 
> direct calls to gc.collect() so we can track stats better).  If this works, 
> I'll post.
>
> adam
>
>
> On Wednesday, March 9, 2016 at 1:45:54 PM UTC-8, Adam Sah wrote:
>>
>> e.g. os.environ['TZ'] changed to America/Chicago when before it was UTC.
>>
>> The docs don't mention this difference anywhere.
>>
>> If anyone has a workaround, pls reply - I'm working on a workaround now, 
>> will post if successful.
>>
>> hope this helps,
>> 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/67e76fa0-15c7-4381-8fd6-19f42e329cef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Managed VM old docs anywhere ?

[Su-Au Hwang]

Having something like in the old docs would be good.
Just to make sure I'm not missing anything:
I've checked these two pages:

   1. https://cloud.google.com/appengine/docs/managed-vms/
   2. https://cloud.google.com/docs/ (The Node.js/Ruby/Python/Go starter)

Here is all I could currently find about extending/custorm runtimes: 

   1. https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes/
   2. 
   https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes/build
   
Basically it says it can be done and describes port 8080, start/stop, 
healthchecks, logging.
But there are no examples at all. And because of the "better" dockerless 
getting started experience, the user hasn't even seen or worked with any 
dockerfile yet. Probably not even virtualbox/docker/boot2docker installed.
At latest now, this should happen. While it isn't strictly necessary, I 
wouldn't expect anyone to write a flawless dockerfile without testing it 
locally.

Compared to the old docs, there were examples
for extending a standard runtime:

   1. 
https://web.archive.org/web/20150320121928/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step4
 
   (apt-get)
   2. 
https://web.archive.org/web/20150320094050/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step5
 
   (python dependcy)
   3. 
https://web.archive.org/web/20150320175551/https://cloud.google.com/appengine/docs/managed-vms/tutorial/step6
 
   (native c extension)
   
for building a custom runtime

   1. 
   
https://web.archive.org/web/20150321081655/https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes
   
on top of that, the user had worked with docker through out the basic 
tutorial already.

If this sounds like a rant, then it's because I've mentioned that here 
already:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/google-appengine-go/Managed$20VM$20GOPATH$20issues/google-appengine-go/LQMhpx447hI/2qgNgNoyl2EJ
,but was told

"Getting Started with Managed VMs" experience was painful due to the need 
> for VirtualBox, boot2docker, and Docker.
>

I understand that "Getting Started" should be kept as simple as possible 
and advanced usages kept for later. But it was simply removed.

 
On Friday, March 11, 2016 at 3:10:13 AM UTC+8, Jon Parrott wrote:
>
> We'd love to hear feedback on how we can make the extending runtime and 
> building custom runtime pages better as well.
>
> On Thursday, March 10, 2016 at 1:15:59 AM UTC-8, Su-Au Hwang wrote:
>>
>> Thanks for the link!
>> I've seen Appstart before and it looks like a great solution, albeit not 
>> officially supported.
>>
>> I'm just disappointed that they almost gave us a nice solution and then 
>> removed it again. Although the Image Service and Cloud Storage has never 
>> been implemented anyways, not even on classic.
>> For now I'll write clean code and abstract away the datastore/taskqueue 
>> other google services completely and replace it with a different 
>> implementation for testing locally. More work, but the result would be more 
>> portable and nicer code.
>>
>> Any hints for making working with MVMs simpler/easier are welcome.
>>
>>
>> On Thursday, March 10, 2016 at 4:06:19 PM UTC+8, pdknsk wrote:
>>>
>>> I agree with you on most points, but want to point out that this has 
>>> already been discussed quite a bit with the Google Cloud SDK developers.
>>>
>>> To read up on (and join) the discussion I recommend to read comment #27 
>>> in the following bug report, and the forum discussion mentioned a few 
>>> comments later.
>>>
>>> https://code.google.com/p/google-cloud-sdk/issues/detail?id=163#c27
>>>
>>

-- 
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/f9ecc696-20d0-4bad-855b-7c4bf692d388%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: another wrinkle with GAE/Python Managed VMs: timezone set to local deploy location, not UTC like in GAE

[Adam Sah]

OK, horrible workaround deployed.  Roughly:

main.py:

PATHS=[...
  (r'/_ah/warmup', WarmupView),
  (r'/_ah/start', StartView),

class WarmupView(webapp.RequestHandler):
  def get(self, *args):  # pylint:disable=W0613,R0201
base.SERVER_TZ = None  # allow base.set_now() to reset server timezone
base.now()

class StartView(webapp.RequestHandler):
  def get(self, *args):  # pylint:disable=W0613,R0201
base.SERVER_TZ = None  # allow base.set_now() to reset server timezone
base.now()

base.py:

import pytz
...
SERVER_TZ = None
...
def now(nowval=None):
  global SERVER_TZ
  ...
  if SERVER_TZ is None:
  try:
# HACK of the year award!  os.environ['TZ'] isn't available during 
GAE/Managed VMs startup
# and date +%Z and /etc/timezone didn't have useful information 
either
# even env | grep TZ failed!!
import subprocess
localtz = subprocess.check_output("date +%Z", shell=True).strip()
# SUPER HACK: I couldn't find pytz-compatible timezone strings, so 
I hacked it.
# Yes, I know I'm going to hell for this.
SERVER_TZ = 'America/Chicago' if localtz == 'CST' else 'UTC'
  except:
SERVER_TZ = 'UTC'
nowval = datetime.datetime.now()  # pylint:disable=W9914
if SERVER_TZ != 'UTC':
  # set the tz to the server tz, convert to UTC, then strip the tz info
  nowval = nowval.replace(tzinfo=pytz.timezone(SERVER_TZ)).astimezone(
pytz.timezone('UTC')).replace(tzinfo=None)
  return nowval


adam


On Thursday, March 10, 2016 at 1:01:57 PM UTC-8, Adam Sah wrote:
>
> oops, to be specific here's what I'm seeing:
>
>datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 14:57:31 2016 
>(i.e. timestamp is in CST with no timezone info)
>os.environ['TZ'] ==> America/Chicago
>
> where dev_appserver and standard GAE return:
>
>datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 21:00:14 2016 
>(i.e. timestamp is in UTC with no timezone info)
>os.environ['TZ'] ==> 'UTC'
>
> adam
>
> On Thursday, March 10, 2016 at 12:32:07 PM UTC-8, Adam Sah wrote:
>>
>> Here's what I've tried so far...
>>  - set os.environ['TZ'] to 'UTC' on startup - failed because GAE 
>> overwrites this.
>>  - set os.environ['TZ'] to 'UTC' on each call by creating a child class 
>> to webapp.WSGIApplication and adding it to __call__() - failed because GAE 
>> overwrites this.
>>  - monkeypatching datetime.datetime.now() to use a specially hacked 
>> function - failed because GAE disallows modifying now()
>>
>> I'm currently trying a hack to rewrite all calls (100+) 
>> to datetime.datetime.now() to instead use an app-specific implementation 
>> which returns the UTC time - this won't work for third party libraries, but 
>> that maybe OK for my app, which uses pylint custom rules to migrate 
>> engineers to using app-specific replacement functions (e.g. we disallow 
>> direct calls to gc.collect() so we can track stats better).  If this works, 
>> I'll post.
>>
>> adam
>>
>>
>> On Wednesday, March 9, 2016 at 1:45:54 PM UTC-8, Adam Sah wrote:
>>>
>>> e.g. os.environ['TZ'] changed to America/Chicago when before it was UTC.
>>>
>>> The docs don't mention this difference anywhere.
>>>
>>> If anyone has a workaround, pls reply - I'm working on a workaround now, 
>>> will post if successful.
>>>
>>> hope this helps,
>>> 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/a01e9187-2528-4e69-b8d9-4c6cf7cd1439%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: another wrinkle with GAE/Python Managed VMs: timezone set to local deploy location, not UTC like in GAE

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

Hey Adam,

Glad to see you found a workaround, I was going to some lengths to verbally 
describe what you basically ended up doing. You should post a quick 
description of this issue to the Public Issue Tracker for App Engine 
 and we'll be happy 
to take a look. It seems rational to have UTC as the default.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 10, 2016 at 6:28:39 PM UTC-5, Adam Sah wrote:
>
> OK, horrible workaround deployed.  Roughly:
>
> main.py:
>
> PATHS=[...
>   (r'/_ah/warmup', WarmupView),
>   (r'/_ah/start', StartView),
>
> class WarmupView(webapp.RequestHandler):
>   def get(self, *args):  # pylint:disable=W0613,R0201
> base.SERVER_TZ = None  # allow base.set_now() to reset server timezone
> base.now()
>
> class StartView(webapp.RequestHandler):
>   def get(self, *args):  # pylint:disable=W0613,R0201
> base.SERVER_TZ = None  # allow base.set_now() to reset server timezone
> base.now()
>
> base.py:
>
> import pytz
> ...
> SERVER_TZ = None
> ...
> def now(nowval=None):
>   global SERVER_TZ
>   ...
>   if SERVER_TZ is None:
>   try:
> # HACK of the year award!  os.environ['TZ'] isn't available during 
> GAE/Managed VMs startup
> # and date +%Z and /etc/timezone didn't have useful information 
> either
> # even env | grep TZ failed!!
> import subprocess
> localtz = subprocess.check_output("date +%Z", shell=True).strip()
> # SUPER HACK: I couldn't find pytz-compatible timezone strings, so 
> I hacked it.
> # Yes, I know I'm going to hell for this.
> SERVER_TZ = 'America/Chicago' if localtz == 'CST' else 'UTC'
>   except:
> SERVER_TZ = 'UTC'
> nowval = datetime.datetime.now()  # pylint:disable=W9914
> if SERVER_TZ != 'UTC':
>   # set the tz to the server tz, convert to UTC, then strip the tz info
>   nowval = nowval.replace(tzinfo=pytz.timezone(SERVER_TZ)).astimezone(
> pytz.timezone('UTC')).replace(tzinfo=None)
>   return nowval
>
>
> adam
>
>
> On Thursday, March 10, 2016 at 1:01:57 PM UTC-8, Adam Sah wrote:
>>
>> oops, to be specific here's what I'm seeing:
>>
>>datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 14:57:31 2016 
>>(i.e. timestamp is in CST with no timezone info)
>>os.environ['TZ'] ==> America/Chicago
>>
>> where dev_appserver and standard GAE return:
>>
>>datetime.datetime.now().strftime("%c %Z") ==> Thu Mar 10 21:00:14 2016 
>>(i.e. timestamp is in UTC with no timezone info)
>>os.environ['TZ'] ==> 'UTC'
>>
>> adam
>>
>> On Thursday, March 10, 2016 at 12:32:07 PM UTC-8, Adam Sah wrote:
>>>
>>> Here's what I've tried so far...
>>>  - set os.environ['TZ'] to 'UTC' on startup - failed because GAE 
>>> overwrites this.
>>>  - set os.environ['TZ'] to 'UTC' on each call by creating a child class 
>>> to webapp.WSGIApplication and adding it to __call__() - failed because GAE 
>>> overwrites this.
>>>  - monkeypatching datetime.datetime.now() to use a specially hacked 
>>> function - failed because GAE disallows modifying now()
>>>
>>> I'm currently trying a hack to rewrite all calls (100+) 
>>> to datetime.datetime.now() to instead use an app-specific implementation 
>>> which returns the UTC time - this won't work for third party libraries, but 
>>> that maybe OK for my app, which uses pylint custom rules to migrate 
>>> engineers to using app-specific replacement functions (e.g. we disallow 
>>> direct calls to gc.collect() so we can track stats better).  If this works, 
>>> I'll post.
>>>
>>> adam
>>>
>>>
>>> On Wednesday, March 9, 2016 at 1:45:54 PM UTC-8, Adam Sah wrote:

 e.g. os.environ['TZ'] changed to America/Chicago when before it was UTC.

 The docs don't mention this difference anywhere.

 If anyone has a workaround, pls reply - I'm working on a workaround 
 now, will post if successful.

 hope this helps,
 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/781f16be-304c-4db1-bbeb-3deb886950c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Log Viewer - Unusable

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

Hey Rajesh,

Thanks for taking the time to write your feedback. Unfortunately, this 
isn't the right place to make such a posting. If you have any concrete 
issues to report or feature requests to propose, feel free to open a thread 
in the Public Issue Tracker for the Cloud Platform 
. We monitor 
it every day and will react quickly to any issue reports or feature 
requests there.  

Best wishes,

Nick
Cloud Platform Community Support

On Thursday, March 10, 2016 at 7:24:24 AM UTC-5, Rajesh Gupta wrote:
>
> New Log viewer is slow with many issues.
> It is just not usable for production logs.
> I was examining the logs that are 10 days old.  
> I am using the advance filter.  
> - Don't know if I am scrolling down, wheather the logs are shown older or 
> newer
> - When given the date, don't know, the logs are searching older than the 
> given date or later than
> the given date.
> - Too slow, 
> - Some times does not fetch the logs even after waiting for 1-2 min.
> - The menu link 'view - show new logs at the top'.  Don't know which state 
> that it is, and it does not store the state. There should be a checkmark, 
> saying it is showing the new logs at top or at the bottom.
>
> Request appengine team, to fix the log viewer and make it more pleasant to 
> use.
>
>
> -- 
> Rajesh
> *www.VeersoftSolutions.com *
> *www.AccountingGuru.net *
> *Accounting/Inventory/Orders 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/dcc37c86-d42c-4c2e-8c47-e19659877a1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Make local appengine use remote datastore (Python)

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

Hey Danny,

I can't say that I'm 100% sure what's happening to cause this behaviour. 
Could you share some more logs, config files, and code? If possible, I'd 
like to try to observe this on my own system. If it represents an issue in 
the SDK or platform, rather than a user misconfiguration, this would be 
necessary to get it fixed, and in the event that it's a user error, I'd 
like to help discover the proper means of getting access to remote 
Datastore via remote API from the development machine. 

Best wishes,

Nick
Cloud Platform Community Support

On Thursday, March 10, 2016 at 11:32:32 AM UTC-5, Danny Tran wrote:
>
> I'm attempting to make my appengine application running locally use a 
> remote datastore.
>
> In appengine_config.py I'm adding the following lines.
>
> from google.appengine.ext.remote_api import remote_api_stub
> remote_api_stub.ConfigureRemoteApiForOAuth('MyApp.appspot.com','/_ah/remote_api')
>  
> # name removed
>
> Per the instructions here:
> https://cloud.google.com/appengine/docs/python/tools/remoteapi
>
> However, when I try to send a basic HTTP request to my local app, it 
> results in an infinite recursion loop between a url fetcher and a logger.
>
> Am I missing something?
>
>

-- 
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/8aa5c78e-ab37-4699-a355-e055d9a0e1e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: I cannot verify my domain name on Developers Console

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

Hey Ian,

This seems like it would be perfectly suited as a defect report at the Public 
Issue Tracker for the Cloud Platform 
. If you 
provide all relevant information, along with your project ID, the domain 
name, and a HAR recording 
 of your attempted 
verification, we'll quickly reply and get to work on determining the root 
cause of the issue. We monitor the Public Issue Trackers every day, so rest 
assured you'll see a response. This thread here is slightly off-topic since 
the App Engine Google Groups forum is meant more for general discussion of 
the platform and services.

Best wishes,

Nick
Cloud Platform Community Support

On Thursday, March 10, 2016 at 2:31:01 PM UTC-5, Ian Anderson wrote:
>
> I think it's a bug. I'm able to do so on the Webmaster Tool/Search 
> Console. But on the Developer Console. With the DNS TXT record 
> verification, it still does not verify despite everything being correct. I 
> even added the record for 2 days so I know it's not a propagation issue. 
>
> The domain I need to verify is poz.com. I'm already verified on Webmaster 
> Tools but not in Developer Console. Any ideas? Where can I set in a bug 
> report?
>

-- 
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/93e92988-d850-462c-b8eb-bd5e859a5a04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cannot send mail

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

Hey Mark,

We continue to look into this issue. The best thing to do would be to 
create a Public Issue Tracker thread with your specific information so that 
we can have a focused and clear context in which to track your issue, which 
might be different or overlapping (we don't know from this point). We 
monitor the Public Issue Tracker every day, so not to worry, we'll be in 
contact quickly after your posting.

On Thursday, March 10, 2016 at 8:15:46 AM UTC-5, Marek Dusek wrote:
>
> Hello,
>
> may I ask how you solved the issue (as the link is no longer valid and the 
> ticket ID disappeared from the public ticket listing)?
>
> We are facing similar issue on our GAE application - emails suddenly 
> (within last days) stopped being delivered, although no change was made to 
> the settings or code (and the mail quota in dev console is being updated 
> properly).
>
> I believe there are similar posts on SO without any conclusion.
>
> Thank you,
> Marek Dusek
>
> On Friday, March 4, 2016 at 9:58:57 PM UTC+1, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Rob,
>>
>> Thanks for the link, and for posting in the right place :) We'll be 
>> active on that thread shortly. 
>>
>> On Friday, March 4, 2016 at 10:56:02 AM UTC-5, Rob Williams wrote:
>>>
>>> Hi Nick,
>>>
>>> I've created 
>>> https://code.google.com/p/googleappengine/issues/detail?id=12786
>>>
>>> Thanks.
>>>
>>> On Thursday, March 3, 2016 at 6:38:11 PM UTC-5, Nick (Cloud Platform 
>>> Support) wrote:

 Hey Rob,

 The best way to get us to look at a potential issue is to make a report 
 in the Public Issue Tracker 
 . Feel free to 
 do so, with as much technical information as possible, and you'll find 
 that 
 the responses are quick and the issue will make progress. Posting in a 
 forum meant for general discussion (such as this one) is far less likely 
 to 
 find its way to people who can help.

 Best wishes,

 Nick



 On Wednesday, March 2, 2016 at 12:49:42 PM UTC-5, Rob Williams wrote:
>
> Hi,
>
> I've seen the same since yesterday, 1-March-2015. Existing code queues 
> mails to not send too fast. Test case has a small number of receivers.
>
> Have found that:
>
>- Logs indicate mail was sent
>- Quota is updated to show mail being sent
>- Only a small random subset of the sent mails are received by 
>remote hosts
>   - Have tested with multiple receiving domains
>   - Emails are not in junk folders
>   - The few emails that are delivered arrive instantly
>- No bounce backs have been delivered
>
>
> Several people are seeing similar behaviour on stack overflow. 
> http://stackoverflow.com/questions/35727054/google-app-engine-python-mail-sent-but-not-received
>   
>
> http://stackoverflow.com/questions/35737937/sending-email-stopped-working-using-anythingtestapp-appspotmail-com
>
>
> Is email transmission broken? Is email being radically queued?
>
> Thanks!
>
>
> On Tuesday, March 1, 2016 at 6:14:20 PM UTC-5, Petr Balogh wrote:
>>
>> Hello, 
>>
>> I've met problem in my application.. problem is that I cannot send 
>> email.. or behaviour seems weird..
>>
>> First time I've got email.. but after that haven't..  if app was 
>> running day, maybe two it started sending email.. but after I sent some 
>> changes to app, it stopped sending mails again..
>>
>> I tried create different testing page but doesn't work :( :
>>
>> from google.appengine.api import mail 
>>   
>> import webapp2   
>>
>>   
>>   
>>
>> [code]   
>>  
>> class emailTest(webapp2.RequestHandler): 
>>
>> def get(self):   
>>
>> message = mail.EmailMessage( 
>>
>> sender="noreply ", 
>>  
>> subject="Testing email"   
>>   
>> ) 
>>   
>>   
>>   
>> message.to = "My Name "  
>> message.body = """   
>>
>> Dear Albert: 
>>
>>

[google-appengine] Re: New Log Viewer - Unusable

[Christian F. Howes]

Rajesh,

I'd love to know what the link is to the issue you file in the Public Issue 
tracker as i would like to star it!  I have the same problems and still use 
the old log viewer because of them.

thanks,

christian

On Thursday, March 10, 2016 at 4:01:27 PM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Rajesh,
>
> Thanks for taking the time to write your feedback. Unfortunately, this 
> isn't the right place to make such a posting. If you have any concrete 
> issues to report or feature requests to propose, feel free to open a thread 
> in the Public Issue Tracker for the Cloud Platform 
> . We monitor 
> it every day and will react quickly to any issue reports or feature 
> requests there.  
>
> Best wishes,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, March 10, 2016 at 7:24:24 AM UTC-5, Rajesh Gupta wrote:
>>
>> New Log viewer is slow with many issues.
>> It is just not usable for production logs.
>> I was examining the logs that are 10 days old.  
>> I am using the advance filter.  
>> - Don't know if I am scrolling down, wheather the logs are shown older or 
>> newer
>> - When given the date, don't know, the logs are searching older than the 
>> given date or later than
>> the given date.
>> - Too slow, 
>> - Some times does not fetch the logs even after waiting for 1-2 min.
>> - The menu link 'view - show new logs at the top'.  Don't know which 
>> state that it is, and it does not store the state. There should be a 
>> checkmark, saying it is showing the new logs at top or at the bottom.
>>
>> Request appengine team, to fix the log viewer and make it more pleasant 
>> to use.
>>
>>
>> -- 
>> Rajesh
>> *www.VeersoftSolutions.com *
>> *www.AccountingGuru.net *
>> *Accounting/Inventory/Orders 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/eb398bb2-3da8-4267-9b8c-31441cbb45ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Make local appengine use remote datastore (Python)

[Danny Tran]

Hi Nick,

Sure.

I've been able to reproduce the issue using a very dumbed-down view.

*app.yaml*
...
- url: /.*
  script: myapp.wsgi.application
  secure: always
...


*wsgi.py*
import os
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "myapp.settings")


from django.core.wsgi import get_wsgi_application
application = get_wsgi_application()

*settings.py*
import os
BASE_DIR = os.path.dirname(os.path.dirname(__file__))
VERSION = '0.1.2'
SECRET_KEY = 'REMOVED'
URLFETCH_TIMEOUT = 60
URLFETCH_VALIDATE_CERTS = True
GAE_NAMESPACE = 'dev'
GAE_SERVICE_ACCOUNT = {
'valid_app_ids': ['REMOVED'],
}
ROOT_URLCONF = 'myapp.urls'
DEBUG = True

*appengine_config.py*
from google.appengine.api import urlfetch
from google.appengine.ext import vendor
vendor.add('lib') # oauth2client lib is installed here

from google.appengine.ext.remote_api import remote_api_stub
remote_api_stub.ConfigureRemoteApiForOAuth('myapp.appspot.com',
'/_ah/remote_api')

from django.conf import settings

*urls.py*
from django.conf.urls import patterns, include, url
from django.shortcuts import render
from django.http import HttpResponse

def foo(request):
return HttpResponse("foo", content_type='text/plain')


urlpatterns = patterns('',
url(r'^v1/foo$', foo)
)


Let me know if you are able to reproduce.

On Thursday, March 10, 2016 at 6:05:13 PM UTC-6, Nick (Cloud Platform 
Support) wrote:
>
> Hey Danny,
>
> I can't say that I'm 100% sure what's happening to cause this behaviour. 
> Could you share some more logs, config files, and code? If possible, I'd 
> like to try to observe this on my own system. If it represents an issue in 
> the SDK or platform, rather than a user misconfiguration, this would be 
> necessary to get it fixed, and in the event that it's a user error, I'd 
> like to help discover the proper means of getting access to remote 
> Datastore via remote API from the development machine. 
>
> Best wishes,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, March 10, 2016 at 11:32:32 AM UTC-5, Danny Tran wrote:
>>
>> I'm attempting to make my appengine application running locally use a 
>> remote datastore.
>>
>> In appengine_config.py I'm adding the following lines.
>>
>> from google.appengine.ext.remote_api import remote_api_stub
>> remote_api_stub.ConfigureRemoteApiForOAuth('MyApp.appspot.com','/_ah/remote_api')
>>  
>> # name removed
>>
>> Per the instructions here:
>> https://cloud.google.com/appengine/docs/python/tools/remoteapi
>>
>> However, when I try to send a basic HTTP request to my local app, it 
>> results in an infinite recursion loop between a url fetcher and a logger.
>>
>> Am I missing something?
>>
>>

-- 
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/c1dc81c3-1b3f-437a-b7d6-860649162d59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Make local appengine use remote datastore (Python)

[Danny Tran]

Some additional discoveries.

If I set_trace() in my "view" method and step through the code. The 
recursion seems to launch when executing this line:
https://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/tools/devappserver2/python/request_handler.py#158

On Thursday, March 10, 2016 at 11:00:59 PM UTC-6, Danny Tran wrote:
>
> Hi Nick,
>
> Sure.
>
> I've been able to reproduce the issue using a very dumbed-down view.
>
> *app.yaml*
> ...
> - url: /.*
>   script: myapp.wsgi.application
>   secure: always
> ...
>
>
> *wsgi.py*
> import os
> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "myapp.settings")
>
>
> from django.core.wsgi import get_wsgi_application
> application = get_wsgi_application()
>
> *settings.py*
> import os
> BASE_DIR = os.path.dirname(os.path.dirname(__file__))
> VERSION = '0.1.2'
> SECRET_KEY = 'REMOVED'
> URLFETCH_TIMEOUT = 60
> URLFETCH_VALIDATE_CERTS = True
> GAE_NAMESPACE = 'dev'
> GAE_SERVICE_ACCOUNT = {
> 'valid_app_ids': ['REMOVED'],
> }
> ROOT_URLCONF = 'myapp.urls'
> DEBUG = True
>
> *appengine_config.py*
> from google.appengine.api import urlfetch
> from google.appengine.ext import vendor
> vendor.add('lib') # oauth2client lib is installed here
>
> from google.appengine.ext.remote_api import remote_api_stub
> remote_api_stub.ConfigureRemoteApiForOAuth('myapp.appspot.com',
> '/_ah/remote_api')
>
> from django.conf import settings
>
> *urls.py*
> from django.conf.urls import patterns, include, url
> from django.shortcuts import render
> from django.http import HttpResponse
>
> def foo(request):
> return HttpResponse("foo", content_type='text/plain')
>
>
> urlpatterns = patterns('',
> url(r'^v1/foo$', foo)
> )
>
>
> Let me know if you are able to reproduce.
>
> On Thursday, March 10, 2016 at 6:05:13 PM UTC-6, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Danny,
>>
>> I can't say that I'm 100% sure what's happening to cause this behaviour. 
>> Could you share some more logs, config files, and code? If possible, I'd 
>> like to try to observe this on my own system. If it represents an issue in 
>> the SDK or platform, rather than a user misconfiguration, this would be 
>> necessary to get it fixed, and in the event that it's a user error, I'd 
>> like to help discover the proper means of getting access to remote 
>> Datastore via remote API from the development machine. 
>>
>> Best wishes,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, March 10, 2016 at 11:32:32 AM UTC-5, Danny Tran wrote:
>>>
>>> I'm attempting to make my appengine application running locally use a 
>>> remote datastore.
>>>
>>> In appengine_config.py I'm adding the following lines.
>>>
>>> from google.appengine.ext.remote_api import remote_api_stub
>>> remote_api_stub.ConfigureRemoteApiForOAuth('MyApp.appspot.com','/_ah/remote_api')
>>>  
>>> # name removed
>>>
>>> Per the instructions here:
>>> https://cloud.google.com/appengine/docs/python/tools/remoteapi
>>>
>>> However, when I try to send a basic HTTP request to my local app, it 
>>> results in an infinite recursion loop between a url fetcher and a logger.
>>>
>>> Am I missing something?
>>>
>>>

-- 
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/09f3f6e4-7a51-4b22-876d-98e8b22d3a9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Make local appengine use remote datastore (Python)

[Danny Tran]

Also, here's a few rounds of the recursion stack trace:

File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 201, in MakeSyncCall
   self._MakeRealSyncCall(service, call, request, response)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 227, in _MakeRealSyncCall
   encoded_response = self._server.Send(self._path, encoded_request)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/appengine_rpc_httplib2.py",
 
line 247, in Send
   url, method=method, body=payload, headers=headers)
 File "...myapp.../lib/oauth2client/client.py", line 622, in new_request
   redirections, connection_type)
 File "...myapp.../lib/httplib2/__init__.py", line 1609, in request
   (response, content) = self._request(conn, authority, uri, request_uri, 
method, body, headers, redirections, cachekey)
 File "...myapp.../lib/httplib2/__init__.py", line 1351, in _request
   (response, content) = self._conn_request(conn, request_uri, method, 
body, headers)
 File "...myapp.../lib/httplib2/__init__.py", line 1307, in _conn_request
   response = conn.getresponse()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/dist27/gae_override/httplib.py",
 
line 522, in getresponse
   **extra_kwargs)
 File "...myapp.../lib/httplib2/__init__.py", line 1106, in fixed_fetch
   validate_certificate=validate_certificate)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/urlfetch.py",
 
line 271, in fetch
   return rpc.get_result()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/apiproxy_stub_map.py",
 
line 613, in get_result
   return self.__get_result_hook(self)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/urlfetch.py",
 
line 378, in _get_fetch_result
   rpc.check_success()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/apiproxy_stub_map.py",
 
line 579, in check_success
   self.__rpc.CheckSuccess()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/apiproxy_rpc.py",
 
line 157, in _WaitImpl
   self.request, self.response)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 201, in MakeSyncCall
   self._MakeRealSyncCall(service, call, request, response)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 227, in _MakeRealSyncCall
   encoded_response = self._server.Send(self._path, encoded_request)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/appengine_rpc_httplib2.py",
 
line 247, in Send
   url, method=method, body=payload, headers=headers)
 File "...myapp.../lib/oauth2client/client.py", line 622, in new_request
   redirections, connection_type)
 File "...myapp.../lib/httplib2/__init__.py", line 1609, in request
   (response, content) = self._request(conn, authority, uri, request_uri, 
method, body, headers, redirections, cachekey)
 File "...myapp.../lib/httplib2/__init__.py", line 1351, in _request
   (response, content) = self._conn_request(conn, request_uri, method, 
body, headers)
 File "...myapp.../lib/httplib2/__init__.py", line 1307, in _conn_request
   response = conn.getresponse()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/dist27/gae_override/httplib.py",
 
line 522, in getresponse
   **extra_kwargs)
 File "...myapp.../lib/httplib2/__init__.py", line 1106, in fixed_fetch
   validate_certificate=validate_certificate)
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/api/urlfetch.py",
 
line 271, in fetch
   return rpc.get_result()
 File 
"/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-