google-app-engine-python

I’m investigating again the unexpected occurrence of TransactionFailedError (too much contention on these datastore entities... in cases, where the code only reads entity groups that are blamed for the contention problems. Setup GAE standard environment, Python 2.7 with NDB (SDK 1.9.51). I managed to observe the error in an isolated app (only me as user) where the same request handler is executed in a task queue and read/write access to the entity-groups mentioned below is only done by this handler. The handler is executed a few times per second and basically is a migration / copy task to move

Is there a way to port the functionality of from google.appengine.api import app_identity from google.appengine.api import urlfetch in the flexible environment? I have a service running on the flex environment which needs to make a request to the standard environment and would like to use App Engine's native app identity and X-Appengine-Inbound-Appid header to do so. It seems that if the origin of the request is from the standard environment, the header is passed on to the flex environment but not the other way around? Update: It is not possible to use the X-Appengine-Inbound-Appid header in

(Background: I am new to Google App Engine, familiar with other cloud providers' services) I am looking for access/view similar to shell access to production node. With a Python/Django based Google App Engine App, I would like to view the code in production. One view I could find is the StackDriver 'Debug' view. However, apparently the code shown in the Debug view doesn't reflect the updated production code (based on what is showing on the production site, for example, the text on the home page different). Does Google App Engine allow me to ssh into the VM where the application/code is running

Specified in app.yaml instance_class: F2 automatic_scaling: min_idle_instances: 5 max_idle_instances: automatic Is their any way out to check instance tier/class from developer console? Only able to guess instance class from billing status costing $0.05 per hour ie F1 instance class. On the new console https://console.cloud.google.com , go to App Engine, then Versions. Under the dropdown More Columns, select Instance Class, then the instance class column will be displayed. I could not find a place where to check specifically the instance type. The only way I could verify that my instance was

In our GAE application, we occasionally see TombstonedTaskError errors in deferred tasks due to named tasks being submitted multiple times with identical names. These tasks seem to be occasionally resubmitted automatically by GAE despite the first execution of the deferred task succeeding. An example can be seen in this log screenshot : the task "refresh_stock_status-1451012400-GNeg-completion-poll-2" was submitted on the morning of Dec 25th, and completed 12-25 07:35:05. The task was then, for some reason, retried automatically by GAE ("X-Appengine-Taskretrycount:1") at 07:35:18, with the

I see that there is already an answer to this question but I feel its outdated. Many things have changes since then. There are now modules , cloud_endpoints and webapp2 . What should be the good directory structure for my project which allows me to add/modify features easily. For example I should be able to manage: Modules. Cron jobs. Task queues. Cloud endpoints. Dan Cornilescu I'd first take a look at modules, at least for these reasons: modules really are in many respects (almost) equivalents to entire (single-module) apps in older docs/references, so once a module's position in the app's

I've got a local Python application configured with runtime: python in it's app.yaml file. When starting the local development server with dev_appserver.py app.yaml all is fine. Since GAE's Local Development Server uses Python2.7 by default, I now want to make use of Python3.x instead. According to Google's documentation, we have to use the flexible environment . Thus I'm changing app.yaml to: runtime: python env: flex runtime_config: python_version: 3 Now dev_appserver.py app.yaml spits out: Under dev_appserver, runtime:python is not supported for Flexible environment. The problem can be