Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

[Ryan B]

I revisited this again recently and wrote a drop-in Flask extension that 
serves app.yaml static file and directory handlers: flask-gae-static 
<https://github.com/snarfed/flask-gae-static>. Feedback is welcome!

On Sunday, October 31, 2021 at 10:39:33 AM UTC-7 Ryan B wrote:

> Resurrecting this year and a half old thread to plug 
> https://github.com/XeoN-GHMB/app_server , a little dev_appserver 
> replacement that wraps your existing local app server and adds static file 
> serving that supports app.yaml static_* handlers. Sounds similar to the 40 
> line middleware you mentioned.
>
> I was finally forced to migrate away from dev_appserver due to the 
> continued degrading of the Python 2 ecosystem. Specifically, when I 
> migrated to macOS Monterey, dev_appserver failed to start and complained, 
> Cannot 
> use the Cloud Datastore Emulator because the packaged grpcio is 
> incompatible to this system. Please install grpcio using pip. I tried to 
> install grpcio for Python 2, but Montery doesn't include Python 2's pip, 
> and easy_install couldn't install it. app_server to the rescue!
>
> On Sunday, December 15, 2019 at 9:22:49 AM UTC-8 re...@el-tramo.be wrote:
>
>> Hi Ryan,
>>  
>>
>>> understood, but using a different static file server is not great. it 
>>> makes local development diverge significantly from production. local no 
>>> longer uses or tests app.yaml's static file handlers, but prod does, so 
>>> bugs will eventually pop up that only happen in production, and are thus 
>>> harder to test for and debug.
>>>
>>
>> The way I solve this is to have a little piece of middleware (only in dev 
>> mode) that loads app.yaml and serves the static_* handlers statically. The 
>> basic logic (I might not be handling all cover cases, but it works for me) 
>> is pretty simple, and the entire middleware class takes about 40 lines of 
>> code.
>>
>> thanks,
>> Remko
>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/369fedf4-ea0b-46a3-a62e-1e629af518cfn%40googlegroups.com.

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

[Ryan B]

Resurrecting this year and a half old thread to plug 
https://github.com/XeoN-GHMB/app_server , a little dev_appserver 
replacement that wraps your existing local app server and adds static file 
serving that supports app.yaml static_* handlers. Sounds similar to the 40 
line middleware you mentioned.

I was finally forced to migrate away from dev_appserver due to the 
continued degrading of the Python 2 ecosystem. Specifically, when I 
migrated to macOS Monterey, dev_appserver failed to start and complained, 
Cannot 
use the Cloud Datastore Emulator because the packaged grpcio is 
incompatible to this system. Please install grpcio using pip. I tried to 
install grpcio for Python 2, but Montery doesn't include Python 2's pip, 
and easy_install couldn't install it. app_server to the rescue!

On Sunday, December 15, 2019 at 9:22:49 AM UTC-8 re...@el-tramo.be wrote:

> Hi Ryan,
>  
>
>> understood, but using a different static file server is not great. it 
>> makes local development diverge significantly from production. local no 
>> longer uses or tests app.yaml's static file handlers, but prod does, so 
>> bugs will eventually pop up that only happen in production, and are thus 
>> harder to test for and debug.
>>
>
> The way I solve this is to have a little piece of middleware (only in dev 
> mode) that loads app.yaml and serves the static_* handlers statically. The 
> basic logic (I might not be handling all cover cases, but it works for me) 
> is pretty simple, and the entire middleware class takes about 40 lines of 
> code.
>
> thanks,
> Remko
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5262282a-44df-46e5-8bff-8de519f618ccn%40googlegroups.com.

[google-appengine] Disabling TLS 1.0

[Patrice B]

June 2018 was the deadline for discontinuing the use of TLS 1.0, (
https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls)
 
and after that date numerous audit tools point the use of TLS 1.0 and 1.1 
as alerts.  
It is now July 2021, 3 years passed the deadline, and it seems App Engine 
is still using both.A number of GAE users have asked how disabling old 
TLS versions could be achieved, but the answers they got are not quite 
satisfactory.   
Some say "you should create a ticket with GCP, but you will have to have a 
support subscription first" (
https://serverfault.com/questions/1003762/how-to-disable-tls-1-0-for-google-app-engine
 
or https://stackoverflow.com/questions/58073141/how-to-update-tls-version).   

Others say the solution is to set up an SSL policy, which would only be 
possible after using  Cloud Load Balancing and serverless NEGS.  That would 
be a lot of trouble, plus added costs, for the sole purpose of making our 
GAE based application compliant with 2018 guidelines. 
But these are just end-user advice given on SO, I would be happy to get the 
official word from GCP on that matter.   It is quite unusual to see GAE 
being 3 years late on a security related issue.
Thank you for your input,

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/468f1aeb-0563-4546-ac3e-a3faf9d09739n%40googlegroups.com.

[google-appengine] Re: Did the standard environment auto scaling scheduler change recently?

[Ryan B]

Thanks for looking! I made that app.yaml change (including min_pending_latency) 
after I noticed the scheduling change. It successfully brought my instance 
count back down, but it didn't explain what caused the initial increase. I'm 
still curious about that.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e903cb28-4536-4307-b618-37ccc9371cado%40googlegroups.com.

[google-appengine] Re: Did the standard environment auto scaling scheduler change recently?

[Ryan B]

I changed my autoscaling settings to be much more aggressive, below, and 
steady state instance count is back down to more or less where it was 
before. I'm stil very curious what changed on App Engine's end, but I'm at 
least out of the woods for now.

automatic_scaling:
 max_idle_instances: 1
 target_cpu_utilization: .9
 min_pending_latency: 500ms
 max_concurrent_requests: 30 

On Monday, June 28, 2021 at 10:27:13 AM UTC-7 Ryan B wrote:

> Hi all! The steady state instance count for a couple of my apps (on Python 
> 3 Standard) increased recently, over the last week or two, without any 
> obvious code or architecture or traffic or load or change on my end. Did 
> the App Engine scheduler itself change recently?
>
> Here's the active instance count for one app. I haven't deployed a new 
> version since April, and load (etc) haven't meaningfully changed either.
>
> [image: 123658491-a116ad80-d7e6-11eb-8805-9ef33584cff7.png]
>
> Here's another. I deploy this one more often, multiple times a week, but 
> nothing related to utilization recently that I can think of, and there 
> haven't been any other architectural, app config, or load for months.
>
> [image: 123658263-657be380-d7e6-11eb-89b4-a8e334e0c5f8.png]
>
> Here are the app.yaml files; neither has changed since March, when I 
> upgraded both apps to Python 3.9.
> https://github.com/snarfed/bridgy-fed/blob/main/app.yaml
> https://github.com/snarfed/bridgy/blob/main/app.yaml
>
> If the scheduler did change, any chance anyone knows how to configure it 
> to get my steady state instance counts back to where they were before?
>
> Thanks in advance!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/beb53b01-887e-4e74-8e07-68d9d2b262dan%40googlegroups.com.

Re: [google-appengine] Re: Appengine Dashboard broken?

[Ryan B]

Same here. The Current load, Application Errors, Server Errors, and Client 
Errors sections of the dashboard have been empty in pretty much all of my 
projects for a week or so now. Example project ids: brid-gy, 
bridgy-federated, granary-demo, oauth-dropins.

On Saturday, October 10, 2020 at 1:38:08 PM UTC-7 vit@gmail.com wrote:

> Hi.
>
> project: telegram-email
>
> [image: 1.PNG]
>
> суббота, 10 октября 2020 г. в 22:54:28 UTC+4, yananc: 
>
>> Hello, 
>>
>> We have received reports of the similar issue recently. The issue seemed 
>> to be transient and disappeared after a while. Does the issue still persist 
>> in your case? If so, would you please provide more information so we could 
>> look into it? Thank you.
>>
>>
>> On Thursday, October 8, 2020 at 3:40:44 PM UTC-4 vit@gmail.com wrote:
>>
>>> Same issue.
>>>
>>> Also:
>>>
>>> Client Errors 
>>> This app has not received any client errors in the last 24 hours.
>>>
>>> четверг, 8 октября 2020 г. в 21:08:56 UTC+4, linus@epspot.com: 
>>>
 Works again for me now.magic.

 Den tor 8 okt. 2020 10:19troberti  skrev:

> We have the same issue, for all our Appengine projects.
>
> On Wednesday, October 7, 2020 at 11:02:47 PM UTC+2 linus@gmail.com 
> wrote:
>
>> In cloud console, Appengine Dasboard for a few days it says:
>>
>> Current load
>>
>> This app has not received any requests in the last 24 hours.
>>
>> This is obviously wrong since I have loads of requests in the logs 
>> and I get billed for them as well.
>>
>> This used to show the top 10 or 20 requested urls, is it broken?
>>
>> The Dashboard in Home works as expected.
>>
>>
>> -- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/81428dd7-9003-4dd7-98de-2a52042cdd9en%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2c693f88-402f-417e-a67e-1ae77c7a2bb9n%40googlegroups.com.

[google-appengine] Re: App Engine HTTP issues

[Ryan B]

Looks like they're in the middle of a partial outage right now. 
https://status.cloud.google.com/

On Tuesday, October 6, 2020 at 8:08:44 AM UTC-7 kris...@escapemasters.co.nz 
wrote:

> Hi All,
> In the past hour we faced on standard java App Engine with numerous 
> unexpected error as java.net.UnknownHostException, ServiceConfigException: 
> java.net.UnknownHostException: servicemanagement.googleapis.com. On our 
> side nothing has been changed. 
> Moreover, when I tried to migrate the traffic to an older version the 
> traffic migration failed in half way.
>
> Who knows anything about this kind of outage?
>
> Thanks in advance,
> Krisztián Guba
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/435fad9f-0b88-4833-91c0-05756d89d0d7n%40googlegroups.com.

[google-appengine] Re: appspot.com started rejecting SSL without SNI causing U-Blox IoT modems to fail, since May

[Ryan B]

Interesting! And concerning. I'd definitely care about this too.

Just as another data point, I checked one of my apps that serves from both 
a custom domain (https://brid.gy/) and appspot 
(https://brid-gy.appspot.com/), and Qualys's SSL Labs test shows that the 
appspot subdomain is still happily supporting traditional IP-based SSL, 
without SNI.

   - 
   
https://www.ssllabs.com/ssltest/analyze.html?d=brid%2dgy.appspot.com=2607%3af8b0%3a4005%3a808%3a0%3a0%3a0%3a2014=on
   - 
   
https://www.ssllabs.com/ssltest/analyze.html?d=brid.gy=2001%3a4860%3a4802%3a32%3a0%3a0%3a0%3a15=on

On Tuesday, July 28, 2020 at 5:07:30 AM UTC-7 bjorn...@gmail.com wrote:

> We have a large fleet of *U-Blox* IoT modem-equipped devices out there, 
> calling in to our backend on AppEngine, using SSL to .
> appspot.com (we don't have any custom SSL cert or managed cert).
>
> Up until May 26 or so this year this has worked fine, after that some 
> endpoints started failing the SSL handshake, and the problem became worse 
> and worse until the entire fleet was disabled.
>
> U-Blox managed to trace it to a failing SSL negotiation, and that their 
> modems don't support the SSL SNI (Server Name Identification) option, which 
> is required normally to differ between certs on a server that has multiple 
> certs on the same IP.
>
> Sure enough, I checked with openssl s_client -noservername and it fails to 
> appspot.com now -* it doesn't provide the normal default cert of 
> *.appspot.com  anymore* when no SNI is given (just 
> the No SNI provided; please fix your client. message).
>
> I didn't find anything in the AppEngine release notes about this change.
>
> Now, this is a tricky because yes, SNI has been around since 2002 and I 
> think it's even mandatory in TLSv1.3. On the other hand, there must be 
> hundreds of thousands of U-Blox modems out there that doesn't support this, 
> and the companies that have built IoT products around AppEngine and U-Blox 
> (like us) will start to see their fleets fail.
>
> *Would it be possible to re-instate a default handling of the SSL 
> endpoints on appspot.com  to provide a default cert of 
> *.appspot.com  ? *
>
> We had to go non-encrypted as a panic work-around, which is obviously not 
> desirable.
>
> Another work-around is to purchase a completely separate IP and custom SSL 
> cert; this would remove the semantical requirement of SNI but it would be 
> helpful to confirm if there would still be a technical requirement for it 
> due to the way the AppEngine SSL endpoints are configured in that case.
>
> Best regards
> /Bjorn
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a08842e6-87d3-4428-bafd-971d93d2b7f4n%40googlegroups.com.

[google-appengine] 403 error when trying to list metrics in different project through monitoring api from app engine

['B' via Google App Engine]

I am using an app engine standard application written in python2.7 to 
collect monitoring metrics from different projects. I am running this from 
cloud shell The app engine application is deployed in projectA and it is 
able to collect the metrics from projectA through the below call

service = build('monitoring', 'v3', cache_discovery=True)
project_name = 'projects/{project_id}'.format(
project_id=project_id
)

metrics = service.projects().metricDescriptors().list(
 name=project_name,
 pageSize=config.PAGE_SIZE,
 pageToken=next_page_token
).execute()

This call is written in a loop, Now i need to collect ProjectB metrics, I 
have owner access to ProjectB. When ProjectB is passed as parameter to 
project_id I am getting this below error:

logMessage: "Error: https://monitoring.googleapis.com/v3/projects/ProjectB/metricDescriptors?pageToken==json=500
 returned "Permission monitoring.metricDescriptors.list denied (or the resource 
may not exist).">" 
severity: "ERROR" 
sourceLocation: {
 file: 
"/base/data/home/apps/s~ProjectA/list-metrics:20200706t123743.427891295940019389/main.py"
  
 functionName: "post"  
 line: "665"  
}
time: "2020-07-06T16:10:43.724399Z"

I am not sure what should be done to make this work? I am very new to 
google cloud and its apis and also new to app engine,python2.7 kindly help, 
Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7875ee66-8b4b-4b96-8390-00fe42479e17o%40googlegroups.com.

[google-appengine] Re: How to remove custom domain from project

[Patrice B]

Hello,

Same problem here: cannot remove custom domain from project.   Is there no 
solution ? 

The story is as follows:  (1) need to have a subdomain of our client's 
domain point to our App Engine project, so we ask our client to add CNAME 
records to prove ownership, then we add subdomain to list of custom domain 
names for an app engine project, (2) client company then closes and domain 
name is not even registered anymore, (3) cannot remove client subdomain 
from list of custom domain names.   So 10 years from now, this custom 
domain name will still be bound to our project ?  What if someone else buys 
this domain, and defines CNAME records so that it reaches our project ? 

Is there no way out of this ? 

I believe this rule is not appropriate at all :  the owner of an app engine 
project should be allowed to remove a custom domain from his project, no 
matter if he can prove ownership or not.   I understand the need to prove 
ownership when trying to attach a new domain, but not when trying to detach.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/72309bff-e725-463b-a813-c3b60b03e92co%40googlegroups.com.

Re: [google-appengine] Re: Any more migration stories?

[Ryan B]

hey alex, long time no see! yup, tests were a life saver for me in these 
migrations. probably also the single best technique i know of for software 
productivity and quality over time in general.

re testing jinja templates, i've gradually leaned toward writing more and 
more web app unit tests at the HTTP request level, integration test style, 
which makes testing templates and HTML output easier. set up the context, 
make the request, check the HTML output. example:

https://github.com/snarfed/bridgy/blob/dab476ec1f7cfd261341f381de645edaf3d97599/tests/test_app.py#L375-L381

On Thursday, May 7, 2020 at 4:06:25 PM UTC-7, Alex Martelli wrote:
>
> Just as a personal note (I'm a Googler but also help maintain App Engine 
> non-profit sites in my spare time etc), I enthusiastically agree that the 
> migration suddenly validated my own long-standing obsession with more and 
> more (automated, esp. unit) testing -- suddenly, that boring test activity 
> became a life-saver, catching most glitches well before moving into 
> staging, much less prod.
>
> Unsurprisingly the main exceptions (which we had to catch over time) were 
> about code hidden in Jinjia templates, which I had never thought of 
> subjecting to the same ambitious, aspirational standards of coverage I hold 
> Python code in .py files to.
>
> There ARE ways to unit test code hidden in Jinja, and I plan to research 
> and apply them, but the error I made as a tech lead in not insisting on 
> such testing earlier is yet another confirmation of how precious unit tests 
> ARE!-)
>
> Alex
>
> On Thu, May 7, 2020 at 3:42 PM Ryan B > 
> wrote:
>
>> i was also extremely fortunate that pretty much all of these apps had 
>> solid unit test coverage, which automatically found the vast majority of 
>> code that needed updating. if i'd had to resort to "rigorous search and 
>> runtime errors," as joshua mentioned, i'd probably be a lot more frustrated.
>>
>> On Thursday, May 7, 2020 at 3:38:57 PM UTC-7, Ryan B wrote:
>>>
>>> hi charlie, thanks for asking!
>>>
>>> my experience was similar to joshua's, if not quite so extreme. i've 
>>> migrated seven or so apps now, the largest weighing in at 26kloc. the big 
>>> differences in API availability and compatibility were the most painful 
>>> parts, followed by changes and difficulties with local development, as 
>>> joshua mentioned.
>>>
>>> here are a handful of threads and issues with details:
>>>
>>>- local dev, deployment:
>>>- 
>>>   
>>> https://groups.google.com/d/topic/google-appengine/BJDE8y2KISM/discussion 
>>>   (fast startup or static assets, choose one?)
>>>   - https://issuetracker.google.com/issues/144150446 (dev_appserver 
>>>   patch to fix this)
>>>   - https://issuetracker.google.com/issues/146780347 (Cloud Build 
>>>   uses stale GitHub clones)
>>>   - logging:
>>>- 
>>>   
>>> https://groups.google.com/d/topic/google-appengine/xTDZ-da27ow/discussion 
>>>   (difficulties reading GAE app logs from the logging API)
>>>   - 
>>>   
>>> https://stackoverflow.com/questions/58753378/how-to-deserialize-app-engine-application-logs-from-stackdriver-logging-api
>>>   - https://github.com/googleapis/google-cloud-python/issues/2572
>>>   - https://github.com/snarfed/bridgy/issues/940 (my app's feature 
>>>   that uses logging API is now way slower)
>>>   - 
>>>   
>>> https://groups.google.com/forum/#!topic/google-stackdriver-discussion/k96EQHCacKM
>>>  
>>>   (can't request increase to logs API read quota)
>>>   - 
>>>   
>>> https://stackoverflow.com/questions/59398479/why-is-my-app-engine-app-hitting-the-stackdriver-logging-256kb-limit
>>>   - https://github.com/snarfed/bridgy/issues/904 (originally 
>>>   ingested way more logs than i expected)
>>>   - ndb, misc growing pains:
>>>- https://github.com/googleapis/python-ndb/issues/263
>>>   - https://github.com/googleapis/python-ndb/issues/238
>>>   - https://github.com/googleapis/python-ndb/issues/277
>>>   - https://github.com/googleapis/python-ndb/issues/376
>>>   - https://github.com/googleapis/python-ndb/issues/267
>>>- cloud tasks missing local emulator, transactional tasks
>>>   - 
>>>   
>>> https://cloud.google.com/tasks/docs/migrating#features_in_task_queues_not_yet_available_via
>>>- migration increased our frontend instan

[google-appengine] Re: Any more migration stories?

[Ryan B]

i was also extremely fortunate that pretty much all of these apps had solid 
unit test coverage, which automatically found the vast majority of code 
that needed updating. if i'd had to resort to "rigorous search and runtime 
errors," as joshua mentioned, i'd probably be a lot more frustrated.

