[google-appengine] Re: pycrypto 2.6.1 errors

> > @Mark: I'm a little bit confused since I don't think you can set the SDK > version used by the app in production. Rather, it is always auto-upgraded > to the latest. > Ah, no, I mean that we reverted to the old PyCrypto version, rather than the SDK version. Thank you very much for the

[google-appengine] Re: pycrypto 2.6.1 errors

gt; > Any update on my last questions? Did you make a post to the Public Issue > Tracker or would you like to keep corresponding here? > > Cheers, > > Nick > Cloud Platform Community Support > > On Tuesday, December 6, 2016 at 6:41:40 AM UTC-5, Mark Cummins wrote: >&g

[google-appengine] Re: Debugging Datastore Read usage

Aha! Very useful, thanks! On Monday, 12 December 2016 23:01:28 UTC, Alex (Cloud Platform Support) wrote: > > Hi Mark, > > As another option, Google Stackdriver Monitoring > allows you to retrieve > relevant metrics about your Datastore operations.

[google-appengine] Debugging Datastore Read usage

Hi, One day last week our Datastore Read Operations were 5x their normal level, and we're trying to identify why. The problem is almost certainly caused by some corner case in our own code. My question is, how can we go about identifying what caused this issue? As far as I can see, our only

[google-appengine] pycrypto 2.6.1 errors

The new Python SDK (1.9.49) includes pycrypto update to 2.6.1. We've flipped over to the new library version, and we're now seeing errors like this: 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57: PowmInsecureWarning:

Re: [google-appengine] log quota

Could anyone clarify the pricing? The message says "Please upgrade to the Premium Tier", however, when I click "Learn More", there is an option: Basic Tier Logs allotment: 5 GB per month per project Logs allotment overage: $0.50 per GB

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

y, It's an invaluable service, I love >>> appengine because it provides building blocks like these - Instead of >>> depreciating such services, it would be lovely to see new ones, for >>> example, a "videos" service, even though I'm using Zencoder for

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

Thank you for this update, very reassuring and makes me very happy! Personally I'm not too worried about some of the more exotic and less-used services being deprecated, so long as their are reasonable migration paths and the overall platform remains available. On Wednesday, 23 November 2016

[google-appengine] Re: Backing up AppEngine

We use the old crusty Datastire Admin backup tool. We run it nightly from a cron. We backup most important entity types nightly, and some less important types weekly. We have tested disaster recovery, and it all seems to work fine We do this to defend against programmer error or attack, e.g. If

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

I also am beginning to fear a "GAE deprecation email". Could anyone at Google give any reassurance on this? Is GAE standard going to be abandoned in favour of managed VMs (which are actually very different)? -- You received this message because you are subscribed to the Google Groups "Google

Re: [google-appengine] Re: Are pending_ms still reported in the logs?

n the documentation > <https://cloud.google.com/appengine/docs/python/logs/> (ctrl+f "Pending > queue"). So, if it's not there, you can interpret that as pending_ms=0 > > Cheers! > > Nick > Cloud Platform Community Support > > On Tuesday, July 19, 2016 at 1:13:21

[google-appengine] Are pending_ms still reported in the logs?

Is the "pending_ms" metric still reported in the logs? I see it mentioned in various places (e.g. here: http://bjk5.com/post/40833194761/pending-queues-and-loading-requests-on-app-engine) We're trying to debug some latency issues and this seems like a useful metic to examin. However, I can't

[google-appengine] Re: GAE Latency & Instance issues

Thank you so much for this! We also got bitten hard by this problem seemingly out of nowhere in the last few weeks. The same request latency varying from 200ms to over 10,000ms in some cases, with no obvious reason except mysterious gaps in the traces. It's a hard one to debug - there's no

[google-appengine] Usability of new logs viewer

The old App Engine console is gone (sadness). The new logs viewer has improved a lot, but it's still frustrating compared to the old viewer. Here are a few things which really bug me, I wonder if anyone has come up with work-arounds or solutions: 1) Collapse the metadata block [part in curly

Re: [google-appengine] New Cloud Console

+1 for the speed of the new console. The old console is very noticeably faster. On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes wrote: > > Hi Lorne, > > Is there any chance that you can share the console roadmap with us? given > that we are getting the turn-down threats again,

[google-appengine] Re: New Cloud Console

Will the logs viewer in the Cloud Console be improved before the App Engine console is shut down? The main reason I still use the old console is that I find the old logs viewer much more useful than the new one. The new logs viewer is shows a view that is either totally collapsed (useless) or

[google-appengine] Re: Where is the Datastore Admin in the new Developers Console?

Quick workaround I found. If you look at the greyed-out link you'll see the URL has an '' parameter. If you remove that you can still get to all of the greyed out links, at least for now. I hope Google isn't just going to dump this functionality. We rely on Datastore Admin to manage our

[google-appengine] Re: App Engine admin console redirects to Developers Console

Could you give feedback on what happened to the Datastore Admin page? This seems to be gone, and we rely on it to manage our backups and also use it perform bulk deletes. On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote: > > Hello! > > We are pleased to announce that we

[google-appengine] Re: Where is the Datastore Admin in the new Developers Console?

s view. On Wednesday, 7 October 2015 11:35:48 UTC+1, Oliver Urs Lenz wrote: > > Thanks very much for your solution! I am quite exasperated as to how > Google doesn't seem to care about usability. > > On Wednesday, October 7, 2015 at 11:50:41 AM UTC+2, Mark Cummins wrote: >> >>

[google-appengine] Re: App Engine admin console redirects to Developers Console

The new logs viewer is much less usable. Because it's either totally collapsed or totally expanded, it's much much harder to extract meaningful patterns of events at a glance. I would really like to get back the single-line-per-message view that the old viewer had. Also, it seems slower to

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

Hi Andrew, Nice to hear that naked domains are now supported too. Given a free choice, is there any reason to prefer www.example.com over example.com? I'm new to the issue and just noticed some other providers advise against naked domains for scalability reasons: e.g.: