Re: [google-appengine] Mail Service Deprecation?

[Emanuele Ziglioli]

yeah, one less reason to bet on App Engine: it's such a moving target.
We can't afford to rewrite critical parts of the code every few years just 
because APIs get deprecated.
Blobstore first, now this.
Mail has been the single most reliable feature for us over the past 5 years.
I understand the problem and costs might be caused by those few spammers 
who send millions of e-mails from GAE.
Why don't you kick them out?
Look at what the average user needs, and restrict the quota for cater for 
us.
Otherwise, just tell us what App Engine is and we'll figure out what to do 
in the future.
You keep telling us GAE's future is solid but then you strip it bits by 
bits.
Very frustrating.

On Wednesday, 4 May 2016 05:21:37 UTC+12, John Wheeler wrote:
>
> The Mail API is extremely important to us and provides satisfactory 
> deliverability for our use cases in its current form. For the amount of 
> mail we send, alternatives are still too expensive. -1 on shutting the API 
> down completely. We rely on it and find it useful.
>
> On Monday, May 2, 2016 at 1:43:21 PM UTC-7, Nick (Cloud Platform Support) 
> wrote:
>>
>> Hey Joshua,
>>
>> That's certainly an interesting idea! While I can't guarantee we'll 
>> implement it, be assured that we've heard this suggestion and will consider 
>> it. In the meantime, if a deprecation were announced, we would certainly 
>> welcome the opportunity to help as many users as possible easily migrate, 
>> in whatever form that looks like.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support 
>>
>> On Monday, May 2, 2016 at 11:35:35 AM UTC-4, Joshua Smith wrote:
>>>
>>> Suggestion for the team: If you do decide to do this, keep your existing 
>>> API and just swap in SendGrid as the underlying transport layer. Maybe we 
>>> could put our SendGrid API key (or however they deal with that) into the 
>>> console, or in app.yaml someplace, or something like that.
>>>
>>> I’ve got dozens of apps on GAE, and do not relish the idea of porting 
>>> them all to a different mail API. Especially since 99% of the mail sent is 
>>> just error logging reports sent to me.
>>>
>>> -Joshua
>>>
>>> On Apr 29, 2016, at 3:27 PM, 'Nick (Cloud Platform Support)' via Google 
>>> App Engine  wrote:
>>>
>>> Hey pdknsk,
>>>
>>> While I can't speak on any concrete plan to deprecate, the excellent 
>>> quality of SendGrid (even at the free tier), combined with our 
>>> 1-year-minimum deprecation policy timeline, should reassure everyone that 
>>> there's nothing significant to worry about. If this were to occur, you can 
>>> rest assured as well that we'd be happy to provide migration advice to 
>>> anybody needing it during the deprecation. 
>>>
>>> Cheers!
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Friday, April 29, 2016 at 10:17:03 AM UTC-4, pdknsk wrote:

 https://cloud.google.com/appengine/docs/python/release-notes

 > Google no longer accepts quota increase requests for the mail 
 service. Customers should use Sendgrid instead.

 Google will probably deprecate it soon, and close it a year later.

>>>
>>> -- 
>>> 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/6a7d9927-1924-4c87-94bc-115f0f7503d1%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/255327ac-939e-485f-8504-574792a52f2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: my git repo is empty

[Andrew Arrow]

thanks Nick! That worked. I have all my code now. You are an excellent googler.

On Tue, May 3, 2016 at 12:01 PM, 'Nick (Cloud Platform Support)' via
Google App Engine  wrote:
> Hey Andrew,
>
> So, we've taken a look at your repo internally and this is what we found:
> The Cloud Source Repository for the app was created in September (at project
> creation). It does not appear that it was ever connected to anything (commit
> from a local git repo, connected to github or bitbucket) (Source Repos
> populate from git commits / pushes). However, you should still be able to
> download any existing, uploaded apps, regardless of source repository. We
> tested with an app that was last updated in June:
>
> $ python ~/src/google_appengine/appcfg.py download_app -A $APPID -M $MODULE
> -V $VERSION .
>
> For this case:
>
> $ python ~/src/google_appengine/appcfg.py download_app -A static-1064 -M
> default -V 1 .
>
> Let me know if that works for you, and I'll be happy to assist further if
> not.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Friday, March 25, 2016 at 7:18:16 PM UTC-4, Andrew Arrow wrote:
>>
>> my site has been running for a year at:
>>
>> https://static-1064.appspot.com/
>>
>> I went to clone the repo:
>>
>> https://source.developers.google.com/p/static-1064/r/default
>>
>> and it clones an empty repo. Where's my code?
>>
> --
> 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/WCz0JORRoQ0/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/38225251-3daa-4ac7-8dcc-c582c675278b%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/CANPS%3DEwzzQy5zTmdj-gJ%2BKWOt5fa%2BvES8J_zmN%2B-qg%2Bx0QYcHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: my git repo is empty

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

Hey Andrew,

So, we've taken a look at your repo internally and this is what we found: 
The Cloud Source Repository for the app was created in September (at 
project creation). It does not appear that it was ever connected to 
anything (commit from a local git repo, connected to github or bitbucket) 
(Source Repos populate from git commits / pushes). However, you should 
still be able to download any existing, uploaded apps, regardless of source 
repository. We tested with an app that was last updated in June:

$ python ~/src/google_appengine/appcfg.py download_app -A $APPID -M $MODULE 
-V $VERSION . 

For this case: 

$ python ~/src/google_appengine/appcfg.py download_app -A static-1064 -M 
default -V 1 .

Let me know if that works for you, and I'll be happy to assist further if 
not.

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 25, 2016 at 7:18:16 PM UTC-4, Andrew Arrow wrote:
>
> my site has been running for a year at:
>
> https://static-1064.appspot.com/
>
> I went to clone the repo:
>
> https://source.developers.google.com/p/static-1064/r/default
>
> and it clones an empty repo. Where's my code?
>
>

-- 
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/38225251-3daa-4ac7-8dcc-c582c675278b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppEngine Application Problem

[Gnani Chaitanya]

Okie Nick, actually I am totally new to this and I got struck with that 
error and  that's the reason I have posted here, I would definitely try 
your solution and, thank you so much for the solution you have provided. 

Rgds,
Chaitanya

On Saturday, April 30, 2016 at 1:10:00 AM UTC+5:30, Nick (Cloud Platform 
Support) wrote:

> Hey Gnani,
>
> It sounds like you're using a third-party system which happens to use App 
> Engine as its back-end. I'm unfamiliar with the error messages you're 
> seeing and thus, can't offer much advice beyond repeating the advice of the 
> error message itself. 
>
> It's possible that in the Logs screen, you haven't selected the right 
> module or version of the app, or you have the log level set to the wrong 
> level. You should set the log level to "Any log level", check to see if 
> there are different versions / modules you can select in the menu drop-down 
> controls at the top of the Logs screen, and also make sure that you're 
> scrolling far back enough in time to the time-period when the error is said 
> to have occurred.
>
> It's worth noting at this time that the App Engine Google Groups forum 
> you're posting in is meant for more general, high level discussion of the 
> platform and services, not for specific issue technical support, so this 
> thread is somewhat off-topic and would be better posted to StackOverflow 
> . Nonetheless I'm happy to help. Feel free to 
> provide more information in your next reply and let me know how else I can 
> help, and I'll be happy to.
>
> Regards,
>
> Nick
> Cloud Platform Community Support 
>
> On Friday, April 29, 2016 at 1:43:57 AM UTC-4, Gnani Chaitanya wrote:
>>
>> Hi When I am trying to open the aggregate url then I am getting below the 
>> error, presently I am using free version and my data usage is within the 
>> limit.
>>
>> A problem has occurred that prevents your AppEngine application from 
>> responding. Your application may have exceeded its per-minute or daily 
>> usage quotas.
>>
>> Please visit your application dashboard at *Google AppEngine* 
>> . The *Billing Status* section will 
>> indicate what daily or per-minute usage limits your application has 
>> exceeded.
>>
>> If your application's usage limits have not been exceeded, then look for 
>> performance issues within Google AppEngine cloud services. From your 
>> application dashboard, click on the the *System Status* link on the left 
>> sidebar under the *Resources* heading. This will report problems with 
>> Google AppEngine cloud services.
>>
>> If neither of those indicate any problems, then your application's Logs 
>> may; these are reachable from the dashboard via the *Logs* link on the 
>> left sidebar under the *Main* heading.
>>
>>
>> I am unable to find the erroe Please suggest me.
>>
>>
>> Rgds,
>>
>> Chaitanya.D
>>
>

-- 
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/4a8f9d9a-0a08-4305-8da0-4f78ff1d7cd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Mail Service Deprecation?

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

Hey John,

Thanks for your feedback. We definitely appreciate hearing from users on 
issues like these. As one helpful recommendation which you might not be 
aware of, I can link to SendGrid's documentation on their free tier 
, which is awesome in the amount of quota / 
features when compared to even the free tier of the App Engine Mail API, so 
do consider checking it out if you're concerned about costs.

Sincerely,

Nick
Cloud Platform Community Support

On Tuesday, May 3, 2016 at 1:21:37 PM UTC-4, John Wheeler wrote:
>
> The Mail API is extremely important to us and provides satisfactory 
> deliverability for our use cases in its current form. For the amount of 
> mail we send, alternatives are still too expensive. -1 on shutting the API 
> down completely. We rely on it and find it useful.
>
> On Monday, May 2, 2016 at 1:43:21 PM UTC-7, Nick (Cloud Platform Support) 
> wrote:
>>
>> Hey Joshua,
>>
>> That's certainly an interesting idea! While I can't guarantee we'll 
>> implement it, be assured that we've heard this suggestion and will consider 
>> it. In the meantime, if a deprecation were announced, we would certainly 
>> welcome the opportunity to help as many users as possible easily migrate, 
>> in whatever form that looks like.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support 
>>
>> On Monday, May 2, 2016 at 11:35:35 AM UTC-4, Joshua Smith wrote:
>>>
>>> Suggestion for the team: If you do decide to do this, keep your existing 
>>> API and just swap in SendGrid as the underlying transport layer. Maybe we 
>>> could put our SendGrid API key (or however they deal with that) into the 
>>> console, or in app.yaml someplace, or something like that.
>>>
>>> I’ve got dozens of apps on GAE, and do not relish the idea of porting 
>>> them all to a different mail API. Especially since 99% of the mail sent is 
>>> just error logging reports sent to me.
>>>
>>> -Joshua
>>>
>>> On Apr 29, 2016, at 3:27 PM, 'Nick (Cloud Platform Support)' via Google 
>>> App Engine  wrote:
>>>
>>> Hey pdknsk,
>>>
>>> While I can't speak on any concrete plan to deprecate, the excellent 
>>> quality of SendGrid (even at the free tier), combined with our 
>>> 1-year-minimum deprecation policy timeline, should reassure everyone that 
>>> there's nothing significant to worry about. If this were to occur, you can 
>>> rest assured as well that we'd be happy to provide migration advice to 
>>> anybody needing it during the deprecation. 
>>>
>>> Cheers!
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Friday, April 29, 2016 at 10:17:03 AM UTC-4, pdknsk wrote:

 https://cloud.google.com/appengine/docs/python/release-notes

 > Google no longer accepts quota increase requests for the mail 
 service. Customers should use Sendgrid instead.

 Google will probably deprecate it soon, and close it a year later.

>>>
>>> -- 
>>> 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/6a7d9927-1924-4c87-94bc-115f0f7503d1%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/da014d21-09e0-4caf-b026-31f935222978%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Mail Service Deprecation?

[John Wheeler]

The Mail API is extremely important to us and provides satisfactory 
deliverability for our use cases in its current form. For the amount of 
mail we send, alternatives are still too expensive. -1 on shutting the API 
down completely. We rely on it and find it useful.

On Monday, May 2, 2016 at 1:43:21 PM UTC-7, Nick (Cloud Platform Support) 
wrote:
>
> Hey Joshua,
>
> That's certainly an interesting idea! While I can't guarantee we'll 
> implement it, be assured that we've heard this suggestion and will consider 
> it. In the meantime, if a deprecation were announced, we would certainly 
> welcome the opportunity to help as many users as possible easily migrate, 
> in whatever form that looks like.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support 
>
> On Monday, May 2, 2016 at 11:35:35 AM UTC-4, Joshua Smith wrote:
>>
>> Suggestion for the team: If you do decide to do this, keep your existing 
>> API and just swap in SendGrid as the underlying transport layer. Maybe we 
>> could put our SendGrid API key (or however they deal with that) into the 
>> console, or in app.yaml someplace, or something like that.
>>
>> I’ve got dozens of apps on GAE, and do not relish the idea of porting 
>> them all to a different mail API. Especially since 99% of the mail sent is 
>> just error logging reports sent to me.
>>
>> -Joshua
>>
>> On Apr 29, 2016, at 3:27 PM, 'Nick (Cloud Platform Support)' via Google 
>> App Engine  wrote:
>>
>> Hey pdknsk,
>>
>> While I can't speak on any concrete plan to deprecate, the excellent 
>> quality of SendGrid (even at the free tier), combined with our 
>> 1-year-minimum deprecation policy timeline, should reassure everyone that 
>> there's nothing significant to worry about. If this were to occur, you can 
>> rest assured as well that we'd be happy to provide migration advice to 
>> anybody needing it during the deprecation. 
>>
>> Cheers!
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Friday, April 29, 2016 at 10:17:03 AM UTC-4, pdknsk wrote:
>>>
>>> https://cloud.google.com/appengine/docs/python/release-notes
>>>
>>> > Google no longer accepts quota increase requests for the mail service. 
>>> Customers should use Sendgrid instead.
>>>
>>> Google will probably deprecate it soon, and close it a year later.
>>>
>>
>> -- 
>> 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/6a7d9927-1924-4c87-94bc-115f0f7503d1%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/24a0e570-f271-456d-a889-7df5fe56216d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Flexible environment: Manual scaling doesn't work

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

A link to the App Engine Public Issue Tracker 
, just in case you 
haven't visited it before.

On Monday, May 2, 2016 at 2:39:57 PM UTC-4, Mike Chang wrote:
>
> I need a worker node that is always on. From my understanding Google 
> managed is the only option on Google Cloud as the servers are always on.
>
> In the beginning I ran google preview app deploy, and 20 or so instances 
> pop up. I then have this with the node on docker image:
>
> runtime: custom
> vm: true
> api_version: 2
> env_variables:
>   runLocal: false
> manual_scaling:
>   instances: 1
>
> Now only one instance shows up after deploy, but as soon as the server 
> gets the first web request all 20 starts spawning again. This is not what I 
> expected of the manual_scaling config. What am I missing?
> 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/e6b5b0a3-1d88-4835-b86b-49f19fab1f36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Flexible environment: Manual scaling doesn't work

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

Hey Mike,

I'll echo Evan Jones here and suggest that it could be that the previous 
version (without manual_scalin, instances: 1) is still the default version 
for that module, and the request is going to that version, spawning the 
instances. However, if this isn't the case, you should open a Public Issue 
Tracker issue with "type-production" label and include your app id, the 
relevant versions, screenshots if possible, etc. and we can take a look at 
potentially determining the cause / a solution.

Regards,

Nick
Cloud Platform Community Support

On Monday, May 2, 2016 at 2:39:57 PM UTC-4, Mike Chang wrote:
>
> I need a worker node that is always on. From my understanding Google 
> managed is the only option on Google Cloud as the servers are always on.
>
> In the beginning I ran google preview app deploy, and 20 or so instances 
> pop up. I then have this with the node on docker image:
>
> runtime: custom
> vm: true
> api_version: 2
> env_variables:
>   runLocal: false
> manual_scaling:
>   instances: 1
>
> Now only one instance shows up after deploy, but as soon as the server 
> gets the first web request all 20 starts spawning again. This is not what I 
> expected of the manual_scaling config. What am I missing?
> 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/568e4d50-57ae-42c5-9d7b-549accecd915%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] upload data via appcfg

[Rotem Vilkovski]

Hey, 

I'm trying to upload data to local Datastore using the file I've downloaded 
from out production using appcfg download_data. 
I get an error almost every time about ProtocolBufferDecodeError: 
corrupted. Sometimes (on the same file) it is just working. This is really 
disturbing and I'd like to know if there's another way to use my local 
datastore with my local file and having a solution for this problem please. 
Everytime I update an entity in production and want to update my local 
Datastore it takes me for 10-20 tries.

Stack trace:
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/tools/adaptive_thread_pool.py",
 
line 172, in WorkOnItems
status, instruction = item.PerformWork(self.__thread_pool)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/tools/bulkloader.py", 
line 750, in PerformWork
transfer_time = self._TransferItem(thread_pool)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/tools/bulkloader.py", 
line 921, in _TransferItem
self.request_manager.PostEntities(self.content)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/tools/bulkloader.py", 
line 1396, in PostEntities
datastore.Put(entities)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/api/datastore.py", 
line 606, in Put
return PutAsync(entities, **kwargs).get_result()
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/datastore/datastore_rpc.py",
 
line 923, in get_result
results = self.__rpcs[0].get_result()
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/api/apiproxy_stub_map.py",
 
line 613, in get_result
return self.__get_result_hook(self)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/datastore/datastore_rpc.py",
 
line 1881, in __put_hook
self.check_rpc_success(rpc)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/datastore/datastore_rpc.py",
 
line 1371, in check_rpc_success
rpc.check_success()
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/api/apiproxy_stub_map.py",
 
line 579, in check_success
self.__rpc.CheckSuccess()
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/api/apiproxy_rpc.py", 
line 157, in _WaitImpl
self.request, self.response)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 286, in MakeSyncCall
handler(request, response)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 460, in _Dynamic_Put
'datastore_v3', 'Put', put_request, put_response)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 201, in MakeSyncCall
self._MakeRealSyncCall(service, call, request, response)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/ext/remote_api/remote_api_stub.py",
 
line 228, in _MakeRealSyncCall
response_pb.ParseFromString(encoded_response)
  File 
"/home/rotem/Desktop/google_appengine/google/net/proto/ProtocolBuffer.py", 
line 140, in ParseFromString
self.MergeFromString(s)
  File 
"/home/rotem/Desktop/google_appengine/google/net/proto/ProtocolBuffer.py", 
line 152, in MergeFromString
self.MergePartialFromString(s)
  File 
"/home/rotem/Desktop/google_appengine/google/net/proto/ProtocolBuffer.py", 
line 168, in MergePartialFromString
self.TryMerge(d)
  File 
"/home/rotem/Desktop/google_appengine/google/appengine/ext/remote_api/remote_api_pb.py",
 
line 770, in TryMerge
d.skipData(tt)
  File 
"/home/rotem/Desktop/google_appengine/google/net/proto/ProtocolBuffer.py", 
line 673, in skipData
raise ProtocolBufferDecodeError, "corrupted"
ProtocolBufferDecodeError: corrupted


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/43b0721d-0848-49fa-9db3-99010adf5c76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Blank page on PHP Hello World

[Radu Popa]

I had the same problem : I has giving the path to php not tophp-cgi

Thank you for your answers.

On Thursday, December 12, 2013 at 1:20:22 AM UTC+1, Andrew Jessup wrote:
>
> You need to specify the php-cgi binary, not the PHP binary
>
> On Tuesday, 10 December 2013 20:02:33 UTC-8, Vinny P wrote:
>>
>> On Fri, Dec 6, 2013 at 7:10 PM, Jefrey Sobreira 
>>  wrote:
>>
>>> *The path specified with the --php_executable_path flag () does not 
>>> exist.* 
>>>
>> So I changed the command line to:
>>> python dev_appserver.py helloworld/ --php_executable_path /usr/bin/php
>>> (i tired as root and also as non-root)
>>> Now that error isn't appearing anymore. But all I see is a blank page...
>>>
>>>
>>
>> Can you run a search for the PHP executable (i.e. *run sudo find / -name 
>> php-cgi* )? I was under the impression that PHP installs under 
>> *usr/bin/php-cgi*.
>>  
>>  
>> -
>> -Vinny P
>> Technology & Media Advisor
>> Chicago, IL
>>
>> App Engine Code Samples: http://www.learntogoogleit.com
>>
>>

-- 
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/dc7b7c92-cc40-44c5-9ee4-33948a56648d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Datastore Admin stopped working

[Michael Steurer]

Thanks for your support Adam, I have posted the issue. 

Michael