On Thursday, May 7, 2020 at 3:38:57 PM UTC-7, Ryan B wrote:
>
> hi charlie, thanks for asking!
>
> my experience was similar to joshua's, if not quite so extreme. i've 
> migrated seven or so apps now, the largest weighing in at 26kloc. the big 
> differences in API availability and compatibility were the most painful 
> parts, followed by changes and difficulties with local development, as 
> joshua mentioned.
>
> here are a handful of threads and issues with details:
>
>- local dev, deployment:
>- 
>   
> https://groups.google.com/d/topic/google-appengine/BJDE8y2KISM/discussion 
>   (fast startup or static assets, choose one?)
>   - https://issuetracker.google.com/issues/144150446 (dev_appserver 
>   patch to fix this)
>   - https://issuetracker.google.com/issues/146780347 (Cloud Build 
>   uses stale GitHub clones)
>   - logging:
>- 
>   
> https://groups.google.com/d/topic/google-appengine/xTDZ-da27ow/discussion 
>   (difficulties reading GAE app logs from the logging API)
>   - 
>   
> https://stackoverflow.com/questions/58753378/how-to-deserialize-app-engine-application-logs-from-stackdriver-logging-api
>   - https://github.com/googleapis/google-cloud-python/issues/2572
>   - https://github.com/snarfed/bridgy/issues/940 (my app's feature 
>   that uses logging API is now way slower)
>   - 
>   
> https://groups.google.com/forum/#!topic/google-stackdriver-discussion/k96EQHCacKM
>  
>   (can't request increase to logs API read quota)
>   - 
>   
> https://stackoverflow.com/questions/59398479/why-is-my-app-engine-app-hitting-the-stackdriver-logging-256kb-limit
>   - https://github.com/snarfed/bridgy/issues/904 (originally ingested 
>   way more logs than i expected)
>   - ndb, misc growing pains:
>- https://github.com/googleapis/python-ndb/issues/263
>   - https://github.com/googleapis/python-ndb/issues/238
>   - https://github.com/googleapis/python-ndb/issues/277
>   - https://github.com/googleapis/python-ndb/issues/376
>   - https://github.com/googleapis/python-ndb/issues/267
>- cloud tasks missing local emulator, transactional tasks
>   - 
>   
> https://cloud.google.com/tasks/docs/migrating#features_in_task_queues_not_yet_available_via
>- migration increased our frontend instance usage noticeably, had to 
>rearchitect and extract out task processing into a separate background 
>service to get costs back down: 
>https://github.com/snarfed/bridgy/issues/578
>(not entirely sure this was GAE's fault)
>- shared memcache got lost entirely, so i had to switch to a runtime 
>in-memory cache, which isn't as helpful
>- https://github.com/GoogleCloudPlatform/webapp2/issues/151 (webapp2 
>is unmaintained, and its port to Python 3 is a bit rough)
>- 
>https://groups.google.com/d/topic/google-appengine/WHo99Gz1S3g/discussion 
>(difficulty finding replacement for app_identity module)
>
>
>
> On Tuesday, May 5, 2020 at 2:06:48 PM UTC-7, Charlie Engelke wrote:
>>
>> This is very helpful feedback. Anybody else have comments for us?
>>
>> On Tuesday, May 5, 2020 at 1:17:52 PM UTC-7 Charlie Engelke wrote:
>>
>>> I'd still like to here anyone's stories involving migrating their App 
>>> Engine apps from Python 2.7 to Python 3.7. Have you migrated yet? Planning 
>>> to do so soon? Not going to move to the new platform?
>>>
>>> And any particular pain points? Things that would have helped? 
>>>
>>> Thanks,
>>>
>>> Charlie
>>>
>>> On Friday, May 1, 2020 at 2:18:33 PM UTC-7 Charlie Engelke wrote:
>>>
>>>> Have you recently migrated from App Engine for Python 2.7 to App Engine 
>>>> for Python 3.7? Are you working on migrating now, or planning to soon? Or 
>>>> maybe you are using App Engine for Python 2.7 and aren't planning such a 
>>>> migration.
>>>>
>>>> In each of those cases, I'd like to hear how things went or are going 
>>>> for you, pain points you encounter, things that went easily, and anything 
>>>> else you have to share. I'm working on creating some new code samples to 
>>>> help with this, and your stories will be a big help.
>>>>
>>>> Thanks,
>>>>
>>>> Charlie
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5f63c9c5-72f3-40f5-a0b5-cd92979cda2d%40googlegroups.com.

[google-appengine] Re: Any more migration stories?

[Ryan B]

hi charlie, thanks for asking!

my experience was similar to joshua's, if not quite so extreme. i've 
migrated seven or so apps now, the largest weighing in at 26kloc. the big 
differences in API availability and compatibility were the most painful 
parts, followed by changes and difficulties with local development, as 
joshua mentioned.

here are a handful of threads and issues with details:

   - local dev, deployment:
   - 
  https://groups.google.com/d/topic/google-appengine/BJDE8y2KISM/discussion 
  (fast startup or static assets, choose one?)
  - https://issuetracker.google.com/issues/144150446 (dev_appserver 
  patch to fix this)
  - https://issuetracker.google.com/issues/146780347 (Cloud Build uses 
  stale GitHub clones)
  - logging:
   - 
  https://groups.google.com/d/topic/google-appengine/xTDZ-da27ow/discussion 
  (difficulties reading GAE app logs from the logging API)
  - 
  
https://stackoverflow.com/questions/58753378/how-to-deserialize-app-engine-application-logs-from-stackdriver-logging-api
  - https://github.com/googleapis/google-cloud-python/issues/2572
  - https://github.com/snarfed/bridgy/issues/940 (my app's feature that 
  uses logging API is now way slower)
  - 
  
https://groups.google.com/forum/#!topic/google-stackdriver-discussion/k96EQHCacKM
 
  (can't request increase to logs API read quota)
  - 
  
https://stackoverflow.com/questions/59398479/why-is-my-app-engine-app-hitting-the-stackdriver-logging-256kb-limit
  - https://github.com/snarfed/bridgy/issues/904 (originally ingested 
  way more logs than i expected)
  - ndb, misc growing pains:
   - https://github.com/googleapis/python-ndb/issues/263
  - https://github.com/googleapis/python-ndb/issues/238
  - https://github.com/googleapis/python-ndb/issues/277
  - https://github.com/googleapis/python-ndb/issues/376
  - https://github.com/googleapis/python-ndb/issues/267
   - cloud tasks missing local emulator, transactional tasks
  - 
  
https://cloud.google.com/tasks/docs/migrating#features_in_task_queues_not_yet_available_via
   - migration increased our frontend instance usage noticeably, had to 
   rearchitect and extract out task processing into a separate background 
   service to get costs back down: 
   https://github.com/snarfed/bridgy/issues/578
   (not entirely sure this was GAE's fault)
   - shared memcache got lost entirely, so i had to switch to a runtime 
   in-memory cache, which isn't as helpful
   - https://github.com/GoogleCloudPlatform/webapp2/issues/151 (webapp2 is 
   unmaintained, and its port to Python 3 is a bit rough)
   - 
   https://groups.google.com/d/topic/google-appengine/WHo99Gz1S3g/discussion 
   (difficulty finding replacement for app_identity module)
   


On Tuesday, May 5, 2020 at 2:06:48 PM UTC-7, Charlie Engelke wrote:
>
> This is very helpful feedback. Anybody else have comments for us?
>
> On Tuesday, May 5, 2020 at 1:17:52 PM UTC-7 Charlie Engelke wrote:
>
>> I'd still like to here anyone's stories involving migrating their App 
>> Engine apps from Python 2.7 to Python 3.7. Have you migrated yet? Planning 
>> to do so soon? Not going to move to the new platform?
>>
>> And any particular pain points? Things that would have helped? 
>>
>> Thanks,
>>
>> Charlie
>>
>> On Friday, May 1, 2020 at 2:18:33 PM UTC-7 Charlie Engelke wrote:
>>
>>> Have you recently migrated from App Engine for Python 2.7 to App Engine 
>>> for Python 3.7? Are you working on migrating now, or planning to soon? Or 
>>> maybe you are using App Engine for Python 2.7 and aren't planning such a 
>>> migration.
>>>
>>> In each of those cases, I'd like to hear how things went or are going 
>>> for you, pain points you encounter, things that went easily, and anything 
>>> else you have to share. I'm working on creating some new code samples to 
>>> help with this, and your stories will be a big help.
>>>
>>> Thanks,
>>>
>>> Charlie
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5c75e080-b0d9-48da-832e-60b69daefcd1%40googlegroups.com.

[google-appengine] 502 Bad Gateway nginx and how to re-deploy

[jane B]

Hello,

When I followed the guide for "Running Django on the App Engine standard 
environment" : https://cloud.google.com/python/django/appengine and 
deployed the app when I went onto the browser I received a 502 Bad Gateway 
Nginx  error. I think I did not connect to MySQL correctly. I think I fixed 
this issue and I want to re-deploy my app using gcloud app deploy .

After following the guideline again (basically redoing it) I get this error 
: 
File upload done.

ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: This deployment has too many 
files. New versions are limited to 1 files for this app.

- '@type': type.googleapis.com/google.rpc.BadRequest

  fieldViolations:

  - description: This deployment has too many files. New versions are 
limited to 1

  files for this app.

field: version.deployment.files[...]


I want to know how to re-deploy the app with the correct code. how am I 
suppose to go about this?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/23e70843-4309-4764-8339-5b2551c907cb%40googlegroups.com.

[google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

[Patrice B]

Hi guys, 

A few months back, I had a similar reflexion on current trends regarding 
AppEngine, which I called "the end of paas", which could be called "end of 
serverless" in a way

https://groups.google.com/forum/?utm_medium=email_source=footer#!search/paas|sort:date/google-appengine/DHMMv5r8qjU/A-VO3PXPDwAJ

It's not very long, so I paste it here, since it is quite similar to what 
is being said here.

It seems most of the services that made AppEngine a proper Platorm as a 
Service are now scheduled to be shut down, and users are advised to 
migrate.   Migrate search to ElasticSearch, migrate memcache to Redis, and 
maybe at some point we'll be asked to migrate Ndb to MongoDB and GCS to 
whatever.   I'm not complaining about the way the process is handled 
actually, there is enough time to consider the options and work on a 
migration scenario, there is no imminent deadline, at least for the 
moment.   But I'm wondering what went wrong with the PaaS approach, and is 
it officially dead.

Is this the end of GAE as a PaaS ?   I truly believed PaaS was the future 
of cloud architectures:  stop thinking in terms of servers, start thinking 
in terms of services.   When I started working with AppEngine, I dreamed of 
CPU as a service, with no server granularity, and I was disappointed to 
find I still had to worry about servers, starting up a new server instance, 
choosing what type of instance would be best, a scaling strategy, etc.   I 
was expecting servers as a service, i.e. serving my requests without me 
ever thinking in terms of servers.   But at least there was Ndb, search, 
memcache, GCS and a few more.

Now it seems all of these are on their way out, which makes me wonder: was 
there something wrong with the concept of PaaS itself, or is it just that 
these products didn't gain traction, and are now too costly to maintain 
with regards to their user base ?   Actually, the one thing that was wrong 
with Paas from the very beginning was that it would lock a project into a 
given cloud.   That was a risk to be reckoned for users, but it could have 
been seen as a feature for the cloud provider.   Now is it for this reason 
that the mentionned services didn't make it ?  Because users would have 
been wary of being locked in, and for that reason would prefer to use 
leading products deployed on leased servers ?One thing is for sure: 
once an application has migrated to more standard services, it will not be 
tied to GCP anymore.

There was a major benefit to the PaaS concept:  it was very cheap for 
startups.   Deploying ElasticSearch on a the smallest possible cluster will 
start at around $200 a month, while the search usage of a small application 
could cost less than $10.   Same for the shared memcache service offered by 
AppEngine.   Now you are having to pay for running servers all night with 
very little transactions to handle. 

I'd be happy to hear your thoughts on this matter ? 


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6edf3459-a4d0-4ea4-9282-86cdb6a2672f%40googlegroups.com.

[google-appengine] Re: Cloud Datastore Emulator support?

[Ryan B]

hi again, jon! silly question, but are you also overriding tearDown() and 
calling self.ndb_context.__exit__(None, None, None) there? if not, i wonder 
if all of the previous tests' contexts are holding onto open connections to 
the datastore emulator and exhausting a connection pool somewhere. seems 
unlikely, but maybe possible.

On Wednesday, March 4, 2020 at 2:42:14 PM UTC-8, Jon Grover wrote:
>
> First, my apologies: I realize this is a bit off-topic. I'm running into a 
> mysterious issue w/ the Cloud Datastore Emulator during a migration from 
> NDB to Cloud NDB. I don't think the issue is related to Cloud NDB in 
> particular, but I'm not sure where to turn for help. I posted a more 
> detailed description in the Google Cloud Datastore Googlegroup here 
> , 
> but it appears to be much less active than this group.
>
> The nutshell version is that I am calling 
> *requests.post('http://localhost:8089/reset 
> ') *in the setUp() method for each of my 
> tests which involve NDB in order to clear the datastore . This works when I 
> run any one test file individually, but when I try to run our full test 
> suite of 580 tests we start seeing an error about halfway through. The 
> error indicates that it wasn't able to create any new connections to the 
> URL, and once it first appears all subsequent tests fail with the same 
> error. 
>
> Traceback (most recent call last):
>   File "test/my_test.py", line 11, in setUp
>   File "/Projects/tilegames/test/_base_test.py", line 50, in setUp
>   File "/Projects/tilegames/lib/requests/api.py", line 119, in post
>   File "/Projects/tilegames/lib/requests/api.py", line 61, in request
>   File "/Projects/tilegames/lib/requests/sessions.py", line 530, in 
> request
>   File "/Projects/tilegames/lib/requests/sessions.py", line 643, in send
>   File "/Projects/tilegames/lib/requests/adapters.py", line 516, in send
> ConnectionError: HTTPConnectionPool(host='localhost', port=8089): Max 
> retries exceeded with url: /reset (Caused by 
> NewConnectionError(' object at 0x11286e590>: Failed to establish a new connection: [Errno 8] 
> nodename nor servname provided, or not known',))
>
> My initial efforts to troubleshoot what's going on here have all failed 
> and I'm not sure where the best place is to turn for support. I suppose 
> Stack Overflow is always an option. Anyone here have thoughts?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8e9377ed-8b0a-4837-9b65-ccea73f8da3a%40googlegroups.com.

Re: [google-appengine] Re: Cloud NDB is now GA

[Ryan B]

On Sunday, March 1, 2020 at 2:44:04 PM UTC-8, Jon Grover wrote:
>
> I've found that entering/exiting context in the setUp/tearDown methods (as 
> you do in your example) is adding about 0.7s to each of my tests, so I'm 
> wondering how you're able to do 500 tests in 52s (works out to 0.1s per 
> test). Perhaps it's machine dependent; I'm running these tests on a 2015 
> MacBook Pro, so maybe they'd be faster on something newer.
>

hmm! i'm actually on a 2014 MBP, so i doubt it's your hardware. feel free 
to poke at that repo, stack, and test suite if you want to see if you can 
find a difference. all of the tests use that base HandlerTest class, 
unittest, and mox3.

 

> On Saturday, February 29, 2020 at 8:22:35 PM UTC-8, Ryan B wrote:
>>
>> the datastore emulator is indeed slower than testbed for unit tests, but 
>> just as another data point, it's not way too slow for me. i routinely use 
>> it as part of my edit/compile/test loop on an app with a cumulative total 
>> of >1600 tests. around 500 of them use the datastore heavily, and running 
>> just those tests takes ~52s. not fast, but manageable, especially when i 
>> iterate on just a few relevant tests, and then expand to all of them before 
>> committing.
>>
>> also, you don't have to entirely tear down and restart the emulator just 
>> to clear its data between tests. just POST to http://localhost:8089/reset 
>> (or whichever port you run the emulator on). example: 
>> https://github.com/snarfed/bridgy/blob/master/tests/testutil.py#L282-L289
>>
>>
>> On Monday, February 24, 2020 at 1:05:33 PM UTC-8, Remko Tronçon wrote:
>>>
>>> On Monday, February 24, 2020 at 9:52:25 PM UTC+1, Andrew Gorcester 
>>> wrote: 
>>> > Cloud NDB is compatible with the Cloud Datastore Emulator; we 
>>> recommend tests be done using that, the same way on Cloud NDB as they would 
>>> be with the Cloud Datastore library. 
>>>
>>> Using an external emulator is way too slow to use for unit tests, even 
>>> if you are able to get all your code changed so you don’ have to tear down 
>>> and clean start the emulator to avoid interference between tests. This is 
>>> pretty disappointing, and means I (and I expect many others) will be forced 
>>> to rewrite everything if your app isn’t in pure maintenance mode. 
>>>
>>> Remko 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9b06feba-3fc3-49eb-aba9-4d5923087a80%40googlegroups.com.

Re: [google-appengine] Re: Cloud NDB is now GA

[Ryan B]

the datastore emulator is indeed slower than testbed for unit tests, but 
just as another data point, it's not way too slow for me. i routinely use 
it as part of my edit/compile/test loop on an app with a cumulative total 
of >1600 tests. around 500 of them use the datastore heavily, and running 
just those tests takes ~52s. not fast, but manageable, especially when i 
iterate on just a few relevant tests, and then expand to all of them before 
committing.

also, you don't have to entirely tear down and restart the emulator just to 
clear its data between tests. just POST to http://localhost:8089/reset (or 
whichever port you run the emulator on). example: 
https://github.com/snarfed/bridgy/blob/master/tests/testutil.py#L282-L289


On Monday, February 24, 2020 at 1:05:33 PM UTC-8, Remko Tronçon wrote:
>
> On Monday, February 24, 2020 at 9:52:25 PM UTC+1, Andrew Gorcester wrote: 
> > Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend 
> tests be done using that, the same way on Cloud NDB as they would be with 
> the Cloud Datastore library. 
>
> Using an external emulator is way too slow to use for unit tests, even if 
> you are able to get all your code changed so you don’ have to tear down and 
> clean start the emulator to avoid interference between tests. This is 
> pretty disappointing, and means I (and I expect many others) will be forced 
> to rewrite everything if your app isn’t in pure maintenance mode. 
>
> Remko 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f7c51bc3-8ac4-4979-9de8-2932393c6fdf%40googlegroups.com.

[google-appengine] Re: Cloud NDB is now GA

[Ryan B]

congratulations andrew! and to chris, carlos, danny, and everyone else who 
built python 3 ndb. it's been a huge boon for migrating from appengine 
python 2 to python 3. we appreciate all the hard work you all put into it!

On Monday, February 24, 2020 at 11:02:36 AM UTC-8, Andrew Gorcester wrote:
>
> Hello Pythonistas,
>
>
> The Cloud NDB client library for Cloud Datastore and Cloud Firestore in 
> Datastore mode, previously introduced as a beta project in September 2019, 
> has been launched to GA with its 1.0 release.
>
>
> Cloud NDB is an updated version of the App Engine NDB client library for 
> Datastore, adding support for Python 3 and targeting the Datastore API. 
> While it is intended for users migrating from App Engine Python 2.7 to App 
> Engine Python 3, it is fully portable and compatible with other Python 
> platforms. The library can be installed with `pip install google-cloud-ndb` 
> and the source code can be found on Github at 
> https://github.com/googleapis/python-ndb.
>
>
> We also have a migration guide for NDB 
> 
>  
> at, as part of our broader GAE Python migration documentation 
> . 
> We'll continue updating and adding to this documentation and library as 
> part of our migration support effort, so please also continue sending us 
> your feedback.
>
>
> Thank you again for your continued support for App Engine and our Cloud 
> platform. I am looking forward to hearing feedback from the community on 
> this and upcoming efforts.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d7adc2e4-0d1a-4fdf-9493-0f8d1ea58ba4%40googlegroups.com.

[google-appengine] Re: Google appengine free quota per application?

[Ryan B]

On Thursday, February 20, 2020 at 12:41:49 PM UTC-8, David (Cloud Platform 
Support) wrote:
>
>
> I would like to clarify this for you. Free quotas are per billing account 
> and not per application.
>
 
hi david! i know you're an official representative, but i don't think this 
is right. i have (and have always had) multiple apps serving under a single 
billing account, and each one gets the standard app engine free quota, eg 
28 frontend instance hours, etc.

...unless my account is grandfathered into some od plan that no longer 
applies to new accounts? that seems unlikely. 


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2a762e1c-820f-42ec-be00-eff7817ac004%40googlegroups.com.

[google-appengine] Re: ndb to cloud ndb migration experience

[Ryan B]

hi jon!

On Tuesday, February 18, 2020 at 5:42:26 AM UTC-8, Jon Grover wrote:
>
> On Thursday, January 16, 2020 at 1:47:03 PM UTC-8, Ryan B wrote:
> 1) First and foremost, I had repeated issues with dev_appserver connecting 
> to my production datastore despite having set all the correct environment 
> variables and setting the --support_datastore_emulator flag. I was finally 
> able to solve it by explicitly passing *--env_var 
> DATASTORE_EMULATOR_HOST=localhost:8081*, but I'm not immediately sure how 
> to do that from within our unittest framework and I'm very worried about 
> our unit tests writing to the production datastore. (For the time being, I 
> used the gcloud CLI to change my project to a dummy one.)
>

yes! this one was/is disappointing. it's a hole in dev_appserver that most 
likely will never be closed, since dev_appserver itself is basically 
deprecated. i literally monkey patch the host/port into the ndb context 
manually: 
https://github.com/snarfed/webutil/blob/master/appengine_config.py#L39 . 
background: https://github.com/googleapis/python-ndb/issues/238
 
 

> 2) This is maybe my own unfamiliarity with NDB context, but I'm not sure 
> what the correct way is to use the same NDB context across all unit tests. 
> I borrowed your WSGI middleware trick for the app itself, but I haven't yet 
> quite figured out how to apply a single context across our entire unittest 
> suite. I tried creating a new NDB context in our base setUp method, which 
> looked like it was working but dragged the test speed to a crawl.
>

right! i do exactly that, and also reset the datastore and call 
__enter__(), and then __exit__() in tearDown: 
https://github.com/snarfed/bridgy/blob/master/tests/testutil.py#L282-L289

unit tests are definitely slower now with the emulator vs testbed in the 
python 2 runtime. one test suite of mine that does datastore operations in 
almost every test, often many per test, takes ~50s to run 526 tests. not 
great, but i usually iterate by running individual tests, so it doesn't 
hurt too much.

 
 

> Just curious if you had any additional insights or example code available. 
> I've already learned quite a bit by reading through your other postings, so 
> thanks regardless.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/86f581f9-886b-4cf9-8cc2-e07c76df07b5%40googlegroups.com.

Re: [google-appengine] Can't I set a specific request timeout ? 24 hours for running an HTTP requets seems crazy.

[Patrice B]

Thank you for your time.   I do understand that task queues and cron jobs 
may need a longer timeout value. 

My question really is this : is there no way to configure an instance in 
such a way that HTTP requests are killed on timeout after say 10 minutes ? 

And if there is no way to achieve this, as seems to be the case, then how 
would you suggest to protect an instance against a request that would keep 
running forever ?Should be start a timer and attempt to handle timeout 
manually ? 


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cbc75d76-591f-4f58-bff3-42d6fe0b8b4c%40googlegroups.com.

[google-appengine] Can't I set a specific request timeout ? 24 hours for running an HTTP requets seems crazy.

[Patrice B]

Regarding request timeout, I find here 
https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed#timeout
 
that a timeout value of 10 minutes is used for "automatic scaling" and a 
value of 24 hours is used in basic and manual scaling.And indeed, I 
have observed requests running for hours and hours, with important impact 
on the instance.

Is there no way for me to define a specific timeout value other than 10 
minutes or 24 hours ?24 hours, which applies to HTTP requests as well 
as task queue tasks,  is a crazy value for web requests, who would wait 24 
hours for an HTTP response ?  

This absence of a reasonable limit has major implications:  while the user 
probably moved on and left the page after a few minutes, the request may be 
running for hours, thus slowing the whole instance. 

It would be very useful to be able to specify one's own timeout value.   
And if that is impossible, then 10 minutes for HTTP requests is certainly a 
better choice than 24 hours. 

Does anyone else have this kind of issue ? 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f411f311-5ef0-47d5-ade7-2cb53830224c%40googlegroups.com.

[google-appengine] Re: No Cloud Tasks local emulator

[Ryan B]

On Friday, January 17, 2020 at 7:04:24 AM UTC-8, Aert van de Hulsbeek wrote:
>
>
> See if the emulator I built works for you: 
> https://github.com/aertje/cloud-tasks-emulator. It's pretty bare bones 
> but hopefully it helps. 
>
> Thanks for replying to my question re. the NDB migration btw!


oh wow, that's exciting! thanks for the nudge, and the kind words. i'll 
give it a shot. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2998b352-d516-487b-b69d-aeae2a33ace3%40googlegroups.com.

Re: [google-appengine] Python 3 standard environment data storage

[Ryan B]

On Friday, January 17, 2020 at 9:28:56 AM UTC-8, Joshua Smith wrote:
>
> That thing is invaluable when you have lots of apps. Is there something 
> similar for P3.7 that will send me exception summaries daily?
>
> I’m familiar with the “Cloud Console” phone app, which will do 
> notifications. But in my experience you can’t rely on that, because 
> sometimes it spontaneously stops notifying.
>

i've been using stackdriver error reporting 
 for this for a while, and it's 
great, and pretty automatic and built in. i don't think it does daily 
digest emails, but you can definitely have it email individual new errors 
when they first appear, or recur after closing them, and those emails have 
been very reliable in my experience.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/43b02b5f-3583-44b3-8f1b-9d1e28d45f87%40googlegroups.com.

Re: [google-appengine] Python 3 standard environment data storage

[Ryan B]

On Friday, January 17, 2020 at 8:42:11 AM UTC-8, Joshua Smith wrote:
>
> Running locally, I’m using this datastore emulator:
>
> https://cloud.google.com/datastore/docs/tools/datastore-emulator
>
> It works, but it is SOOO SLW. It takes literally 10-20 seconds to 
> respond to a simple query.
>

huh, that's surprising. just as a data point, i definitely don't see that 
behavior. i use the datastore emulator locally for both unit tests and 
interactive development, and it responds many orders of magnitude faster, 
as expected. for example, one project runs 524 unit tests in ~53s, many of 
which do multiple operations (both read and write) against the emulator.

i'm on mac os 10.15.2, gcloud 276.0.0, cloud-datastore-emulator 2.1.0, 
python 3.6.5.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7d3216cc-15d6-48c5-989f-0f963c3b7e07%40googlegroups.com.

[google-appengine] Re: ndb to cloud ndb migration experience

[Ryan B]

i recently migrated a number of nontrivial apps from python 2 to python 3 
(standard). it wasn't easy, especially since i used a number of the old 
APIs - task queues, logging, memcache, ndb, etc - that have changed 
significantly or disappeared entirely. it took a significant amount of 
effort, coding, and workarounds, but it was doable in the end. kudos in 
particular to chris rossi, danny hermes, carlos de la guardia, et al for 
the new python 3 ndb library !

i've posted many of the bigger gotchas i hit here on this list 
,
 
and over 

 on 
SO , and on the python 3 ndb 
issue tracker 
.
 
beyond all those, two key things i ended up doing for ndb were:

* replace testbed 

 
with the datastore emulator 
 for 
running unit tests without mocking out ndb. example commands. 

* this WSGI middleware to run all HTTP request handlers inside an NDB 
client context. 
 
without it, i would have had to add a ton of ugly new with 
ndb_client.context(): ... blocks and indents everywhere.

also, shameless plug, feel free to test things out in shell-py3.appspot.com, 
an interactive REPL inside python 3 GAE standard that includes the new ndb.

On Wednesday, January 15, 2020 at 5:27:12 AM UTC-8, Aert van de Hulsbeek 
wrote:
>
> We are currently looking to migrate a reasonable number of gae std 
> services from py2 to py3 and are tossing up between a datastore or cloud 
> ndb implementation.
> Has anyone done a somewhat complex migration from ndb to cloud ndb and 
> what was this experience like? I am mainly interested in unforeseen and 
> undocumented gotcha's / blockers that might direct us down the datastore 
> path.
> If anyone can share some hands-on experience, that would be fantastic. 
> Thanks, Aert.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/142c3da2-0871-43c1-be3c-0c7b6c0eb674%40googlegroups.com.

Re: [google-appengine] gcloud app deploy is failing

[Patrice B]

So I'm not the only one feeling AppEngine is gradually moving away from 
Paas, although this trend does not seem to be acknowledged officially.
I had recently posted here:  the end of Paas ? 

Indeed it seems more and more of the services that made App Engine a proper 
PaaS offering are being migrated to IaaS.



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cadbd968-4282-4313-95f6-68df099aeada%40googlegroups.com.

[google-appengine] server-side REPL shell for Python 3 Standard Environment

[Ryan B]

hi all! i've ported the venerable, old school server side shell app 
shell-hrd.appspot.com from Python 2 to 3: shell-py3.appspot.com. it's a 
full fledged, interactive Python REPL that runs its code server side inside 
the Python 3 Standard Environment. feel free to try it out!

in the process of porting a few nontrivial apps to Python 3, i regularly 
found myself asking how bits of the production runtime behaved. which 
directory on the filesystem is the virtualenv installed in? what do the 
app-default credentials look like, specifically? what are the WSGI (etc) 
environment variables set to?

one way to answer these is to add logging that prints them, deploy that 
code, run it, make a request, and look at the logs. that iteration cycle is 
pretty slow, though. using this shell is way faster.

it also includes a number of the new Google Cloud API libraries, including 
google.cloud.ndb, .logging, and .error_reporting, which has been useful for 
experimenting with them.

feedback is welcome!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d2152351-0153-446e-980c-327181069bd5%40googlegroups.com.

[google-appengine] Re: GAE Standard | Local Dev | Python37: google.appengine.api not found

[Ryan B]

hi Yanay! the classic App Engine APIs in google.appengine.api aren't available 
in the Python 3 runtime. More details: 
https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis


On Sunday, November 24, 2019 at 6:08:57 PM UTC-8, Yanay Lehavi wrote:
>
> I see a number of threads on this in git etc. but they all seem unresolved:
>
> >>> import google.appengine.api
>
> Traceback (most recent call last):
>
>   File "", line 1, in 
>
> ModuleNotFoundError: No module named 'google'
>
> >>> 
>
> In the above mentioned threads, some people suggested various env vars, 
> none of which I have, nor ever needed... (been developing GAE locally for a 
> long time).
> My platform: Mac Catalina.
> Anyone knows how to resolve this?
> Many 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2fbbae44-76e6-4e28-9cc6-3c4bfe50f074%40googlegroups.com.

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

[Ryan B]

the patch below makes dev_appserver use an existing virtualenv instead of 
creating a new one from scratch each time. it applies cleanly against 
google cloud SDK 272.0.0, app-engine-python component 1.9.87. i'd happily 
add a command line flag and send a PR, but afaik the google cloud SDK isn't 
open source.

put it in a file named dev_appserver.virtualenv.diff, then apply it with:

patch /opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/
platform/google_appengine/google/appengine/tools/devappserver2/python/
instance_factory.py ~/dev_appserver.virtualenv.diff

that path is for Mac OS, for a google cloud SDK originally installed via 
homebrew. you may need to update it for your own environment. you'll also 
need to change 'local3' below in the patch to your own virtualenv's path, 
relative to the app root directory.

diff instance_factory.py.orig instance_factory.py
105,106c105
< if os.path.exists(venv_dir):
<   shutil.rmtree(venv_dir)
--
> pass
120,121c119,124
< self._CleanUpVenv(self._venv_dir)
< self._venv_dir = tempfile.mkdtemp()
--
> self._venv_dir = os.path.join(os.path.dirname(self.
_module_configuration.config_path), 'local3')
> self.venv_env_vars = {
> 'VIRTUAL_ENV': self._venv_dir,
> 'PATH': ':'.join([os.path.join(self._venv_dir, 'bin'), os.environ[
'PATH']])
> }
> return

i'd hoped to write a wrapper script with a monkey patch instead, so i 
wouldn't have to reapply the patch every time i upgrade gcloud, but 
dev_appserver goes through a couple layers of import bootstraps at startup, 
and it wasn't easy to inject the monkey patch at just the right time. ah 
well. fingers crossed for the feature request to add this officially. 
<https://issuetracker.google.com/issues/144150446>


On Friday, November 8, 2019 at 4:56:35 PM UTC-8, Ryan B wrote:
>
> The latest in the saga of using dev_appserver.py locally is that Python 3 
> ndb (aka google-cloud-ndb) doesn't support it. I've filed this bug report. 
> <https://github.com/googleapis/python-ndb/issues/238> Whee!
>
> On Friday, November 8, 2019 at 3:35:40 PM UTC-8, Andrew Gorcester wrote:
>>
>> That does make sense. If you could bridge the gap by using a single 
>> static file directory in app.yaml served with a single static_dir handler, 
>> that might work too. But I know some apps have very complex app.yaml 
>> defined static files, so I understand why you're looking at the 
>> dev_appserver.py option instead.
>>
>> On Fri, Nov 8, 2019 at 3:33 PM Ryan Barrett  wrote:
>>
>>> thanks for the reply!
>>>
>>> On Fri, Nov 8, 2019 at 2:40 PM 'Andrew Gorcester' via Google App Engine <
>>> google-a...@googlegroups.com> wrote:
>>>
>>>> I would recommend trying to solve the first problem and serving static 
>>>> files locally.
>>>>
>>>
>>> understood, but using a different static file server is not great. it 
>>> makes local development diverge significantly from production. local no 
>>> longer uses or tests app.yaml's static file handlers, but prod does, so 
>>> bugs will eventually pop up that only happen in production, and are thus 
>>> harder to test for and debug.
>>>
>>> for that reason, i'm actually going the other way and using 
>>> dev_appserver right now, soi still have some confidence that my app will 
>>> behave more or less the same in production that it does locally. the minute 
>>> long delay on startup is definitely painful though.
>>>
>>>
>>> At first glance I think the most straightforward ways to do that would 
>>>> be to either:
>>>>
>>>> - Use the Flask development server instead of gunicorn and leverage 
>>>> Flask's integrated /static directory 
>>>> https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
>>>> - If you prefer to use gunicorn or you need more serving options, add 
>>>> WhiteNoise middleware to your app; ideally, have your app detect whether 
>>>> it's running in production or in development mode and conditionally add 
>>>> WhiteNoise in development only: http://whitenoise.evans.io/en/stable/
>>>>
>>>>
>>>> On Fri, Nov 8, 2019 at 2:21 PM Ryan B  wrote:
>>>>
>>>>> Hi all! My Python 3 topic for the day is local development. How are 
>>>>> you all doing it? Any tips?
>>>>>
>>>>> The two main ways seem to be a third party server, eg Flask or 
>>>>> Gunicorn, or dev_appserver.py. I have both working, but each one has 
>>>>> a fatal flaw that makes it basically unusable for me so far

Re: [google-appengine] Python 3 local development: fast startup or static assets, choose one?

[Ryan B]

The latest in the saga of using dev_appserver.py locally is that Python 3 
ndb (aka google-cloud-ndb) doesn't support it. I've filed this bug report. 
<https://github.com/googleapis/python-ndb/issues/238> Whee!

On Friday, November 8, 2019 at 3:35:40 PM UTC-8, Andrew Gorcester wrote:
>
> That does make sense. If you could bridge the gap by using a single static 
> file directory in app.yaml served with a single static_dir handler, that 
> might work too. But I know some apps have very complex app.yaml defined 
> static files, so I understand why you're looking at the dev_appserver.py 
> option instead.
>
> On Fri, Nov 8, 2019 at 3:33 PM Ryan Barrett  > wrote:
>
>> thanks for the reply!
>>
>> On Fri, Nov 8, 2019 at 2:40 PM 'Andrew Gorcester' via Google App Engine <
>> google-a...@googlegroups.com > wrote:
>>
>>> I would recommend trying to solve the first problem and serving static 
>>> files locally.
>>>
>>
>> understood, but using a different static file server is not great. it 
>> makes local development diverge significantly from production. local no 
>> longer uses or tests app.yaml's static file handlers, but prod does, so 
>> bugs will eventually pop up that only happen in production, and are thus 
>> harder to test for and debug.
>>
>> for that reason, i'm actually going the other way and using dev_appserver 
>> right now, soi still have some confidence that my app will behave more or 
>> less the same in production that it does locally. the minute long delay on 
>> startup is definitely painful though.
>>
>>
>> At first glance I think the most straightforward ways to do that would be 
>>> to either:
>>>
>>> - Use the Flask development server instead of gunicorn and leverage 
>>> Flask's integrated /static directory 
>>> https://flask.palletsprojects.com/en/1.1.x/tutorial/static/
>>> - If you prefer to use gunicorn or you need more serving options, add 
>>> WhiteNoise middleware to your app; ideally, have your app detect whether 
>>> it's running in production or in development mode and conditionally add 
>>> WhiteNoise in development only: http://whitenoise.evans.io/en/stable/
>>>
>>>
>>> On Fri, Nov 8, 2019 at 2:21 PM Ryan B > 
>>> wrote:
>>>
>>>> Hi all! My Python 3 topic for the day is local development. How are you 
>>>> all doing it? Any tips?
>>>>
>>>> The two main ways seem to be a third party server, eg Flask or 
>>>> Gunicorn, or dev_appserver.py. I have both working, but each one has a 
>>>> fatal flaw that makes it basically unusable for me so far.
>>>>
>>>> When I run my app with eg gunicorn -b :8080 app:application - the way 
>>>> Google recommends 
>>>> <https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app#running_locally>
>>>>  
>>>> - it works, but doesn't serve any assets from static file handlers in my 
>>>> app.yaml. This is widely reported on StackOverflow 
>>>> <https://stackoverflow.com/search?q=%5Bgoogle-app-engine%5D+%5Bpython-3.x%5D+static>
>>>>  
>>>> and elsewhere. Responses are often some variation of, "why do you need 
>>>> static assets for dynamic requests?" The obvious reason is that pretty 
>>>> much 
>>>> all webapps use images, CSS, and/or JS, among other static files. They're 
>>>> generally not usable without those assets.
>>>>
>>>> When I run my app with  dev_appserver.py, it creates a new virtualenv 
>>>> and installs all of my dependencies from requirements.txt. This is 
>>>> nice, but also extremely slow for any nontrivial app. My current medium 
>>>> sized app has 155 packages, and even when they're all cached locally, 
>>>> installing them takes around 60s. I often switch between different apps 
>>>> and 
>>>> other stacks, so I can't often keep dev_appserver running for hours or 
>>>> days 
>>>> on end to avoid this. (I've filed this feature request for 
>>>> dev_appserver to reuse an existing virtualenv. 
>>>> <https://issuetracker.google.com/u/1/issues/144150446>)
>>>>
>>>> Let me know if you have any ideas!
>>>>
>>>> -- 
>>>> 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 
>>

[google-appengine] Python 3 local development: fast startup or static assets, choose one?

[Ryan B]

Hi all! My Python 3 topic for the day is local development. How are you all 
doing it? Any tips?

The two main ways seem to be a third party server, eg Flask or Gunicorn, or 
dev_appserver.py. I have both working, but each one has a fatal flaw that 
makes it basically unusable for me so far.

When I run my app with eg gunicorn -b :8080 app:application - the way 
Google recommends 
<https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app#running_locally>
 
- it works, but doesn't serve any assets from static file handlers in my 
app.yaml. This is widely reported on StackOverflow 
<https://stackoverflow.com/search?q=%5Bgoogle-app-engine%5D+%5Bpython-3.x%5D+static>
 
and elsewhere. Responses are often some variation of, "why do you need 
static assets for dynamic requests?" The obvious reason is that pretty much 
all webapps use images, CSS, and/or JS, among other static files. They're 
generally not usable without those assets.

When I run my app with  dev_appserver.py, it creates a new virtualenv and 
installs all of my dependencies from requirements.txt. This is nice, but 
also extremely slow for any nontrivial app. My current medium sized app has 
155 packages, and even when they're all cached locally, installing them 
takes around 60s. I often switch between different apps and other stacks, 
so I can't often keep dev_appserver running for hours or days on end to 
avoid this. (I've filed this feature request for dev_appserver to reuse an 
existing virtualenv. <https://issuetracker.google.com/u/1/issues/144150446>)

Let me know if you have any ideas!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eff3cf33-3a7b-4cc4-8b8c-2a46b2c56c45%40googlegroups.com.

Re: [google-appengine] Python 3: how to deserialize App Engine application logs from StackDriver Logging API?

[Ryan B]

thanks guys! as mentioned, LogEntry.to_api_repr() is currently broken for 
this use case with the latest version of google-cloud-logging, 1.14.0. i've 
posted details on 
https://github.com/googleapis/google-cloud-python/issues/2572#issuecomment-551199704
 
(which is unfortunately closed right now).

On Thursday, November 7, 2019 at 10:56:53 AM UTC-8, Dustin Ingram wrote:
>
> You can use the LogEntry.to_api_repr() 
> <https://googleapis.dev/python/logging/latest/entries.html#google.cloud.logging.entries.LogEntry.to_api_repr>
>  
> function to get a JSON version of the LogEntry.
>
> On Thu, Nov 7, 2019 at 9:36 AM Ryan B > 
> wrote:
>
>> Hi again! As part of migrating to Python 3, I need to migrate from 
>> logservice 
>> <https://cloud.google.com/appengine/docs/standard/python/refdocs/google.appengine.api.logservice.logservice>
>>  
>> to the StackDriver Logging API 
>> <https://cloud.google.com/logging/docs/reference/api-overview>. I have 
>> google-cloud-logging <https://pypi.org/project/google-cloud-logging/> 
>> installed, and I can successfully fetch GAE application logs with eg:
>>
>> >>> from google.cloud.logging_v2 import LoggingServiceV2Client
>> >>> entries = LoggingServiceV2Client().list_log_entries((
>> 'projects/brid-gy',),
>>  filter_='resource.type="gae_app" AND protoPayload.@type="
>> type.googleapis.com/google.appengine.logging.v1.RequestLog"')
>> >>> print(next(iter(entries)))
>> proto_payload {
>>   type_url: "type.googleapis.com/google.appengine.logging.v1.RequestLog"
>>   value: "\n\ts~brid-gy\022\0018\032R5d..."
>> }
>> ...
>>
>> This gets me a LogEntry with text application logs in the 
>> proto_payload.value field. How do I deserialize that field? I've found 
>> lots of related mentions in the docs - links below - but nothing pointing 
>> me to a google.appengine.logging.v1.RequestLog protobuf generated class 
>> anywhere that I can use, if that's even the right idea. Has anyone done 
>> this?
>>
>>
>> https://googleapis.dev/python/logging/latest/gapic/v2/types.html#google.cloud.logging_v2.types.LogEntry.proto_payload
>>
>> https://cloud.google.com/logging/docs/reference/v2/rpc/google.appengine.logging.v1#requestlog
>>
>> https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.proto_payload
>>
>> https://cloud.google.com/logging/docs/api/v2/resource-list#resource-indexes
>> https://groups.google.com/d/topic/google-cloud-dev/Xr6tZxOIaJY/discussion
>>
>> -- 
>> 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-a...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/a6665355-a7e6-42d4-96c2-82090d457adf%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/a6665355-a7e6-42d4-96c2-82090d457adf%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4fc5946c-5e8e-4d86-b30f-98575508e4b4%40googlegroups.com.

[google-appengine] Re: Python 3: how to deserialize App Engine application logs from StackDriver Logging API?

[Ryan B]

Interesting. Dustin Ingram (Google DevRel) copied this question to 
StackOverflow 
<https://stackoverflow.com/questions/58753378/how-to-deserialize-app-engine-application-logs-from-stackdriver-logging-api>,
 
and answered it there, but not here. Is that standard for this group?

In any case, thanks Dustin! Except your answer 
<https://stackoverflow.com/a/58753379/186123> to switch to the v1 
StackDriver Logging API and use LogEntry.to_api_repr() doesn't work for me. 
I get:

Traceback (most recent call last):
  File "", line 1, in 
  File 
"/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/google/cloud/logging/entries.py"
, line 357, in to_api_repr
info["protoPayload"] = MessageToDict(self.payload)
  File 
"/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/google/protobuf/json_format.py"
, line 168, in MessageToDict
return printer._MessageToJsonObject(message)
  File 
"/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/google/protobuf/json_format.py"
, line 202, in _MessageToJsonObject
return methodcaller(_WKTJSONMETHODS[full_name][0], message)(self)
  File 
"/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/google/protobuf/json_format.py"
, line 314, in _AnyMessageToJsonObject
sub_message = _CreateMessageFromTypeUrl(type_url, self.descriptor_pool)
  File 
"/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/google/protobuf/json_format.py"
, line 389, in _CreateMessageFromTypeUrl
'Can not find message descriptor by type_url: {0}.'.format(type_url))
TypeError: Can not find message descriptor by type_url: type.googleapis.com/
google.appengine.logging.v1.RequestLog.

Searching turns up a few GitHub issues showing that people maintaining 
Google Cloud Python libraries have struggled with this for years. I got 
lost in them and haven't yet managed to find a conclusion:

https://github.com/googleapis/google-cloud-python/issues/2572
https://github.com/googleapis/google-cloud-python/issues/2674
etc.

In case it helps, here are the relevant packages I have installed in my 
virtualenv:

google-api-core1.14.3
google-api-python-client   1.7.11
google-auth1.6.3
google-auth-httplib2   0.0.3
google-cloud-core  1.0.3
google-cloud-logging   1.14.0
googleapis-common-protos   1.6.0
oauth2client   4.1.3


On Thursday, November 7, 2019 at 7:34:42 AM UTC-8, Ryan B wrote:
>
> Hi again! As part of migrating to Python 3, I need to migrate from 
> logservice 
> <https://cloud.google.com/appengine/docs/standard/python/refdocs/google.appengine.api.logservice.logservice>
>  
> to the StackDriver Logging API 
> <https://cloud.google.com/logging/docs/reference/api-overview>. I have 
> google-cloud-logging <https://pypi.org/project/google-cloud-logging/> 
> installed, and I can successfully fetch GAE application logs with eg:
>
> >>> from google.cloud.logging_v2 import LoggingServiceV2Client
> >>> entries = LoggingServiceV2Client().list_log_entries((
> 'projects/brid-gy',),
>  filter_='resource.type="gae_app" AND protoPayload.@type="
> type.googleapis.com/google.appengine.logging.v1.RequestLog"')
> >>> print(next(iter(entries)))
> proto_payload {
>   type_url: "type.googleapis.com/google.appengine.logging.v1.RequestLog"
>   value: "\n\ts~brid-gy\022\0018\032R5d..."
> }
> ...
>
> This gets me a LogEntry with text application logs in the 
> proto_payload.value field. How do I deserialize that field? I've found 
> lots of related mentions in the docs - links below - but nothing pointing 
> me to a google.appengine.logging.v1.RequestLog protobuf generated class 
> anywhere that I can use, if that's even the right idea. Has anyone done 
> this?
>
>
> https://googleapis.dev/python/logging/latest/gapic/v2/types.html#google.cloud.logging_v2.types.LogEntry.proto_payload
>
> https://cloud.google.com/logging/docs/reference/v2/rpc/google.appengine.logging.v1#requestlog
>
> https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.proto_payload
> https://cloud.google.com/logging/docs/api/v2/resource-list#resource-indexes
> https://groups.google.com/d/topic/google-cloud-dev/Xr6tZxOIaJY/discussion
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c28a02dc-b15a-4ff6-9771-023bae2b4e80%40googlegroups.com.

[google-appengine] Python 3: how to deserialize App Engine application logs from StackDriver Logging API?

[Ryan B]

Hi again! As part of migrating to Python 3, I need to migrate from 
logservice 

 
to the StackDriver Logging API 
. I have 
google-cloud-logging  
installed, and I can successfully fetch GAE application logs with eg:

>>> from google.cloud.logging_v2 import LoggingServiceV2Client
>>> entries = LoggingServiceV2Client().list_log_entries(('projects/brid-gy'
,),
 filter_='resource.type="gae_app" AND 
protoPayload.@type="type.googleapis.com/google.appengine.logging.v1.RequestLog"'
)
>>> print(next(iter(entries)))
proto_payload {
  type_url: "type.googleapis.com/google.appengine.logging.v1.RequestLog"
  value: "\n\ts~brid-gy\022\0018\032R5d..."
}
...

This gets me a LogEntry with text application logs in the 
proto_payload.value field. How do I deserialize that field? I've found lots 
of related mentions in the docs - links below - but nothing pointing me to 
a google.appengine.logging.v1.RequestLog protobuf generated class anywhere 
that I can use, if that's even the right idea. Has anyone done this?

https://googleapis.dev/python/logging/latest/gapic/v2/types.html#google.cloud.logging_v2.types.LogEntry.proto_payload
https://cloud.google.com/logging/docs/reference/v2/rpc/google.appengine.logging.v1#requestlog
https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.proto_payload
https://cloud.google.com/logging/docs/api/v2/resource-list#resource-indexes
https://groups.google.com/d/topic/google-cloud-dev/Xr6tZxOIaJY/discussion

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a6665355-a7e6-42d4-96c2-82090d457adf%40googlegroups.com.

[google-appengine] Re: Python 3: how to determine the current app's project id?

[Ryan B]

ah, found it. looks like it's GAE_APPLICATION: 
https://cloud.google.com/appengine/docs/standard/python3/runtime#environment_variables

might be worth adding to the differences page 
<https://cloud.google.com/appengine/docs/standard/python3/python-differences>
!

On Wednesday, November 6, 2019 at 7:11:14 AM UTC-8, Ryan B wrote:
>
> Hi all! In the Python 2 runtime, I can use the app_identity API 
> <https://cloud.google.com/appengine/docs/standard/python/appidentity/> to 
> determine the current app's project id (ie application id) with 
> app_identity.get_application_id(). Anyone know how to do this in the 
> Python 3 runtime? 
> https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
>  
> doesn't mention the app_identity API, and 
> https://cloud.google.com/appengine/docs/standard/python3/python-differences#modules
>  
> doesn't mention project id.
>
> Thanks in advance!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/07d5e8e9-b601-467a-86e2-e18499196041%40googlegroups.com.

[google-appengine] Python 3: how to determine the current app's project id?

[Ryan B]

Hi all! In the Python 2 runtime, I can use the app_identity API 
 to 
determine the current app's project id (ie application id) with 
app_identity.get_application_id(). Anyone know how to do this in the Python 
3 runtime? 
https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis
 
doesn't mention the app_identity API, and 
https://cloud.google.com/appengine/docs/standard/python3/python-differences#modules
 
doesn't mention project id.

Thanks in advance!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/969a7b5d-ba89-4b31-9d06-724ce3a5597a%40googlegroups.com.

[google-appengine] No Cloud Tasks local emulator

[Ryan B]

I have a bunch of small apps on App Engine Standard, on the old generation 
Python 2 runtime. I'm itching to migrate to Python 3 Standard, but I use 
many of the classic App Engine APIs - datastore via ndb, task queues, 
memcache, etc - which are difficult to migrate away from 

.

Tasks is one of the biggest current blockers. I'd happily switch to Cloud 
Tasks, but it has no local emulator, which makes local development and unit 
testing difficult at best. I've starred the issue. 
 Any news on if/when we 
can expect an emulator? (I'd ask on the Cloud tasks mailing list 
, but it requires 
approval to join.)

More broadly, the writing is on the wall. App Engine's future is 
serverless, containerized, and decoupled from services like datastore, task 
management, in-memory caches, etc. Flexible got there first, Standard's new 
generation of runtimes (Python 3 etc) followed.

Other forum members have already written eloquently about this here (see GAE 
APIs 
, 
The end of PaaS? 
), 
so I won't recap their concerns. Personally, I'm ok with this decoupling 
roadmap. I even trust that you all will gradually fill in our migration 
path. And I know Python 2 isn't going EOL anytime soon. I'm just impatient 
to get onto Python 3, so I'm chafing at blockers like Cloud Tasks' lack of 
an emulator.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b674ef4b-351b-49e8-9e2c-0ca0f61cb47d%40googlegroups.com.

[google-appengine] Re: The end of PaaS ?

[Patrice B]

Hello Kaan, 

I wished to start a discussion on a more philosophical, or say strategic 
question: whether there was a real trend towards replacing true services by 
software products hosted on leased servers.I did not want to get this 
mixed up with some specific grievance at all.   

The first consideration of your initial post was in line with that 
question, and your mention of the email service was quite to the point.   
In fact, pushing users from the original email api towards Sendgrid was one 
of these significant shifts, which I went through, but it was one where a 
service is replaced by another service, albeit from another provider, and 
with a significant free quota so that cost is not too much of an issue. 

In the two other shifts that I mention, memcache and search, I would have 
much preferred that sort of migration, from service to other service.   I 
would not mind using the ElasticSearch API, which is indeed much more 
powerful than the GCP search api.   What I do mind, is having to lease 2 
servers or more, full time, for that.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e7dcc967-7a30-4293-9d16-4729924bc8e0%40googlegroups.com.

[google-appengine] Re: The end of PaaS ?

[Patrice B]

Thank you for your update and insight.Maybe I was seeing a trend where 
there is none.   

Actually, there are two separate considerations:  (1) some products are 
replaced by other products, generally for the better, and developpers 
should plan for migration, this is life I guess, and it's ok as long as 
there is enough anticipation and not too profound disruption, it's fine.   
(2) in at least two cases (search and memcache) the replacement product is 
not a pure API, not "as a service", it has to be deployed on a number of 
server instances, whereas the former product was a simple service.   

Maybe it's not a trend, maybe just two isolated cases.   But it does have 
adverse consequences in terms of increased cost and of increased complexity.

The Datastore to Firestore migration, on the contrary, seems to be in 
perfect continuity, both in terms of api (when the Python 3 api comes out 
of beta) and of billing (I have not looked much into that later point 
actually).

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ca4160e5-2037-4c4e-9dfb-c043dfb2c681%40googlegroups.com.

[google-appengine] The end of PaaS ?

[Patrice B]

It seems most of the services that made AppEngine a proper Platorm as a 
Service are now scheduled to be shut down, and users are advised to 
migrate.   Migrate search to ElasticSearch, migrate memcache to Redis, and 
maybe at some point we'll be asked to migrate Ndb to MongoDB and GCS to 
whatever.   I'm not complaining about the way the process is handled 
actually, there is enough time to consider the options and work on a 
migration scenario, there is no imminent deadline, at least for the 
moment.   But I'm wondering what went wrong with the PaaS approach, and is 
it officially dead.

Is this the end of GAE as a PaaS ?   I truly believed PaaS was the future 
of cloud architectures:  stop thinking in terms of servers, start thinking 
in terms of services.   When I started working with AppEngine, I dreamed of 
CPU as a service, with no server granularity, and I was disappointed to 
find I still had to worry about servers, starting up a new server instance, 
choosing what type of instance would be best, a scaling strategy, etc.   I 
was expecting servers as a service, i.e. serving my requests without me 
ever thinking in terms of servers.   But at least there was Ndb, search, 
memcache, GCS and a few more.

Now it seems all of these are on their way out, which makes me wonder: was 
there something wrong with the concept of PaaS itself, or is it just that 
these products didn't gain traction, and are now too costly to maintain 
with regards to their user base ?   Actually, the one thing that was wrong 
with Paas from the very beginning was that it would lock a project into a 
given cloud.   That was a risk to be reckoned for users, but it could have 
been seen as a feature for the cloud provider.   Now is it for this reason 
that the mentionned services didn't make it ?  Because users would have 
been wary of being locked in, and for that reason would prefer to use 
leading products deployed on leased servers ?One thing is for sure: 
once an application has migrated to more standard services, it will not be 
tied to GCP anymore.

There was a major benefit to the PaaS concept:  it was very cheap for 
startups.   Deploying ElasticSearch on a the smallest possible cluster will 
start at around $200 a month, while the search usage of a small application 
could cost less than $10.   Same for the shared memcache service offered by 
AppEngine.   Now you are having to pay for running servers all night with 
very little transactions to handle. 

I'd be happy to hear your thoughts on this matter ? 


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f6be955a-9064-47f8-b57c-69ea9ca6e406%40googlegroups.com.

[google-appengine] Very long request is not killed ?

[Patrice B]

Hello, 
Recently, I had a request that took 40 mn to complete.  It was an ordinary 
http request, just with parameters that made it very long to process.  This 
hogged the instance and caused high latency for the whole time.
Obviously, we need to work on checking the request's parameters so that we 
can identify very early that this request will be too long and reject it.
However, this raises 2 questions:
1) I thought maximum response time for an http request was 1 mn, so I would 
have expected the request to be aborted somehow.   Maybe it was aborted for 
the client, but the processing did continue for 40 mn, and the request 
appears in the log not as an error, but as successfully processed in 40 
minutes.
2) In response, the load balancing did spawn more instances, as would be 
expected, but strangely the latency seemed to be affected on all 
instances.   Can this be real, or is it just a coincidence ?

Thank you for your thoughts and expertise.   Patrice.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cc9e7ce5-9723-4ddb-9904-fcf8a736e103%40googlegroups.com.

[google-appengine] Is there any way of triggering DataPrep based flow from AppEngine?

[Chauhan B]

Hi,

 

I am new to Google DataPrep, and for one of my implementation I am trying 
to use Google DataPrep.

 

I have to create a UI using App Maker and I have to run a pipeline for 
performing intermediate jobs [data cleansing & transformation] and pushing 
final data to destination. I have used Google DataPrep for performing 
intermediate data cleansing and transformation but I am not able to make 
out how to run/execute my dataprep based flows on button click event from 
my AppMaker based UI?

 

What is the way of calling any dataprep pipeline on every button click from 
UI? Is it possible or not?

 

Any quick reference would be of great help.

 

Regards,

Bhupesh

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ca053c06-39a9-4fdf-ad12-67b8e3be5c5e%40googlegroups.com.

[google-appengine] Re: webapp2 based web application development, add social login

[Ryan B]

harmit is right, but at a fairly low level. i've encapsulated the oauth 
implementations for lots of existing social sites and integrated them with 
app engine in the oauth-dropins package. feel free to try it out: 
https://oauth-dropins.appspot.com/ . if you like it, you can pip install it 
into your app's virtualenv and use it from there. more details in the docs: 
https://oauth-dropins.readthedocs.io/

On Monday, July 8, 2019 at 11:59:51 AM UTC-7, Harmit Rishi (Cloud Platform 
Support) wrote:
>
> Hello, 
>
> Thank you for using Google Groups!
>
> Based on my understanding of what you have described, you can implement 
> OAuth within Google App engine. You may find further details of this here 
> .
>  
>
>
> However, I was able to find *StackOverflow* threads that revolve around 
> this issue with Webapp2. In regards to specific social logins, I was able 
> to find the following thread here 
> 
>  that 
> discusses how to integrate Facebook login within App Engine. Though, I 
> believe it would be worthwhile for you to check out the discussion here 
> 
>  as 
> the entire thread discusses "Webapp2 Authentication and Login". 
> Additionally, there is a third party boilerplate provided by the community 
> on that thread for what you are attempting to do. You may feel free to 
> explore the links shared to determine if the ideas discussed in them would 
> be applicable in your use case.
>
> I hope this helps!
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/00426117-a13e-4396-813a-b4e4190550b8%40googlegroups.com.

[google-appengine] Automatic scaling on App Engine: do I need to set scaling parameters for every version ?

[Patrice B]

It seems auto scaling parameters such as min_instances or min_idle_instances 
are not defined through the app.yaml file.   They can be defined through 
APIs.   But does this mean that for every deployment of a new version with 
gcloud 
app deploy I would need to go the the APIs again and define scaling 
parameters again ?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/defb9740-fac6-41db-abf0-cfcbd8087733%40googlegroups.com.

[google-appengine] gcloud 238.0.0 broke dev_appserver.py on Mac OS X

[Ryan B]

hi all! looks like gcloud 238.0.0 + app-engine-python 1.9.84 and later 
broke dev_appserver.py on Mac OS X, at least when using 
google.appengine.ext.vendor to load libraries from a virtualenv. (i expect 
that's many/most of us. :P)

stack trace and SO questions below. any chance this will be fixed in gcloud 
241.0.0? thanks in advance!

https://stackoverflow.com/questions/55166959/osx-dev-appserver-py-file-not-accessible-system-library-coreservices-systemve
https://stackoverflow.com/questions/55151062/gcloud-update-broke-my-app-gcp-python-2-7

Traceback (most recent call last):
  ...
  File 
"/Users/ryan/src/granary/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 
line 951, in 
class Environment(object):
  File 
"/Users/ryan/src/granary/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 
line 955, in Environment
self, search_path=None, platform=get_supported_platform(),
  File 
"/Users/ryan/src/granary/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 
line 180, in get_supported_platform
plat = get_build_platform()
  File 
"/Users/ryan/src/granary/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 
line 389, in get_build_platform
version = _macosx_vers()
  File 
"/Users/ryan/src/granary/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 
line 356, in _macosx_vers
version = platform.mac_ver()[0]
  File 
"/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/platform.py",
 
line 764, in mac_ver
info = _mac_ver_xml()
  File 
"/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/platform.py",
 
line 741, in _mac_ver_xml
pl = plistlib.readPlist(fn)
  File 
"/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py",
 
line 75, in readPlist
pathOrFile = open(pathOrFile)
  File 
"/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/python/runtime/stubs.py",
 
line 283, in __init__
raise IOError(errno.EACCES, 'file not accessible', filename)
IOError: [Errno 13] file not accessible: 
'/System/Library/CoreServices/SystemVersion.plist'



-- 
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/8099b259-f961-4b04-adc3-027e5e6e965f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE APIs

[Ryan B]

this is the existential question facing app engine's 
glacier-under-the-surface installed base of python 2 apps. the writing 
seems to be on the wall for the legacy, custom app engine python APIs; all 
signs point to the decoupled, REST-based APIs to standalone services 
(datastore, cloud tasks, etc) as the future.

you're right, though, we still haven't heard a migration path for long time 
users like us with existing python codebases that use the old APIs. word on 
the street seems to be that google knows this, and has been thinking about 
an answer for a while. one obvious reason is that there are plenty of big 
whale app engine customers in the same boat as us (ahem 
) who presumably have more leverage.

i have no inside knowledge, but my bet is that we'll get some form of 
compatibility layer, either porting (most) old libraries to use the new 
REST APIs under the hood, and/or (less likely) a code transformation tool 
like python's 2to3. i doubt either one would handle 100% of existing code, 
but if they hit 80% or 90%, i expect they'd declare victory. here's hoping!

On Monday, January 28, 2019 at 1:54:49 AM UTC-8, Joshua Fox wrote:
>
> Are there end-of-life plans   for GAE APIs in GAE Standard Environment, as 
> indeed happened in Flexible Environment already?
>
> If so, what is the timeline?
>
> -- 
>  
>
> *JOSHUA FOX*
> Director, Software Architecture | Freightos
>
>
>
> *T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953  
> Smooth shipping.
>
>
>
>

-- 
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/561c5a7a-414b-4601-a680-4df119bd437d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dev_appserver in 1.9.76 switched import resolution from relative to absolute?

[Ryan B]

thanks for the link, amit! that issue definitely looks related. this 
problem still happens for me on cloud SDK 220 + app-engine-python 1.9.77, 
so i may be seeing a different variation of that issue, since most people 
there say 220 fixed it for them. i've added a comment.


On Thursday, October 11, 2018 at 9:31:52 AM UTC-7, Amit (Google Cloud 
Support) wrote:
>
> Hello Ryan
>
> What is the current Google Cloud SDK version you are using? As of now current 
> version <https://cloud.google.com/sdk/docs/release-notes> for Google 
> Cloud SDK is [220.0.0]. We had a known issue [1] on version [219.0.1] in 
> dev_appserver with app-engine-python [1.9.76] which should be resolved in 
> the current version where the version of app-engine-python is [1.9.77]. I 
> would recommend to update your SDK version using this [2] command and try 
> again. If you still having this issue after upgrade and believe this could 
> be a bug, please create an issue in issuetracker 
> <https://cloud.google.com/support/docs/issue-trackers> with details 
> description of your issue and provide the output of this [3] command so 
> that we know more about your SDK.
>
> [1] https://issuetracker.google.com/117145272
>
> [2] gcloud components update
>
> [3] gcloud info --anonymize
>
>
> On Wednesday, October 10, 2018 at 6:51:57 PM UTC-4, Ryan B wrote:
>>
>> fwiw, i've deployed at least one of the affected apps since 
>> app-engine-python 1.9.76 was released, and it's still working fine, which 
>> implies that the prod runtime isn't similarly affected. (i did that deploy 
>> with gcloud sdk 218, purely out of superstition, but i didn't really expect 
>> it to matter much one way or the other.)
>>
>> On Wednesday, October 10, 2018 at 3:50:02 PM UTC-7, Ryan B wrote:
>>>
>>> hi all! i'm debugging a dev_appserver problem that seems to have been 
>>> introduced in google cloud sdk 219 / app-engine-python 1.9.76: imports are 
>>> now all resolved as absolute instead of relative. does that sound familiar?
>>>
>>> for example, i use the future library <http://python-future.org/> in 
>>> many of my apps, which has this line of code 
>>> <https://github.com/PythonCharmers/python-future/blob/fdd5eebe3aea61959533dbb722820fac7c5954ea/src/future/standard_library/__init__.py#L484>
>>> :
>>>
>>> import test
>>>
>>> on gcloud sdk 218 / app-engine-python 1.9.75 and before, this worked 
>>> fine. it resolved the import relative to the containing source file, in 
>>> local/lib/python2.7/site-packages/future/... , a virtualenv, which i 
>>> set up with vendor 
>>> <https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27#vendoring>.
>>>  
>>> on 1.9.76, it changed to resolving absolute instead, so it imports an 
>>> unrelated test/ package directory in the top level of my app, which 
>>> obviously won't work, and the app breaks.
>>>
>>> i couldn't find any mention of this in release notes or docs. was this 
>>> expected? any recommendations for handling it? thanks in advance!
>>>
>>>
>>>

-- 
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/043b9c9d-f2f4-4aec-91bb-e94dc9d090d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dev_appserver in 1.9.76 switched import resolution from relative to absolute?

[Ryan B]

fwiw, i've deployed at least one of the affected apps since 
app-engine-python 1.9.76 was released, and it's still working fine, which 
implies that the prod runtime isn't similarly affected. (i did that deploy 
with gcloud sdk 218, purely out of superstition, but i didn't really expect 
it to matter much one way or the other.)

On Wednesday, October 10, 2018 at 3:50:02 PM UTC-7, Ryan B wrote:
>
> hi all! i'm debugging a dev_appserver problem that seems to have been 
> introduced in google cloud sdk 219 / app-engine-python 1.9.76: imports are 
> now all resolved as absolute instead of relative. does that sound familiar?
>
> for example, i use the future library <http://python-future.org/> in many 
> of my apps, which has this line of code 
> <https://github.com/PythonCharmers/python-future/blob/fdd5eebe3aea61959533dbb722820fac7c5954ea/src/future/standard_library/__init__.py#L484>
> :
>
> import test
>
> on gcloud sdk 218 / app-engine-python 1.9.75 and before, this worked fine. 
> it resolved the import relative to the containing source file, in 
> local/lib/python2.7/site-packages/future/... , a virtualenv, which i set 
> up with vendor 
> <https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27#vendoring>.
>  
> on 1.9.76, it changed to resolving absolute instead, so it imports an 
> unrelated test/ package directory in the top level of my app, which 
> obviously won't work, and the app breaks.
>
> i couldn't find any mention of this in release notes or docs. was this 
> expected? any recommendations for handling it? thanks in advance!
>
>
>

-- 
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/d04cbc6c-98cf-468c-beec-35aa5e37ea39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] dev_appserver in 1.9.76 switched import resolution from relative to absolute?

[Ryan B]

hi all! i'm debugging a dev_appserver problem that seems to have been 
introduced in google cloud sdk 219 / app-engine-python 1.9.76: imports are 
now all resolved as absolute instead of relative. does that sound familiar?

for example, i use the future library  in many 
of my apps, which has this line of code 

:

import test

on gcloud sdk 218 / app-engine-python 1.9.75 and before, this worked fine. 
it resolved the import relative to the containing source file, in 
local/lib/python2.7/site-packages/future/... , a virtualenv, which i set up 
with vendor 
.
 
on 1.9.76, it changed to resolving absolute instead, so it imports an 
unrelated test/ package directory in the top level of my app, which 
obviously won't work, and the app breaks.

i couldn't find any mention of this in release notes or docs. was this 
expected? any recommendations for handling it? thanks in advance!


-- 
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/51b6c05e-02ef-4c99-9ff7-33bf432b8a8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Directx or Hyper-V In google Cloud?

[Jason Bourne :b]

So i already 6 days trying to solve these issue, i need to be able to 
install Hyper-V(For RemoteFX) or be able to fully enable Directx 
Aceleration. I already do a big research and google cloud dosnt support 
Hyper-V and RDP dosnt support Directx. So i have any other alternative for 
be able to succesfully run Directx Games inside google cloud plataform?
The game i want to test is metin2. And yes my server has GPU(P100 Virtual 
Workstation)

-- 
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/97a70a6b-59fa-4583-b07f-b09517f74f25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: URLFetch adds gzip,deflate,br to outbound requests' Accept-Encoding?

[Ryan B]

i've filed https://issuetracker.google.com/issues/112277350 for this.

On Thursday, August 2, 2018 at 10:50:51 AM UTC-7, Ryan B wrote:
>
> hi all! i had to debug a URLFetch problem recently, and the root cause 
> turned out to be that i was unexpectedly receiving a brotli-compressed 
> response. it took me a while to figure out why: evidently URLFetch is 
> adding gzip,deflate,br to outbound requests' Accept-Encoding HTTP header.
>
> is this expected? it's not documented on 
> https://cloud.google.com/appengine/docs/standard/python/outbound-requests#request_headers
>  
> , and brotli support isn't built into many common HTTP libraries, e.g. 
> python requests, so this will usually be an unpleasant surprise when 
> talking to a server that supports brotli. is it unintentional? should i 
> file a bug?
>
> here's a snippet that reproduces this on https://shell-hrd.appspot.com/ :
>
> >>> from google.appengine.api import urlfetch
> >>> resp = urlfetch.fetch('https://httpbin.org/headers', 
> >>> headers={'Accept-Encoding': 'foo'})
> >>> resp.status_code
> 200
> >>> print(resp.content)
> {
>   "headers": {
> "Accept-Encoding": "foo,gzip,deflate,br",
> "Connection": "close",
> "Host": "httpbin.org",
> "User-Agent": "AppEngine-Google; (+http://code.google.com/appengine; 
> appid: s~shell-hrd)",
> "X-Cloud-Trace-Context": 
> "795505ff8141cf535fa9cf33afe59daa/1604381323415253803;o=1"
>   }
> }
>
>
>

-- 
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/752ee899-07fb-491a-b8b3-83f6b3c5a270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] URLFetch adds gzip,deflate,br to outbound requests' Accept-Encoding?

[Ryan B]

hi all! i had to debug a URLFetch problem recently, and the root cause 
turned out to be that i was unexpectedly receiving a brotli-compressed 
response. it took me a while to figure out why: evidently URLFetch is 
adding gzip,deflate,br to outbound requests' Accept-Encoding HTTP header.

is this expected? it's not documented on 
https://cloud.google.com/appengine/docs/standard/python/outbound-requests#request_headers
 
, and brotli support isn't built into many common HTTP libraries, e.g. 
python requests, so this will usually be an unpleasant surprise when 
talking to a server that supports brotli. is it unintentional? should i 
file a bug?

here's a snippet that reproduces this on https://shell-hrd.appspot.com/ :

>>> from google.appengine.api import urlfetch
>>> resp = urlfetch.fetch('https://httpbin.org/headers', 
>>> headers={'Accept-Encoding': 'foo'})
>>> resp.status_code
200
>>> print(resp.content)
{
  "headers": {
"Accept-Encoding": "foo,gzip,deflate,br",
"Connection": "close",
"Host": "httpbin.org",
"User-Agent": "AppEngine-Google; (+http://code.google.com/appengine; appid: 
s~shell-hrd)",
"X-Cloud-Trace-Context": 
"795505ff8141cf535fa9cf33afe59daa/1604381323415253803;o=1"
  }
}


-- 
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/193794a4-4cda-4a2b-a5f8-0e0e69b64cd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

[Ryan B]

thanks, steren! makes sense.

i'm actually trying the Node runtime for the first time, on a small 
personal project, so i don't actually have the "lots of static file 
handlers in Node" use case yet. i'm just sensitive to DRY and seeing 
duplicated things skew over time.

thanks again!

On Thursday, July 12, 2018 at 1:39:26 PM UTC-7, Steren Giannini wrote:
>
> Hi Ryan,
>
> The feedback we receive was that Node.js developers expect to start their 
> application with "npm start" more than with "dev_appserver.py".
>
> Replicating the handlers in your web framework is indeed the 
> recommendation that we give in our static handler documentation 
> <https://cloud.google.com/appengine/docs/standard/nodejs/serving-static-files#serving_files_for_local_development>
> .
>
> That being said, we are currently exploring an optional solution to run 
> your Node.js App Engine app in a local emulator that would emulate the 
> static handlers.
>
> In am curious, can you share more about why your application uses many 
> different static handlers?
>
> Steren
>
> On Thu, Jul 12, 2018 at 10:28 AM Ryan B > 
> wrote:
>
>> thanks, kenworth!
>>
>> looks like the key part of that example is these lines in app.js:
>>
>> // Use the built-in express middleware for serving static files from 
>> './public'
>> app.use('/static', express.static('public'));
>>
>> that does indeed get the static files serving. it still ignores the 
>> static file handlers in app.yaml, though, and just duplicates them via 
>> express in app.js instead. that's ok, but it's unfortunate for larger 
>> applications with many different static file handlers in app.yaml, since 
>> you have to duplicate them all, and they'll inevitably skew when you change 
>> them.
>>
>> if this is expected, i'm happy to file a feature request on the issue 
>> tracker! just let me know.
>>
>> On Thursday, July 12, 2018 at 9:20:30 AM UTC-7, Kenworth (Google Cloud 
>> Platform) wrote:
>>>
>>> This is currently possible. Here is an example to help you get started:
>>>
>>> https://github.com/
>>> GoogleCloudPlatform/nodejs-docs-samples/tree/master/appengine/static-files
>>>
>>> npm start app.standard.yaml
>>>
>>>
>>>
>>> -- 
>> 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/60e8d17a-61b1-4bf7-aced-f669092fcbf6%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/60e8d17a-61b1-4bf7-aced-f669092fcbf6%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ba590bf6-8a1e-4468-a262-129244fefe44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Run Node app locally and serve static file handlers from app.yaml?

[Ryan B]

thanks, kenworth!

looks like the key part of that example is these lines in app.js:

// Use the built-in express middleware for serving static files from 
'./public'
app.use('/static', express.static('public'));

that does indeed get the static files serving. it still ignores the static 
file handlers in app.yaml, though, and just duplicates them via express in 
app.js instead. that's ok, but it's unfortunate for larger applications 
with many different static file handlers in app.yaml, since you have to 
duplicate them all, and they'll inevitably skew when you change them.

if this is expected, i'm happy to file a feature request on the issue 
tracker! just let me know.

On Thursday, July 12, 2018 at 9:20:30 AM UTC-7, Kenworth (Google Cloud 
Platform) wrote:
>
> This is currently possible. Here is an example to help you get started:
>
>
> https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/master/appengine/static-files
>
> npm start app.standard.yaml
>
>
>
>

-- 
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/60e8d17a-61b1-4bf7-aced-f669092fcbf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Run Node app locally and serve static file handlers from app.yaml?

[Ryan B]

hi all! the docs for Node currently say use to npm start, ie "your local 
environment with the development tools that you usually use," to run an app 
locally:

https://cloud.google.com/appengine/docs/standard/nodejs/testing-and-deploying-your-app#running_locally

this works fine for URLs handled by Node, but it doesn't serve static files 
handled by app.yaml, so testing an app manually locally is difficult (or 
impossible) since it won't have static HTML, CSS, JS, etc.

other language runtimes use eg dev_appserver to serve both dynamic and 
static file handlers. are there plans for anything similar for Node?

-- 
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/cf83608f-e409-4d42-a4fa-8d2d2f080c5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: App Engine to Compute Engine communication via internal IP

[Niklas B]

Agreed, this would be very helpful. This would serve as a poor mans cloud 
functions until they get python and internal access. Looking for this on 
the Flexible environment. 

Den fredag 9 mars 2018 kl. 12:48:56 UTC+1 skrev Daniel Florey:
>
> Any news? I've spend a lot of time to find information on how to access 
> Compute Engine vial URLFetch from App Engine standard using internal IP.
> Is this simply not possible (yet)?
>
> On Thursday, June 29, 2017 at 2:19:49 AM UTC+2, Lorne Kligerman wrote:
>>
>> Not just yet.  We'll let you know when we're ready for early tests.
>> Thanks!
>>
>> On Wed, Jun 28, 2017 at 3:07 PM, Robert Dyas  
>> wrote:
>>
>>> Now that GAE Std Java 8 is in beta, is there any update on when this 
>>> might become available for testing?
>>>
>>> On Wednesday, January 4, 2017 at 1:25:40 PM UTC-5, Lorne Kligerman wrote:
>>>
 As Adam mentioned, this is only possible right now with the flex.  
 However we do know this is a problem and are working towards a solution 
 for 
 standard, nothing more to report at this time.


 On Friday, December 30, 2016 at 1:53:53 PM UTC-8, Nick (Cloud Platform 
 Support) wrote:
>
> Hey Jitenda,
>
> The Flexible Environment can be used by any user, although of course 
> being a beta product, it isn't covered by the same SLA's as other 
> products. 
> You should check our documentation including the terms of service 
> , service level agreements 
> , and the explanation of launch 
> stages .
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, December 29, 2016 at 9:14:50 AM UTC-5, JITENDRA GANGWAR 
> wrote:
>>
>> Thanks Adam for your answer , But  as per this documentation 
>>  App Engine 
>> flexible environment is still in beta release , can it be used in 
>> production ?
>>
>> On Saturday, June 25, 2016 at 2:38:46 AM UTC+5:30, Adam (Cloud 
>> Platform Support) wrote:
>>>
>>> You should be able to do this if you use a Flexible Environment 
>>> instance, and specify the same network name 
>>> 
>>>  
>>> in the app.yaml that your Compute Engine instance running MySQL is on. 
>>> It 
>>> won't work for Standard Environment instances as they are on separate, 
>>> physical networks.
>>>
>>> I say "should" as I haven't played around with this, and there's an 
>>> additional layer of network routing from the Docker container the app 
>>> lives 
>>> in which also has its own local subnet.
>>>
>>> On Friday, June 24, 2016 at 10:43:29 AM UTC-4, Stephen Dunkley wrote:

 I have a Java Web application deployed on a Compute Engine instance 
 connecting to MySql running on another Compute Engine instance in the 
 same 
 project. I am able to connect to MySql using the internal IP address 
 (jdbc:mysql://10.240.0.4:3306/).

 If I deploy the same web application to an App Engine instance 
 within the same project, I can only connect to the MySql instance via 
 the 
 extermal IP address (jdbc:mysql://104.196.148.141:3306/>>>
 If I try to use the internal IP address, I get a Communication Link 
 Failure, Permission Denied due to policy.

 My question is how do I open up communication between an App Engine 
 instance and a Compute Engine instance via an internal IP address? The 
 performance is about 5 x faster when using the internal IP address.

 Any help would be much appreciated

>>> -- 
>>> 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/5RsoKIPWyTQ/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, 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/b21223f6-8d58-4522-b369-a17744453b53%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 

[google-appengine] When does app engine serialise the http response?

[b]

Hi,

I am trying to set the headers on the http response but realised in some 
cases the http response has been serialised and the setHeader() function 
will fail. When exactly does app engine serialise the http response?

Best,
Baojun

-- 
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/2050eb23-61f0-49b7-83a9-b7af1a5bb63a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] When does app engine set the cookie JSESSIONID

[b]

Hi,

https://groups.google.com/forum/#!topic/google-appengine/0luWnYACBlQ

According to this post. The App Engine set the cookie JSESSIONID after 
request.getSession() is called. But when exactly? Is it done by a internal 
filter?

What if I set the JESSIONID myself right after a new session is created? 
Will App Engine try to overwrite my cookie or it will just skip creating 
one?

Best,
Baojun

-- 
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/47766049-29d0-4a80-9a83-2610744bec79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to bulk create entities in cloud datastore

[Sammy B]

Thanks Jordan. I'll post to stack overflow if I have more questions

On Wednesday, November 22, 2017 at 3:01:02 PM UTC-5, Jordan (Cloud Platform 
Support) wrote:
>
> The documentation you are following is for exporting existing Datastore 
> entities and importing existing Datastore entities using the 
> '.overall_export_metadata' Datastore specific backup files. 
>
> If you do not have any entities, or if the exported entities match the 
> imported entities, there will be no new Entities added to your Datastore 
> Kind. If you instead wish to create new entities it is recommended to use 
> the Client Library API 
> 
> .
>
> - Note that Google Groups is for general product discussions and not for 
> technical support. If you require further technical support for populating 
> your Datastore it is recommended to post your full detailed question 
>  to Stack Overflow 
>  using the supported 
> Cloud tags. 
>

-- 
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/0a492c1a-4c1f-4114-b602-48b6f1636b7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Unable to bulk create entities in cloud datastore

[Sammy B]

Hi,
I'm following the the link below to create entities in cloud datastore

https://cloud.google.com/datastore/docs/export-import-entities

I did the following:
1. create bucket
2. upload cvs
3. using the link above, exported the data using the export command
4. ran the import command

However, I don't see the data populated on the cloud datastore dashboard. 
Can someone please advise?

Thanks,
Sammy

-- 
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/7bf17b09-99c5-46fe-8546-c9af8400e321%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Importing data into Datastore. What's the deal?

[Niklas B]

Randy, did you ever find a solution? Using put_multi would take me 15-23 
days to upload my 15 GB of data ;)

Regards,
Niklas

Den fredag 24 februari 2017 kl. 17:51:28 UTC+1 skrev George (Cloud Platform 
Support):
>
> Datastore is beneficial in some cases, and your use case is not the most 
> frequently encountered in this context. There are alternative storage 
> solutions you might have a look at, listed in the Other storage options 
> from the Cloud Datastore Overview document 
> . 
>
> You may use the Rest API to store JSON data in Datastore, with methods: 
> “Method: projects.beginTransaction” and then “Method: projects.commit”. 
>
> One needs to create objects from JSON lines and then transfer them to the 
> Datastore in an economical way, so as to reduce time and cost. 
>
> More detail about the options available for doing so is to be found in a 
> relatively recent article from Stackoverflow: “How to upload data in bulk 
> to the appengine datastore? 
> ”,
>  
> that you may consider reading. 
>

-- 
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/3a535a85-8648-4be0-b9d8-1d8288cdea91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Doubt about "Frontend Instance hours"

[Ryan B]

On Wednesday, September 6, 2017 at 6:08:33 AM UTC-7, Diego Barreiro wrote:
>
>
> I have my application, with only one service ("default") and only one 
> version reciving all traffic ("2-0-0"). If two users use my app for an 
> hour, that quota increases by two hours or only one hour?
>

only one hour. instance hours are unrelated to number of users.

-- 
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/dbc7a279-e295-4c18-8282-c0d464bda96d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Billed Instance Estimate noticeably wrong: shows 2 instances, actually billed for almost 3

[Ryan B]

hi all! i have an app engine project that consistently uses 2 frontend 
instances, based on cloud console's "Billed Instance Estimate," but has 
consistently been billed for almost 3 instances, for at least the last few 
months. screenshots below for august: 1980h / 29 days = ~2.83 instances.


any idea what's going on? is "Billed Instance Estimate" known to be wrong 
in some cases? i have a dozen or so other apps that generally run on just 1 
instance each according to "Billed Instance Estimate," occasionally over, 
and their actual billed instance hours all match correctly.

thanks in advance!








-- 
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/64c3ae42-3eda-44f6-b49d-80152482cdb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Brauche Hilfe beim Cloudspeicher :(

[Pascal B.]

Momentan bin ich dabei mit AI2 eine App zu entwickeln und wollte dafür 
einen online Speicher haben. Aber jedes mal wenn ich auf "Deploy" klicke 
kommt nur diese Fehlermeldung:

2017-08-26 21:27:54 Running command: "['C:\\Python27\\python.exe', '-u', 
'C:\\Program Files (x86)\\Google\\google_appengine\\appcfg.py', 
'--oauth2_credential_file=C:\\Users\\Passi/.appcfg_oauth2_tokens', 
'update', 'E:\\customtinywebdb\\customtinywebdb']"
09:27 PM Application: test-178018; version: 1
09:27 PM Host: appengine.google.com
09:27 PM Starting update of app: test-178018, version: 1
09:27 PM Getting current resource limits.
09:27 PM Scanning files on local disk.
Error 400: --- begin server output ---
Python 2.5 is not supported in 'e' partition.
--- end server output ---
2017-08-26 21:27:59 (Process exited with code 1)

You can close this window now.


Ich werde daraus nicht schlau, vor allem weil auf einmal irgendwas mit 
Python 2.5 da drin ist, obwohl ich nur Version 2.7 habe. Vielleicht hängt 
das damit zusammen, dass ich vorher einen anderen Fehler behoben hab, indem 
ich was weggenommen habe?

2017-08-26 21:15:23 Running command: "['C:\\Python27\\python.exe', 
'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py', 
'--skip_sdk_update_check=yes', '--port=8080', '--admin_port=8000', 
'E:\\customtinywebdb\\customtinywebdb']"
WARNING  2017-08-26 21:15:25,871 application_configuration.py:189] The 
"python" runtime specified in "E:\customtinywebdb\customtinywebdb\app.yaml" 
is not supported - the "python27" runtime will be used instead. A 
description of the differences between the two can be found here:
https://developers.google.com/appengine/docs/python/python25/diff27
INFO 2017-08-26 21:15:25,871 devappserver2.py:116] Skipping SDK update 
check.
INFO 2017-08-26 21:15:26,098 api_server.py:313] Starting API server at: 
http://localhost:51240
INFO 2017-08-26 21:15:26,102 dispatcher.py:226] Starting module 
"default" running at: http://localhost:8080
INFO 2017-08-26 21:15:26,104 admin_server.py:116] Starting admin server 
at: http://localhost:8000
INFO 2017-08-26 21:16:11,234 module.py:416] [default] Detected file 
changes:
  main.py
INFO 2017-08-26 19:17:35,193 stubs.py:50] Sandbox prevented access to 
file "E:\customtinywebdb\customtinywebdb\main.pyc"

INFO 2017-08-26 19:17:35,194 stubs.py:51] If it is a static file, check 
that `application_readable: true` is set in your app.yaml

ERROR2017-08-26 19:17:35,315 cgi.py:122] Traceback (most recent call 
last):

  File "E:\customtinywebdb\customtinywebdb\main.py", line 18, in 

from django.utils import simplejson as json

ImportError: No module named django.utils



INFO 2017-08-26 21:17:35,326 module.py:832] default: "GET / HTTP/1.1" 
500 -
INFO 2017-08-26 21:17:55,250 module.py:416] [default] Detected file 
changes:
  main.py
INFO 2017-08-26 21:18:01,153 api_server.py:945] Applying all pending 
transactions and saving the datastore
INFO 2017-08-26 21:18:01,153 api_server.py:948] Saving search indexes
2017-08-26 21:18:01 (Process exited with code 0)

2017-08-26 21:18:02 Running command: "['C:\\Python27\\python.exe', 
'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py', 
'--skip_sdk_update_check=yes', '--port=8080', '--admin_port=8000', 
'E:\\customtinywebdb\\customtinywebdb']"
WARNING  2017-08-26 21:18:04,263 application_configuration.py:189] The 
"python" runtime specified in "E:\customtinywebdb\customtinywebdb\app.yaml" 
is not supported - the "python27" runtime will be used instead. A 
description of the differences between the two can be found here:
https://developers.google.com/appengine/docs/python/python25/diff27
INFO 2017-08-26 21:18:04,263 devappserver2.py:116] Skipping SDK update 
check.
INFO 2017-08-26 21:18:04,536 api_server.py:313] Starting API server at: 
http://localhost:51354
INFO 2017-08-26 21:18:04,539 dispatcher.py:226] Starting module 
"default" running at: http://localhost:8080
INFO 2017-08-26 21:18:04,540 admin_server.py:116] Starting admin server 
at: http://localhost:8000
INFO 2017-08-26 19:18:09,944 stubs.py:50] Sandbox prevented access to 
file "E:\customtinywebdb\customtinywebdb\main.pyc"

INFO 2017-08-26 19:18:09,944 stubs.py:51] If it is a static file, check 
that `application_readable: true` is set in your app.yaml

INFO 2017-08-26 21:18:10,078 module.py:832] default: "GET / HTTP/1.1" 
200 2401
INFO 2017-08-26 21:18:10,118 module.py:832] default: "GET 
/images/customLogo.gif HTTP/1.1" 304 -
INFO 2017-08-26 21:26:38,720 api_server.py:945] Applying all pending 
transactions and saving the datastore
INFO 2017-08-26 21:26:38,720 api_server.py:948] Saving search indexes
2017-08-26 21:26:39 (Process exited with code 0)

2017-08-26 21:30:22 Running command: "['C:\\Python27\\python.exe', 
'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py', 
'--skip_sdk_update_check=yes', '--port=8080', '--admin_port=8000', 

[google-appengine] app engine data store retrieving the deleted entities

[Yashavanta S B]

I am trying to delete all the entities of a kind. After deleting i am 
trying to make query on the same kind. But the thing is, even after 
deleting all the entities the query is giving the results with some 'n' 
number of rows.

 I know it is the HRD issue where the indexes are not deleted yet. But i 
want to know from where the query is getting the data though we are deleted 
the actual data.

Consider the below code,


class CustomReportInfo {
 String reportName;
 
 // Setters and getters
}

Here i am trying delete the CustomReportInfo kind entities. In order delete 
the entities what i am doing is,


List customReportInfoList= quey(CustomReportInfo.class).
list();
delete(customReportInfoList);


So, as you see i am deleting all the entities of CustomReportInfo. After 
that i am trying to make query on the same kind. Like,

List list = query(CustomReportInfo.class).list();


Still i am getting the 'n' number of rows after deleting. From where the 
query is getting the results even after the deleting the actual data?

-- 
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/b7cb622e-8b48-45c2-aad3-45615553986b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Parameterized type com.googlecode.objectify.Key not supported.

[Yashavanta S B]

I am using Google App Engine 1.9.42, Eclipse, Objectify 4.0rc2. My Class is 
as follows:


@Entity
public class LeadActivity {
@Id
private Long id;
private String subject;

Key jobKey;

//getters & setters 
}


When I try calling the google endpoint for this class thru Eclipse, I get 
the following error: *java.lang.IllegalArgumentException: Parameterized 
type com.googlecode.objectify.Key not supported.*


Any ideas what I am doing wrong?


After this i completely removed above API method and try to call other API 
methods which does not have Key  field type.

But i still get the same messaage  *java.lang.IllegalArgumentException: 
Parameterized type com.googlecode.objectify.Key not supported.*


[INFO] Mar 14, 2017 4:34:29 PM com.google.api.server.spi.SystemService 
invokeServiceMethod
[INFO] SEVERE: exception occurred while calling backend method
[INFO] java.lang.IllegalArgumentException: Parameterized type 
com.googlecode.objectify.Key not supported.
[INFO]  at 
com.google.api.server.spi.config.jsonwriter.JsonConfigWriter.addTypeToSchema(JsonConfigWriter.java:549)
[INFO]  at 
com.google.api.server.spi.config.jsonwriter.JsonConfigWriter.addTypeToNode(JsonConfigWriter.java:671)
 more messages
[INFO]  at 
com.google.api.server.spi.SystemService.getApiConfigs(SystemService.java:411)   
 
[INFO]  at 
com.google.api.server.spi.BackendService.getApiConfigs(BackendService.java:98)  
 
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  

[INFO]  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
 more messages
[INFO] Mar 14, 2017 4:34:29 PM com.google.apphosting.utils.jetty.JettyLogger 
warn
[INFO] WARNING: /_ah/api/vsloginendpoint/v2/vsLoginIonic2: java.io.IOException: 
Failed to retieve API configs with status: 400   


Is the API cached? If so, how do i clean the cache?

What is "Failed to retrieve API configs with status" means?


-- 
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/0d6004b3-91a6-44ff-b035-7450fcd89c39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Is the Google cloud endpoint API cached?

[Yashavanta S B]

Hey guys,

I am trying to call an API method, but i am getting some weird exceptions. 
You can refer the below link.

http://stackoverflow.com/questions/42785183/is-the-google-cloud-endpoint-api-cached

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/cce71bb3-864e-42f5-b94e-3b80a758ad54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

[Yashavanta S B]

The issue is still there, even without setting the default time zone to 
GMT+00:00 in the ServletContextLIstener. Servlet is showing different 
timezone in development server.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5d6a2c25-3a04-4c21-a2cb-59928f3a7025%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

[Yashavanta S B]

Thank you for the information. But my question is - why it is showing the 
different time zone in servlets and filters, even when we are setting the 
default time zone to GMT+00:00. The issue is with the local development 
server. But in the production server it is fine.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/06ba65d6-1d41-4351-8e83-736b92c53d0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine TimeZone changed

[Yashavanta S B]

Thanks for the reply.

What about in development server? Can we change the app-engine time zone in 
development server? Because we want to test date behavior for different 
time zones and we are facing the difficulties in testing the different time 
zone dates.

On Sunday, March 5, 2017 at 3:44:33 AM UTC+5:30, Adam (Cloud Platform 
Support) wrote:
>
> The timezone in App Engine is always set to UTC and cannot be changed. 
> You'll need to convert between UTC and the timezone you wish to use. You 
> can refer to one of the numerous existing threads 
> <https://www.google.ca/search?q=app+engine+set+timezone> on the subject 
> for more background.
>
> On Friday, March 3, 2017 at 11:48:41 PM UTC-5, Yashavanta S B wrote:
>>
>> Hey,
>>
>> In ServletContextListener initialization method we are setting the JVM 
>> Time Zone as
>>
>> public void contextInitialized(ServletContextEvent event) {
>> TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
>> }
>>
>> But when i check the Time Zone information in servlets and filters the 
>> Time Zone got changed.
>>
>> log.info("TimeZone : " + TimeZone.getDefault());
>>
>> What might be the reason? 
>>
>> Thanks
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6926dc41-07a9-4e0c-b122-24ebcb6d4300%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] appengine TimeZone changed

[Yashavanta S B]

Hey,

In ServletContextListener initialization method we are setting the JVM Time 
Zone as

public void contextInitialized(ServletContextEvent event) {
TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
}

But when i check the Time Zone information in servlets and filters the Time 
Zone got changed.

log.info("TimeZone : " + TimeZone.getDefault());

What might be the reason? 

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/307e4922-a885-4cc1-9751-d1e1d2dcafd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Time Zone Changed

[Yashavanta S B]

Hey,

In ServletContextListener initialization method we are setting Time Zone as

public void contextInitialized(ServletContextEvent event) {
TimeZone.setDefault(TimeZone.getTimeZone("GMT+00:00"));
}

 But when i check the Time Zone information in servlets and filters the 
Time Zone got changed.
 Any one know what might be the reason. 

Thanks

 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cb50b521-48a7-4a10-8875-544ca9721c61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore: how to design for huge time-series data

[Etienne B. Roesch]

Hi,

Sorry for the repeat, but I am trying to wrap my head around the 
GAE-osphere and I am getting a bit confused;

I need to store and retrieve/analyse timeseries data, of varying sizes and 
resolutions; at the moment, the data is received and stored on GAE through 
to Google Cloud SQL (python). That's not ideal. I foresee I will have to do 
more analytics than data storage for the sake of storage, and I predict a 
big throughput of data generally, and have thus been looking at 
BigQuery/Datalab. I don't seem to find an obvious way to load data in 
BigQuery from Cloud SQL, and would either have to export the data to Cloud 
Storage in csv-ish, or directly stream the data from the GAE app to 
BigQuery (which is currently my preferred option).
Alternatively, there is the option of passing through to Google Datastore 
first, which for me might be a more flexible way of preprocessing the data 
before it enters in BigQuery.

Is this the way to do things, or am I missing something?

Thanks!

Etienne


On Tuesday, 13 August 2013 13:59:52 UTC+1, Martin Trummer wrote:
>
> I'm a newbie to the AppEngine datastore and like to know how to best 
> design this use case:
> there may be some time-series with huge amount of data: e.g. terra-bytes 
> for one time-series
> the transacations doc 
>  
> says about entity groups:
>
>- *"Every entity belongs to an entity group, a set of one or more 
>entities that can be manipulated in a single transaction."*
>- *"every entity with a given root entity as an ancestor is in the 
>same entity group. All entities in a group are stored in the same 
> Datastore 
>node."*
>
> so does that mean, that all the terra-bytes of data for the huge 
> time-series would end up *on one computer* somewhere in the AppEngine 
> network?
> if so: 
>
>- that's not a good idea, right?
>- how to avoid it? should I split up the data in sections (e.g. per 
>month) where each section has it's own kind/entity group?
>
>

-- 
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/3bfaf3d1-8f39-4fbd-a30f-2577b8428269%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Cant upload Java Application - No name matching appengine.google.com found

[Divya B]

Hi,

I'm using Java GAE, suddenly today I cant able to upload my application 
using "appcfg.cmd   update \war" command.

I'm getting "CertificateException: No name matching appengine.google.com 
found" error.

I have also tried to upload the app after 
deleting .appcfg_oauth2_tokens_java file but not luck. Please advise.


*Error Trace:*
Oct 13, 2016 3:44:21 PM 
com.google.appengine.tools.info.RemoteVersionFactory getVersion
INFO: Unable to access 
https://appengine.google.com/api/updatecheck?runtime=java=1.9.30=1446685788_versions=['1.0']
javax.net.ssl.SSLHandshakeException: 
java.security.cert.CertificateException: No name matching 
appengine.google.com found
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown 
Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown 
Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown 
Source)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown 
Source)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown 
Source)
at java.net.URL.openStream(Unknown Source)
at 
com.google.appengine.tools.info.RemoteVersionFactory.getVersion(RemoteVersionFactory.java:76)
at 
com.google.appengine.tools.info.UpdateCheck.getApplicationVersionInfo(UpdateCheck.java:153)
at 
com.google.appengine.tools.info.UpdateCheck.maybePrintNagScreen(UpdateCheck.java:361)
at com.google.appengine.tools.admin.AppCfg.(AppCfg.java:188)
at com.google.appengine.tools.admin.AppCfg.(AppCfg.java:127)
at com.google.appengine.tools.admin.AppCfg.main(AppCfg.java:123)
Caused by: java.security.cert.CertificateException: No name matching 
appengine.google.com found
at sun.security.util.HostnameChecker.matchDNS(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown 
Source)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown 
Source)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown 
Source)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown 
Source)
... 20 more

Reading application configuration data...
Oct 13, 2016 3:44:22 PM com.google.apphosting.utils.config.IndexesXmlReader 
readConfigXml
INFO: Successfully processed 
C:\Bala\Phonegap\svn\branches\GAE\serverNotification\war\WEB-INF\appengine-generated\datastore-indexes-auto.xml


Beginning interaction for module default...

javax.net.ssl.SSLHandshakeException: 
java.security.cert.CertificateException: No name matching 
appengine.google.com found
Unable to update app: java.security.cert.CertificateException: No name 
matching appengine.google.com found
Please see the logs 
[C:\Users\CHITTA~1\AppData\Local\Temp\appcfg3857449247097391609.log] for 
further information.

-- 
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/1a906ef8-a1d9-4ff4-bc72-6fa72e833913%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] How to Configure JUnit test to suggest the missing datastore-indexes?

[Yashavanta S B]

I would like to know how the JUnit test uses the datastore-indexes while 
doing the queries.

My problem is that, I would like to track the missing datastore-indexes 
using the JUnit test. Is there any way to give the indexes file as an input 
while configuring the datastore?

I don't want to use the auto datastore-indexes for my JUnit tests.

What configuration can I make so that JUnit will be able to suggest what 
are the missing indexes?

Any suggestions would be appreciated. Thanks in advance.

-- 
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/caf416a8-954f-4cfc-bed5-7c7c4aa0b498%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Unable to create directory wp-content/uploads/2016/07

[B Modela]

Unable to create directory wp-content/uploads/2016/07. Is its parent 
directory writable by the server?

I installed Wordpress with Google App Engine on my windows system but I get 
the above error each time I try to upload an image or install a 
plugin/theme. How do I resolve this. Thanks in advance.

-- 
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/7c3af1e1-c0f2-4ed3-abbf-06776b45d2ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Instagram blocking App Engine's urlfetch/sockets IP block

[Ryan B]

9ed even though i'm not
>> >> >> fetching
>> >> >> that particular URL in any of my apps.
>> >> >>
>> >> >> it definitely seems odd, agreed. i only suspect rate
>> >> >> limiting/blocking
>> >> >> at the IP level because i exhaused the other obvious causes. i'd be
>> >> >> happy to be proven wrong!
>> >> >>
>> >> >>
>> >> >> > know what you think in your reply.
>> >> >> >
>> >> >> > Cheers,
>> >> >> >
>> >> >> > Nick
>> >> >> > Cloud Platform Community Support
>> >> >> >
>> >> >> > On Wednesday, May 4, 2016 at 1:09:35 PM UTC-4, Ryan Barrett wrote:
>> >> >> >>
>> >> >> >> thanks for the replies! i should have emphasized that this is for
>> >> >> >> www.instagram.com, not the API. API requests are working fine.
>> >> >> >>
>> >> >> >> you're right that IP blocking wouldn't usually be the first
>> >> >> >> culprit
>> >> >> >> in
>> >> >> >> general, especially for 429s. i tried from a few different apps,
>> >> >> >> though,
>> >> >> >> including shell-hrd (log in my first post), which pretty much
>> >> >> >> never
>> >> >> >> uses
>> >> >> >> urlfetch otherwise based on its quota numbers, so i doubt it's
>> >> >> >> User-Agent
>> >> >> >> blocking. i tried an entirely new www.instagram.com URL and still
>> >> >> >> got a
>> >> >> >> 429,
>> >> >> >> so it's probably not specific URLs, at least due to my own
>> >> >> >> traffic.
>> >> >> >> and
>> >> >> >> i
>> >> >> >> can fetch the same URL fine from my local machine. hence my IP
>> >> >> >> suspicion.
>> >> >> >>
>> >> >> >> i've already worked around this, so it's not urgent. just figured
>> >> >> >> you
>> >> >> >> all
>> >> >> >> might want to know. thanks again!
>> >> >> >>
>> >> >> >> On Monday, May 2, 2016 at 10:52:11 AM UTC-7, Nick (Cloud Platform
>> >> >> >> Support)
>> >> >> >> wrote:
>> >> >> >>>
>> >> >> >>> Hey Ryan,
>> >> >> >>>
>> >> >> >>> I'm unsure that this indicates that App Engine specifically is
>> >> >> >>> being
>> >> >> >>> rate-limited. It's likely that the 429 response is directly
>> >> >> >>> related
>> >> >> >>> to
>> >> >> >>> the
>> >> >> >>> frequency with which you're making requests, regardless of the
>> >> >> >>> origin
>> >> >> >>> of
>> >> >> >>> those requests. While not impossible, I suppose, it would be
>> >> >> >>> surprising if
>> >> >> >>> they were keeping track of App Engine IP ranges and applying a
>> >> >> >>> different
>> >> >> >>> rate-limit, and would require some thorough A/B testing to
>> >> >> >>> prove.
>> >> >> >>> So,
>> >> >> >>> I
>> >> >> >>> recommend just checking their documentation or, if the
>> >> >> >>> rate-limit
>> >> >> >>> is
>> >> >> >>> undocumented, benchmarking to attempt to determine it, and try
>> >> >> >>> to
>> >> >> >>> fly
>> >> >> >>> under
>> >> >> >>> it. Generally, exponential-backoff is a good tactic when dealing
>> >> >> >>> with
>> >> >> >>> rate-limiting.
>> >> >> >>>
>> >> >> >>> Sincerely,
>> >> >> >>>
>> >> >> >>> Nick
>> >> >> >>> Cloud Platform Community Support
>