On Tuesday, May 3, 2016 at 12:06:26 AM UTC+2, Adam (Cloud Platform Support) 
wrote:
>
> I see this too. The Datastore Admin has a dependency on the old builtin 
> mapreduce library which can't be enabled anymore. It does not work with the 
> latest appengine-mapreduce library even when fixing the handler paths 
> (/mapreduce -> /_ah/mapreduce) in the include.yaml. Vendoring the old 
> mapreduce builtin from the SDK into the project causes problems with 
> imports.
>
> It looks like deploying the datastore admin manually isn't a trivial task. 
> I'll keep trying to get it to work and will update this thread if I make 
> any progress. It might be possible to use an old, deprecated SDK version 
> that still allows 'mapreduce: on' in the list of builtins.
>
> For now, I would advise posting a production issue on the issue tracker 
> and requesting a manual restore of the 'ah-builtin-python-bundle' version.
>
> On Monday, May 2, 2016 at 10:57:32 AM UTC-4, Michael Steurer wrote:
>>
>> Hi Adam, hi Josh,
>> thanks for your help. We've deployed the new version according to your 
>> suggestions and the Datastore Admin works fine again. Still, we can not do 
>> any backups. Mapreduce gets kicked off (in the logs of the new datastore 
>> version we see /_ah/mapreduce/kickoffjob_callback/$THIS_IS_MY_ID) and the 
>> state of the backup in the Datastore Admin is pending. We can also see an 
>> active operation in the "Active Operations" section but it never finishes 
>> (0 steps completed, 1 active). The link behind this job 
>> https://datastore-admin-dot-$
>> MY_PROJECT.appspot.com/_ah/mapreduce/detail?mapreduce_id=$THIS_IS_MY_ID 
>> redirects back to the Datastore Admin. 
>>
>> What are we missing?
>>
>> Cheers Michael
>>
>>
>> On Saturday, April 30, 2016 at 8:57:47 PM UTC+2, Adam (Cloud Platform 
>> Support) wrote:
>>>
>>> Also, regarding the inconsistencies in the console 
>>> for 'ah-builtin-python-bundle', feel free to post to the issue tracker 
>>>  so we can grab 
>>> the app ID and investigate the specific project.
>>>
>>> On Saturday, April 30, 2016 at 2:53:36 PM UTC-4, Adam (Cloud Platform 
>>> Support) wrote:

 Thanks Josh, I didn't think the source for this was available as 
 'appcfg.py 
 download_app' is purposely blocked for 'ah-builtin-python-bundle', but 
 it was right in the SDK all along! 

 Although restoring to 'ah-builtin-python-bundle' won't work due to 
 'ah-builtin' being a reserved version name prefix (the console button will 
 remain broken), you can still restore to a different version and access 
 the 
 datastore admin functionality that way. The source is available in the App 
 Engine Python SDK under 
 $GAE_SDK_PATH/google/appengine/ext/datastore_admin or in the Google 
 Cloud SDK under 
 $CLOUD_SDK_PATH/platform/google_appengine/google/appengine/ext/datastore_admin.
  
 You can add a simple app.yaml to deploy:

 application: my-project-id
 version: datastore-admin
 runtime: python27
 api_version: 1
 threadsafe: yes

 handlers:
 - url: .*
   script: main.APP

 On Friday, April 29, 2016 at 3:04:18 PM UTC-4, joshuamo wrote:
>
> For anyone who is or has been affected by an accidental deletion of 
> datastore admin, a workaround is to deploy datastore admin as a separate 
> version or module of your app.  The code for datastore admin is provided 
> in 
> the Cloud SDK:  $CLOUD_SDK_PATH/google/appengine/ext/datastore_admin
>
>
>
> On Fri, Apr 29, 2016 at 10:45 AM, Michael Steurer wrote:
>
>> Adam,
>> unfortunately the 'ah-builtin-python-bundle'  is visible under 
>> 'Versions'. At least it was visible for me in the afternoon - now it 
>> disappeared again. I can provide you with a screenshot if you like. From 
>> my 
>> perspective this looks like a bug in Console.
>>
>> Cheers Michael
>>
>> On Wednesday, April 27, 2016 at 11:12:33 PM UTC+2, Christian F. Howes 
>> wrote:
>>>
>>> Adam,
>>>
>>> since this is a required version for administering our applications, 
>>> can Google put in safeties to prevent it from being deleted?  It's 
>>> pretty 
>>> scary that it can accidently be deleted and not be re-created.
>>>
>>> thanks,
>>>
>>> christian 
>>>
>> -- 
>> 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