Re: [google-appengine] Instagram blocking App Engine's urlfetch/sockets IP block

[Ryan B]

thanks for going above and beyond, nick! much appreciated. i'm
currently working around it by using a reverse proxy outside of app
engine, so that my requests are charged to a different IP and isolated
from other app engine apps. glad this info is here now for other
people too.


On Thu, May 5, 2016 at 2:13 PM, 'Nick (Cloud Platform Support)' via
Google App Engine <google-appengine@googlegroups.com> wrote:
>
> After some extensive testing, I've determined that the 429 you're receiving
> is expected behaviour from instagram, and it does relate to a windowing
> average, although it may not be the same as that published in their
> documentation for APIs. After sending a few thousand requests in a span of
> ~15 seconds, I began to receive 429 responses, with some 200's intermixed.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Wednesday, May 4, 2016 at 3:21:46 PM UTC-4, Ryan Barrett wrote:
>>
>> On Wed, May 4, 2016 at 12:02 PM, 'Nick (Cloud Platform Support)' via
>> Google App Engine <google-appengine@googlegroups.com> wrote:
>> > So, you're attempting merely to fetch http://www.instagram.com/, and you
>> > receive 429 on the first request, and you're not launching many other
>> > requests at the same time? It seems odd that a rate-limit response would
>> > come without a condition being reached requiring rate-limiting... Let me
>>
>> i'm actually fetching profile URLs, not the front page. eg `import
>> urllib2; urllib2.urlopen('https://www.instagram.com/kevin/')` in
>> https://shell-hrd.appspot.com/ gets 429ed even though i'm not fetching
>> that particular URL in any of my apps.
>>
>> it definitely seems odd, agreed. i only suspect rate limiting/blocking
>> at the IP level because i exhaused the other obvious causes. i'd be
>> happy to be proven wrong!
>>
>>
>> > know what you think in your reply.
>> >
>> > Cheers,
>> >
>> > Nick
>> > Cloud Platform Community Support
>> >
>> > On Wednesday, May 4, 2016 at 1:09:35 PM UTC-4, Ryan Barrett wrote:
>> >>
>> >> thanks for the replies! i should have emphasized that this is for
>> >> www.instagram.com, not the API. API requests are working fine.
>> >>
>> >> you're right that IP blocking wouldn't usually be the first culprit in
>> >> general, especially for 429s. i tried from a few different apps,
>> >> though,
>> >> including shell-hrd (log in my first post), which pretty much never
>> >> uses
>> >> urlfetch otherwise based on its quota numbers, so i doubt it's
>> >> User-Agent
>> >> blocking. i tried an entirely new www.instagram.com URL and still got a
>> >> 429,
>> >> so it's probably not specific URLs, at least due to my own traffic. and
>> >> i
>> >> can fetch the same URL fine from my local machine. hence my IP
>> >> suspicion.
>> >>
>> >> i've already worked around this, so it's not urgent. just figured you
>> >> all
>> >> might want to know. thanks again!
>> >>
>> >> On Monday, May 2, 2016 at 10:52:11 AM UTC-7, Nick (Cloud Platform
>> >> Support)
>> >> wrote:
>> >>>
>> >>> Hey Ryan,
>> >>>
>> >>> I'm unsure that this indicates that App Engine specifically is being
>> >>> rate-limited. It's likely that the 429 response is directly related to
>> >>> the
>> >>> frequency with which you're making requests, regardless of the origin
>> >>> of
>> >>> those requests. While not impossible, I suppose, it would be
>> >>> surprising if
>> >>> they were keeping track of App Engine IP ranges and applying a
>> >>> different
>> >>> rate-limit, and would require some thorough A/B testing to prove. So,
>> >>> I
>> >>> recommend just checking their documentation or, if the rate-limit is
>> >>> undocumented, benchmarking to attempt to determine it, and try to fly
>> >>> under
>> >>> it. Generally, exponential-backoff is a good tactic when dealing with
>> >>> rate-limiting.
>> >>>
>> >>> Sincerely,
>> >>>
>> >>> Nick
>> >>> Cloud Platform Community Support
>> >>>
>> >>> On Monday, May 2, 2016 at 11:57:15 AM UTC-4, Nickolas Daskalou wrote:
>> >>>>
>> >>>> Hi Ryan,
>> >>>>
>> >>>

Re: [google-appengine] Instagram blocking App Engine's urlfetch/sockets IP block

[Ryan B]

On Wed, May 4, 2016 at 12:02 PM, 'Nick (Cloud Platform Support)' via
Google App Engine <google-appengine@googlegroups.com> wrote:
> So, you're attempting merely to fetch http://www.instagram.com/, and you
> receive 429 on the first request, and you're not launching many other
> requests at the same time? It seems odd that a rate-limit response would
> come without a condition being reached requiring rate-limiting... Let me

i'm actually fetching profile URLs, not the front page. eg `import
urllib2; urllib2.urlopen('https://www.instagram.com/kevin/')` in
https://shell-hrd.appspot.com/ gets 429ed even though i'm not fetching
that particular URL in any of my apps.

it definitely seems odd, agreed. i only suspect rate limiting/blocking
at the IP level because i exhaused the other obvious causes. i'd be
happy to be proven wrong!


> know what you think in your reply.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Wednesday, May 4, 2016 at 1:09:35 PM UTC-4, Ryan Barrett wrote:
>>
>> thanks for the replies! i should have emphasized that this is for
>> www.instagram.com, not the API. API requests are working fine.
>>
>> you're right that IP blocking wouldn't usually be the first culprit in
>> general, especially for 429s. i tried from a few different apps, though,
>> including shell-hrd (log in my first post), which pretty much never uses
>> urlfetch otherwise based on its quota numbers, so i doubt it's User-Agent
>> blocking. i tried an entirely new www.instagram.com URL and still got a 429,
>> so it's probably not specific URLs, at least due to my own traffic. and i
>> can fetch the same URL fine from my local machine. hence my IP suspicion.
>>
>> i've already worked around this, so it's not urgent. just figured you all
>> might want to know. thanks again!
>>
>> On Monday, May 2, 2016 at 10:52:11 AM UTC-7, Nick (Cloud Platform Support)
>> wrote:
>>>
>>> Hey Ryan,
>>>
>>> I'm unsure that this indicates that App Engine specifically is being
>>> rate-limited. It's likely that the 429 response is directly related to the
>>> frequency with which you're making requests, regardless of the origin of
>>> those requests. While not impossible, I suppose, it would be surprising if
>>> they were keeping track of App Engine IP ranges and applying a different
>>> rate-limit, and would require some thorough A/B testing to prove. So, I
>>> recommend just checking their documentation or, if the rate-limit is
>>> undocumented, benchmarking to attempt to determine it, and try to fly under
>>> it. Generally, exponential-backoff is a good tactic when dealing with
>>> rate-limiting.
>>>
>>> Sincerely,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Monday, May 2, 2016 at 11:57:15 AM UTC-4, Nickolas Daskalou wrote:
>>>>
>>>> Hi Ryan,
>>>>
>>>> It seems to be working fine for us (SocialPage.me).
>>>>
>>>> Are you accessing their API using separate access tokens for each user?
>>>>
>>>> Nick
>>>>
>>>>
>>>> On 2 May 2016 at 14:30, Ryan Barrett <goo...@ryanb.org> wrote:
>>>>>
>>>>> hi all! just FYI, it looks like Instagram is blocking/rate limiting App
>>>>> Engine's IPs from fetching www.instagram.com, both urlfetch and sockets,
>>>>> across apps. e.g. this session from https://shell-hrd.appspot.com/ :
>>>>>
>>>>> >>> urllib2.urlopen('https://www.instagram.com/snarfed/')
>>>>> Traceback (most recent call last):
>>>>> ...
>>>>>   File
>>>>> "/base/data/home/runtimes/python/python_dist/lib/python2.5/urllib2.py", 
>>>>> line
>>>>> 506, in http_error_default
>>>>> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
>>>>> HTTPError: HTTP Error 429: Unknown
>>>>>
>>>>> it's not 100% consistent - i occasionally see requests make it through
>>>>> - but the majority get 429ed.
>>>>>
>>>>> not holding my breath, but i figured you all might want to know,
>>>>> especially in case cloud support people have lines of communication open
>>>>> with instagram/facebook for this kind of thing.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Google App Engine" group.
>>>>> To unsubscribe from thi

Re: [google-appengine] Re: Deployment suddenly failed today

[Wizard of B]

Hi Zeehad, Hi Ulapp,
  Thanks a lot for your timely explanation.
Saved a lot of time for me.I still am trying to
figure out OAuth2 utilization in my project.

Thanks & Regards.

On Thu, Apr 14, 2016 at 10:44 PM, Ulapph Corporation 
wrote:

> Oauth2 is very nice because it no longer ask for password as I install to
> different appengine project IDs. It is now just clicking one button in
> order to update all projects at once!
>
> On Thu, Apr 14, 2016 at 9:43 PM, 'Zeehad (Cloud Platform Support)' via
> Google App Engine  wrote:
>
>> Hello,
>>
>> I'm glad to see you've found the solution.
>>
>> This has happened because of ClientLogin Turndown on April 12th. The
>> appcfg.py has been using OAuth 2.0
>>  as
>> default authentication since May 2015
>> .
>> Additional information and instructions for migrating your application to
>> be using OAuth 2.0 is available here
>> 
>> .
>>
>> 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/eRF3ZodRWhE/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/a621803a-0982-4060-9302-495ac9ffb8e8%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/eRF3ZodRWhE/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/CAG-eCFCR2omUwysnu4eVrX%2BFtaMrt9sjKww7dSFuZ%3DnONSKt_g%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAHivR604%3D1tzn_3foPaJvdQ3bSR7EMe49nUx-KFHtRKyMN1F-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Deployment suddenly failed today

[Wizard of B]

Though I was not a part of this discussion I was also facing the same 
problem deploying my app to app engine.
Now this appcfg.py with complete form helped me as well. Thanks a lot.

On Thursday, 14 April 2016 07:42:40 UTC+5:30, Ulapph Corporation wrote:
>
> Hi everyone! I also encountered same issue but below command works fine:
> appcfg.py --application= --email= --oauth2 update 
> PROJECT_DIR
>
> This will launch Chrome to authenticate using oauth2. Let me know if you 
> have any questions. 
>
> On Wednesday, April 13, 2016 at 10:07:34 PM UTC+8, Yan Zhou wrote:
>>
>> I tried to deploy my two projects today, one in python ,one in php, both 
>> failed. 
>>
>> It was OK yesterday, I wonder if anyone has the same problem.
>>
>> Here is the error for python project:
>> Error 404: --- begin server output ---
>> https://developers.google.com/accounts/docs/AuthForInstalledApps
>> --- end server output ---
>>
>> Here is the error for php project:
>> ERROR appcfg.py:2615 An unexpected error occurred. Aborting. 
>> Traceback (most recent call last):
>>   File "C:\Program Files (x86)\Google\google_appengine\
>> google\appengine\tools\appcfg.py", line 2452, in DoUpload
>> missing_files = self.Begin()
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appcfg.py", line 1974, 
>> in Begin
>> payload=config_copy.ToYAML())
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appcfg.py", line 1740, 
>> in Send
>> result = self.rpcserver.Send(url, payload=payload, **kwargs)
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appengine_rpc.py", 
>> line 440, in Send
>> self._Authenticate()
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appengine_rpc.py", 
>> line 581, in _Authenticate
>> super(HttpRpcServer, self)._Authenticate()
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appengine_rpc.py", 
>> line 310, in _Authenticate
>> credentials = self.auth_function()
>>   File "C:\Program Files 
>> (x86)\Google\google_appengine\google\appengine\tools\appcfg.py", line 3241, 
>> in GetUserCredentials
>> password = self.raw_input_fn(password_prompt)
>> EOFError: EOF when reading a line
>>
>> 2016-04-13 21:13:22 (Process exited with code 1)
>>
>> I appreciate if you can help
>> Thanks
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5018bb05-19be-4ef2-93f7-7568f87540ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google App Engine - Tutorial - upload data - 404 NOT_FOUND

[Dassine B.]

I'm newbie and I'm following this tutorial to build a backend for a mobile 
app :
https://cloud.google.com/solutions/mobile/how-to-build-mobile-app-with-app-engine-backend-tutorial/#ios

After setting up all IDs in section "Deploy the Sample App" and "Build and 
Deploy the backed". I tried command line (see section "Populate the 
datastore with data"):

appcfg.py upload_data --config_file bulkloader.yaml 
--url=http://.appspot.com/_ah/remote_api --filename places.csv 
--kind=Place -e @gmail.com

Unforutnately I hit this error :

07:52 AM Uploading data records.[INFO] Logging to 
bulkloader-log-2015.075243[INFO] Throttling transfers:[INFO] 
Bandwidth: 25 bytes/second[INFO] HTTP connections: 8/second[INFO] 
Entities inserted/fetched/modified: 20/second[INFO] Batch Size: 10Error 
404: --- begin server output ---404 NOT_FOUNDError: NOT_FOUND--- end 
server output ---

Did I miss something ? Did I miss the setup the database or something like 
that ?

Thanks for you're help !

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/473a8282-c640-401d-a982-6333ccc6246f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google App Engine - Tutorial - upload data - 404 NOT_FOUND

[Dassine B.]

I'm newbie and I'm following this tutorial to build a backend for a mobile 
app :
https://cloud.google.com/solutions/mobile/how-to-build-mobile-app-with-app-engine-backend-tutorial/#ios

After setting up all IDs in section "Deploy the Sample App" and "Build and 
Deploy the backed". I tried command line (see section "Populate the 
datastore with data"):

appcfg.py upload_data --config_file bulkloader.yaml 
--url=[http://.appspot.com/_ah/remote_api][2] --filename 
places.csv --kind=Place -e @gmail.com

Unforutnately I hit this error :

07:52 AM Uploading data records.[INFO] Logging to 
bulkloader-log-2015.075243[INFO] Throttling transfers:[INFO] 
Bandwidth: 25 bytes/second[INFO] HTTP connections: 8/second[INFO] 
Entities inserted/fetched/modified: 20/second[INFO] Batch Size: 10Error 
404: --- begin server output ---404 NOT_FOUNDError: NOT_FOUND--- end 
server output ---

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e8a1ce7b-bba5-4e6d-b02d-ebe028d4a959%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Deleted default Google Cloud Storage bucket, unable to recreate

[bb b]

Filed https://code.google.com/p/googleappengine/issues/detail?id=12502 for 
the issue specific to Managed VMs.

On Sunday, November 1, 2015 at 3:08:01 AM UTC-8, bb b wrote:
>
> Reviving this thread... Is there a tracker for this issue?
>
> I ran into a different version of this: I accidentally deleted the 
> staging..appspot.com bucket used by the Managed VM deployment 
> process (gcloud preview app deploy) and I can't recreate it; further 
> invocations of "gcloud preview app deploy" fail when trying to add files to 
> this bucket. As far as I know there's no way to change the staging bucket 
> used by that deployment process, so it would seem that I can't use Managed 
> VM in this project anymore. :-(
>
> +1 to Jeff Schnitzer's "it's just very bad practice to have buttons that, 
> when accidentally clicked, wedge the application into a state that cannot 
> be recovered without spending engineering resources on changing the 
> deployment process"
>
>
> On Monday, June 8, 2015 at 8:55:48 PM UTC-7, Chris Ramsdale wrote:
>>
>> well, this isn't cool.  let me look into what's going on here and see if 
>> we can add a fix.  at minimum, we shouldn't allow you to delete the default 
>> bucket (we use if for other services) and get yourself into a horked state. 
>>  -- Chris
>>
>> On Mon, Jun 8, 2015 at 5:08 PM, Sean Lynch <tech...@gmail.com> wrote:
>>
>>> While GCS is very cheap, the default bucket is free up to 5GB and more 
>>> importantly, does not require billing to be enabled. I just ported an 
>>> application using the deprecated google.appengine.ext.files API to GCS but 
>>> now I'll need to enable billing to restore this file upload functionality 
>>> for their application. 
>>>
>>> On Mon, Jun 8, 2015, 6:20 PM Jeff Schnitzer <je...@infohazard.org> 
>>> wrote:
>>>
>>>> While I haven't made this particular mistake, it's actually kind of a 
>>>> big deal. We deploy the same code to acceptance, staging, etc 
>>>> environments. 
>>>> Using the default bucket means we don't have to set up buckets by hand for 
>>>> each of those environments. Before you say "that's not a big deal", the 
>>>> entire career of devops exists because there are a thousand "no big deals" 
>>>> required to set up and run environments. GAE's primary value proposition 
>>>> is 
>>>> "no devops".
>>>>
>>>> Also, it's just very bad practice to have buttons that, when 
>>>> accidentally clicked, wedge the application into a state that cannot be 
>>>> recovered without spending engineering resources on changing the 
>>>> deployment 
>>>> process.
>>>>
>>>> I would star this issue.
>>>>
>>>> Jeff
>>>>
>>>> On Mon, Jun 8, 2015 at 2:38 PM, Patrice (Cloud Platform Support) <
>>>> pvout...@google.com> wrote:
>>>>
>>>>> Hi Sean,
>>>>>
>>>>> Unfortunately, no there is no way to re-create the default bucket if 
>>>>> you deleted it. 
>>>>>
>>>>> I don't see why you really need the default one though... can't you 
>>>>> use any other bucket, since they have the exact same behavior as the 
>>>>> default ones?
>>>>>
>>>>> If you really need to use the default one, yes unfortunately the only 
>>>>> way to do so is to re-create a new app, but again, I don't see why you 
>>>>> need 
>>>>> to take the default one, when you can just create a new one.
>>>>>
>>>>> Cheers!
>>>>>
>>>>>
>>>>> On Monday, June 8, 2015 at 4:00:39 PM UTC-4, Sean Lynch wrote:
>>>>>>
>>>>>> While attempting to get the ACL setup correctly on the default Google 
>>>>>> Cloud Storage bucket (APPID.appspot.com), I deleted this default 
>>>>>> bucket but now I see no way to recreate it.  
>>>>>>
>>>>>> Under Cloud Integration on the old App Engine console, I now see "The 
>>>>>> project was created successfully. See the Basics section for more 
>>>>>> details." 
>>>>>> instead of the create button.  At the top of Application Settings I see 
>>>>>> Google 
>>>>>> Cloud Storage Bucket: APPID.appspot.com but clicking the link 
>>>>>> returns "A required resource is not available&qu

Re: [google-appengine] Re: Deleted default Google Cloud Storage bucket, unable to recreate

[bb b]

Reviving this thread... Is there a tracker for this issue?

I ran into a different version of this: I accidentally deleted the 
staging..appspot.com bucket used by the Managed VM deployment 
process (gcloud preview app deploy) and I can't recreate it; further 
invocations of "gcloud preview app deploy" fail when trying to add files to 
this bucket. As far as I know there's no way to change the staging bucket 
used by that deployment process, so it would seem that I can't use Managed 
VM in this project anymore. :-(

+1 to Jeff Schnitzer's "it's just very bad practice to have buttons that, 
when accidentally clicked, wedge the application into a state that cannot 
be recovered without spending engineering resources on changing the 
deployment process"


On Monday, June 8, 2015 at 8:55:48 PM UTC-7, Chris Ramsdale wrote:
>
> well, this isn't cool.  let me look into what's going on here and see if 
> we can add a fix.  at minimum, we shouldn't allow you to delete the default 
> bucket (we use if for other services) and get yourself into a horked state. 
>  -- Chris
>
> On Mon, Jun 8, 2015 at 5:08 PM, Sean Lynch  > wrote:
>
>> While GCS is very cheap, the default bucket is free up to 5GB and more 
>> importantly, does not require billing to be enabled. I just ported an 
>> application using the deprecated google.appengine.ext.files API to GCS but 
>> now I'll need to enable billing to restore this file upload functionality 
>> for their application. 
>>
>> On Mon, Jun 8, 2015, 6:20 PM Jeff Schnitzer > > wrote:
>>
>>> While I haven't made this particular mistake, it's actually kind of a 
>>> big deal. We deploy the same code to acceptance, staging, etc environments. 
>>> Using the default bucket means we don't have to set up buckets by hand for 
>>> each of those environments. Before you say "that's not a big deal", the 
>>> entire career of devops exists because there are a thousand "no big deals" 
>>> required to set up and run environments. GAE's primary value proposition is 
>>> "no devops".
>>>
>>> Also, it's just very bad practice to have buttons that, when 
>>> accidentally clicked, wedge the application into a state that cannot be 
>>> recovered without spending engineering resources on changing the deployment 
>>> process.
>>>
>>> I would star this issue.
>>>
>>> Jeff
>>>
>>> On Mon, Jun 8, 2015 at 2:38 PM, Patrice (Cloud Platform Support) <
>>> pvout...@google.com > wrote:
>>>
 Hi Sean,

 Unfortunately, no there is no way to re-create the default bucket if 
 you deleted it. 

 I don't see why you really need the default one though... can't you use 
 any other bucket, since they have the exact same behavior as the default 
 ones?

 If you really need to use the default one, yes unfortunately the only 
 way to do so is to re-create a new app, but again, I don't see why you 
 need 
 to take the default one, when you can just create a new one.

 Cheers!


 On Monday, June 8, 2015 at 4:00:39 PM UTC-4, Sean Lynch wrote:
>
> While attempting to get the ACL setup correctly on the default Google 
> Cloud Storage bucket (APPID.appspot.com), I deleted this default 
> bucket but now I see no way to recreate it.  
>
> Under Cloud Integration on the old App Engine console, I now see "The 
> project was created successfully. See the Basics section for more 
> details." 
> instead of the create button.  At the top of Application Settings I see 
> Google 
> Cloud Storage Bucket: APPID.appspot.com but clicking the link returns 
> "A required resource is not available".
>
> I tried to manually recreate the GCS bucket under the new Cloud 
> console, but get the error:
>
>> Note that a bucket name may only contain a dot if it is a valid 
>> domain name, such as "example.com" or "sub.example.com". You will 
>> need to demonstrate that you are an owner or manager of this domain 
>> before 
>> creating the bucket.
>
>
> I'd rather not create a new application to replace this one.  How can 
> I recreate the default bucket? 
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "Google App Engine" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to google-appengi...@googlegroups.com .

>>>
 To post to this group, send email to google-a...@googlegroups.com 
 .
 Visit this group at http://groups.google.com/group/google-appengine.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-appengine/4c503d36-706c-4cbe-ba70-984b529c856f%40googlegroups.com
  
 
 .

 For more options, visit 

[google-appengine] Custom Google Cloud Subdomain Google Webmaster

[Divya B]

Hi,

We have POS app in Google Cloud with custom domain pos.erpfog.com and its 
appspot domain name is erpfog.appspot.com

Question 1. My question is in google webmaster should we add the custom 
domain or appspot domain name? 

Question 2: From our base website(erpfog.com) we have a link to the custom 
domain(pos.erpfog.com) but in google webmaster of base domain is not 
showing the subdomain as internal link.

Can you please suggest?



Regards
Divya

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eb13f7d7-c7d3-4a86-95f8-8b6f4a59ac0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: CSRF token is null!

[Dassine B.]

Having the token didn't fix my problem. I still can't uploads files. It 
works only locally. 

Please if anyone can help me to figure out what's going on it will be 
really appreciated ! 

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ef7b842c-a3f0-477c-a176-db64c3ea93da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: CSRF token is null!

[Dassine B.]

My mistake. I removed  2 lines in settings.py : 


MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
)

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/19f7c62a-8bec-4df3-9896-a220b7246ceb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] CSRF token is null!

[Dassine B.]

Hi there !

I'm building a form which allows the user to upload files. Everything works 
perfectly locally but not live. I got this error : 

POST http://trocodeal.co/ 500 (Internal Server Error)
send @ jquery.min.js:5
b.extend.ajax @ jquery.min.js:5
send @ jquery.fileupload.js:711
(anonymous function) @ jquery.min.js:3
c @ jquery.min.js:3
p.add @ jquery.min.js:3
(anonymous function) @ jquery.min.js:3
b.extend.each @ jquery.min.js:3
(anonymous function) @ jquery.min.js:3
b.extend.Deferred @ jquery.min.js:3
r.then @ jquery.min.js:3
$.widget._onSend @ jquery.fileupload.js:755
(anonymous function) @ jquery.ui.widget.js:105
$.each.newData.submit @ jquery.fileupload.js:811
(anonymous function) @ jquery.fileupload-ui.js:105
c @ jquery.min.js:3
p.fireWith @ jquery.min.js:3
(anonymous function) @ jquery.fileupload-ui.js:618
b.event.dispatch @ jquery.min.js:3
v.handle @ jquery.min.js:3

After hours of research and trying many solution. It might be related to 
crsftoken. this one is available when I use my local environment but not my 
domain. Is this possible ? 

I'm stumped and really stuck ! If anyone can help, it will be really 
appreciated !

Thanks !

FYI. I'm new in web development/GAE/Django

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c835c751-ae7e-4c6f-85ee-10ee42f29574%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: TinyWebDB problem

[B. T.]

Hi,

I have the same issue. How did you fix this problem?

Regards,


On Thursday, March 19, 2015 at 9:15:48 PM UTC+4, Developer Account wrote:

 I don't know what project is it talking about 
 but I fixed the problem by the way 

 On Thu, Mar 19, 2015 at 6:48 PM, Paul Canning pa...@drawandcode.com 
 javascript: wrote:

 Well, are you a direct member of the project?

 On Thursday, March 19, 2015 at 11:53:49 AM UTC, Developer Account wrote:

 I'm using App engine to create tinyWebDB when I click on dashboard it 
 takes me to page that says: Access denied to group members
 To access App Engine, you must be a direct member of the project
 anyone can help ?

  -- 
 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/xKWn7sSam3A/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-appengi...@googlegroups.com javascript:.
 To post to this group, send email to google-a...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-appengine/b8af6422-bec5-45a6-bb78-c553503fd55a%40googlegroups.com
  
 https://groups.google.com/d/msgid/google-appengine/b8af6422-bec5-45a6-bb78-c553503fd55a%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/75dcc5c7-d494-4b37-9eda-8edc60733f96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Regarding Google App Engine application that is configured to use the deprecated service Master/Slave Datastore

[Madhavi B]

Hi Alex,

Thank you for the help.
How can see files list in the application .
As per your mail , only developer can download.
 I am also owner of the application , how can i see the code . I mean under 
what section
I want to update with some  google analytics tracking code in the pages.
Will i be able to do so?

Can you please guide ,  any documentation /videos from google  , so that I 
can  understand  the existing application source code .
 I checked  https://appengine.google.com   ,  i could see some settings of 
the application but could not find source code related information.


Best Regards,
Madhavi





-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/314d322a-d3cf-4574-a69f-60da1e366af3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Regarding Google App Engine application that is configured to use the deprecated service Master/Slave Datastore

[Madhavi B]

Hello All,

I got a email Google App Engine application that is configured to use the 
deprecated service Master/Slave Datastore  and i have migrate to HRD .
My application is not using any data store.  i.e no data store is used for 
my application.
Inspite of this , do i need to migrate to HRD. Please clarify my doubt.

IF yes, then  i have no source code with me.
Application is in java7. How can i download from app engine. I have access 
to app engine.
But i do not know how to download that source code.
Developer who developed this application , he has not given it to me. Now 
now he is not reachable.
Please   help me.

Best REgards,
Madhavi


-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/14d996d8-0356-49ec-ba1c-b6af012e451a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Getting exit_code=204 on every second request

[jothirmayee b]

Sorry, Actually i am getting the 500 error through out my application not a 
particular page. and even the same server call success after a 30 sec . In 
local server it is working fine..

On Monday, November 24, 2014 2:17:27 PM UTC+5:30, Vinny P wrote:

 In your original post, you said calls to one particular page result in a 
 500 Internal Server Error. Does that mean *all calls to that page* result 
 in 500 Internal Server/Error Code 204, or that *errors only occur on that 
 page and on no other page* - but some calls are successful?

 If errors only occur on that page, do those erroring requests share a 
 common thread? For example, perhaps they have the same parameters, access a 
 particular service, and so forth.
  
  
 -
 -Vinny P
 Technology  Media Consultant
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
  
  

 On Sat, Nov 22, 2014 at 1:12 AM, jothirmayee b jothir...@gmail.com 
 javascript: wrote:

 frequently my server calls being failed and getting 500 internal error in 
 logs it is like
 A problem was encountered with the process that handled this request, 
 causing it to exit. This is likely to cause a new process to be used for 
 the next request to your application. (Error code 204).
 and some times same server calls are going to success(200) and it is 
 working fine in local server no failures.




  


-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Getting exit_code=204 on every second request

[jothirmayee b]

in logs i got this error:
A problem was encountered with the process that handled this request, 
causing it to exit. This is likely to cause a new process to be used for 
the next request to your application. (Error code 204).
and i observe that works fine if i try later 30 sec. 

On Saturday, November 22, 2014 12:49:36 AM UTC+5:30, Mars Lan wrote:

 I believe this is a different issue. What do you see in the log?

 On Thursday, November 20, 2014 9:56:18 PM UTC-8, jothirmayee b wrote:

 Hi Amy,
 I have a PHP project which works fine except on one particular page, if 
 requested, fails with a:
 500 Internal server error

 and i added apc.cache_by_default = 0
 to a php.ini file in the root of myApp Engine project. but it didn't 
 work. Can u help me?

 Thanks 
 jothirmayee

 On Tuesday, May 20, 2014 8:58:05 PM UTC+5:30, Amy Unruh wrote:

 Ward,

 Can you try adding
 apc.cache_by_default = 0
 to a php.ini file in the root of your App Engine project, and see if 
 that helps?


 On 20 May 2014 06:42, Ward Vanwalleghem ward.van...@gmail.com wrote:

 Thanks for your response, but I believe there's more going on than just 
 that.  I archived my application and uploaded the standard zend framework 
 skeleton application instead and I still have the problem!  I know I 
 didn't 
 have this when I first started using app engine, so it looks like 
 something 
 I configured triggered this, not the actual application.  Any idea's ???


 On Friday, 16 May 2014 22:40:03 UTC+1, Mars Lan wrote:

 We are aware of an issue where leaving file handles un-closed can 
 sometimes cause the subsequent request to crash.

 On Wednesday, May 14, 2014 4:19:30 AM UTC-7, Ward Vanwalleghem wrote:

 Hi Jeffery,

 did you get to the bottom of this ?  I'm experiencing the same 
 problem...

 Cheers,

 Ward

 On Thursday, 20 June 2013 06:31:25 UTC+1, Jeffery Fernandez wrote:

 Thanks Amy, 

 I have sent you a direct email with details.


 On Thu, Jun 20, 2013 at 3:01 PM, Amy Unruh amyu+...@google.com 
 wrote:

 Jeffery,  

 Would you mind giving me your app id?  You can email it directly if 
 you like.  

  -- 
 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 http://groups.google.com/group/google-appengine
 .
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




 -- 
 Mobile: +61 430 534 464
 Home: +61 3 9764 4439
 Work: +61 3 9723 9399
  
  -- 
 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 http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Getting exit_code=204 on every second request

[jothirmayee b]

frequently my server calls being failed and getting 500 internal error in 
logs it is like
A problem was encountered with the process that handled this request, 
causing it to exit. This is likely to cause a new process to be used for 
the next request to your application. (Error code 204).
and some times same server calls are going to success(200) and it is 
working fine in local server no failures.

On Saturday, November 22, 2014 10:35:52 AM UTC+5:30, jothirmayee b wrote:

 in logs i got this error:
 A problem was encountered with the process that handled this request, 
 causing it to exit. This is likely to cause a new process to be used for 
 the next request to your application. (Error code 204).
 and i observe that works fine if i try later 30 sec. 

 On Saturday, November 22, 2014 12:49:36 AM UTC+5:30, Mars Lan wrote:

 I believe this is a different issue. What do you see in the log?

 On Thursday, November 20, 2014 9:56:18 PM UTC-8, jothirmayee b wrote:

 Hi Amy,
 I have a PHP project which works fine except on one particular page, if 
 requested, fails with a:
 500 Internal server error

 and i added apc.cache_by_default = 0
 to a php.ini file in the root of myApp Engine project. but it didn't 
 work. Can u help me?

 Thanks 
 jothirmayee

 On Tuesday, May 20, 2014 8:58:05 PM UTC+5:30, Amy Unruh wrote:

 Ward,

 Can you try adding
 apc.cache_by_default = 0
 to a php.ini file in the root of your App Engine project, and see if 
 that helps?


 On 20 May 2014 06:42, Ward Vanwalleghem ward.van...@gmail.com wrote:

 Thanks for your response, but I believe there's more going on than 
 just that.  I archived my application and uploaded the standard zend 
 framework skeleton application instead and I still have the problem!  I 
 know I didn't have this when I first started using app engine, so it 
 looks 
 like something I configured triggered this, not the actual application. 
  Any idea's ???


 On Friday, 16 May 2014 22:40:03 UTC+1, Mars Lan wrote:

 We are aware of an issue where leaving file handles un-closed can 
 sometimes cause the subsequent request to crash.

 On Wednesday, May 14, 2014 4:19:30 AM UTC-7, Ward Vanwalleghem wrote:

 Hi Jeffery,

 did you get to the bottom of this ?  I'm experiencing the same 
 problem...

 Cheers,

 Ward

 On Thursday, 20 June 2013 06:31:25 UTC+1, Jeffery Fernandez wrote:

 Thanks Amy, 

 I have sent you a direct email with details.


 On Thu, Jun 20, 2013 at 3:01 PM, Amy Unruh amyu+...@google.com 
 wrote:

 Jeffery,  

 Would you mind giving me your app id?  You can email it directly 
 if you like.  

  -- 
 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 http://groups.google.com/
 group/google-appengine.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




 -- 
 Mobile: +61 430 534 464
 Home: +61 3 9764 4439
 Work: +61 3 9723 9399
  
  -- 
 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 http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Getting exit_code=204 on every second request

[jothirmayee b]

Hi Amy,
I have a PHP project which works fine except on one particular page, if 
requested, fails with a:
500 Internal server error

and i added apc.cache_by_default = 0
to a php.ini file in the root of myApp Engine project. but it didn't work. 
Can u help me?

Thanks 
jothirmayee

On Tuesday, May 20, 2014 8:58:05 PM UTC+5:30, Amy Unruh wrote:

 Ward,

 Can you try adding
 apc.cache_by_default = 0
 to a php.ini file in the root of your App Engine project, and see if that 
 helps?


 On 20 May 2014 06:42, Ward Vanwalleghem ward.van...@gmail.com 
 javascript: wrote:

 Thanks for your response, but I believe there's more going on than just 
 that.  I archived my application and uploaded the standard zend framework 
 skeleton application instead and I still have the problem!  I know I didn't 
 have this when I first started using app engine, so it looks like something 
 I configured triggered this, not the actual application.  Any idea's ???


 On Friday, 16 May 2014 22:40:03 UTC+1, Mars Lan wrote:

 We are aware of an issue where leaving file handles un-closed can 
 sometimes cause the subsequent request to crash.

 On Wednesday, May 14, 2014 4:19:30 AM UTC-7, Ward Vanwalleghem wrote:

 Hi Jeffery,

 did you get to the bottom of this ?  I'm experiencing the same 
 problem...

 Cheers,

 Ward

 On Thursday, 20 June 2013 06:31:25 UTC+1, Jeffery Fernandez wrote:

 Thanks Amy, 

 I have sent you a direct email with details.


 On Thu, Jun 20, 2013 at 3:01 PM, Amy Unruh amyu+...@google.com 
 wrote:

 Jeffery,  

 Would you mind giving me your app id?  You can email it directly if 
 you like.  

  -- 
 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 http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




 -- 
 Mobile: +61 430 534 464
 Home: +61 3 9764 4439
 Work: +61 3 9723 9399
  
  -- 
 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 javascript:.
 To post to this group, send email to google-a...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-appengine.
 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Help Needed in handling Forms (GAE PHP)

[Ryan B]

I think Vinny P is on the right track. Only thing I can see (as stated 
earlier) is the PHP trying to upload as static files. Put the files back 
where they were then replace:

- url: /scripts
static_dir: static_website/scripts


with 


- url: /(.+\.php)$
script: \1

https://cloud.google.com/appengine/docs/php/config/appconfig#PHP_app_yaml_About_app_yaml

And try the upload again.

On Thursday, October 2, 2014 7:34:31 AM UTC-4, Anmol Parashar wrote:


   I'm trying to set up my new website using *Google App Engine (PHP)*. I 
 have bought the domain and my website is working fine. Well, kind of. I 
 have two forms on my website, one asks for just an email and other a 
 contact form. Both of them accepts input but can't send the input to where 
 they are supposed to. A message is displayed, PHP scripts/files are either 
 not configured properly or are missing. Contact your host.

 *Here's the thing*,

 I made my website using Adobe Muse and their forms uses PHP. I have 
 provided all my static html files to Google App Engine (which I'm using as 
 a host) using the Deploy function but whenever I hit deploy, most of the 
 files are read and uploaded except the 8 .php files. The error says, 
 *Mimetype 
 can't be recognized for *.php. Using application octet stream instead.*

 *How do I upload my .php files?* (What to write in my app.yaml)

 I can use the *script:* operative for lets say *index.php* but that page 
 only requires two more php files to run the form and we can't use 
 *script:* 3 times for a single page.

 *If you have any knowledge of HTML or HTML5, can you tell me how to make a 
 form that doesn't use PHP?*

 I'm not using a database. The only thing the form has to do is to send the 
 input to an email.

 My website is Subscriber Shop http://subscribershop.com.

 My app.yaml currently,

 application: sub
 version: 1
 runtime: php
 api_version: 1
 threadsafe: yes

 handlers:
 - url: /favicon\.ico
 static_files: favicon.ico
 upload: favicon\.ico

 - url: /
 static_files: static_website/index.html
 upload: static_website/index.html

 - url: /index.html
 static_files: static_website/index.html
 upload: static_website/index.html

 #specific html pages:
 - url: /about-us.html
 static_files: static_website/about-us.html
 upload: static_website/about-us.html

 - url: /faqs.html
 static_files: static_website/faqs.html
 upload: static_website/faqs.html

 - url: /drop-a-word.html
 static_files: static_website/drop-a-word.html
 upload: static_website/drop-a-word.html

 - url: /unsubscribe
 script: static_website/jl3sxnhv7vv.php

 - url: /css
 static_dir: static_website/css

 - url: /images
 static_dir: static_website/images

 - url: /scripts
 static_dir: static_website/scripts

 - url: /phone
 static_dir: static_website/phone

 - url: /.*
 static_files: static_website/what-what.html 
 upload: static_website/what-what.html

 inbound_services:
 - mail
 - xmpp_subscribe



 My index page, contact page and another are supposed to have these 3 forms 
 and they use a total of 8 .php files that are in *static_website/scripts*

 Can anyone please help?

  *PS:* The support at Adobe Muse says that PHP is not configured. Contact 
 the server admin. How do I tell Google To enable php?


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] error appcfg

[Iñigo B]

Hello, I recieved this message error trying to deploy my App:

ERROR appcfg.py:2323 An error occurred processing file '': HTTP Error 400: 
Bad Request. Aborting. 

Error 400: --- begin server output ---

A version or backend parameter is required.

--- end server output ---

2014-05-14 07:19:25 (Process exited with code 1)

You can close this window now.

Anyone knows how to resolve it? 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.