I would imagine anyone doing anything half serious has a series of
environments, all my projects have at least a -Dev and -UAT environment. I'd
much prefer if those got the newer sdk first.
Or just actual environmental support built in - that would solve everyone's
problem (and was underway at
Jesse, agreed. But at a minimum would like to control when it happens so it is
a mutually convenient time.
BTW, you guys used to do SDK pre-releases. This might also help to catch some
issues. I sed to always download the pre-release and run my tests on it.
> On Sep 18, 2015, at 1:15 PM, Jesse
Julian there should be somebody from the engineering team reaching out to
you soon -- if not already -- to understand what happened in your case.
As I mentioned in PK's issue we're working on ways to handle canaries
better. BTW the most obvious approach, a flag for "never run my app on a
canary
Thanks, PK - I will take a look at the issue you filed and comment
accordingly.
We suffered pretty major disruption to our application, and lost many hours
of data, unfortunately. The symptoms were extra null fields in some
Datastore objects, which caused storage of new uploaded data from clien
Hi Julian,
Google routinely does this when they release a new runtime that they believe it
is backwards incompatible. It mostly works OK but I did experience downtime for
several hours on July 24th because a new version was rolled out that had an
issue. It was a Friday, I was in an intercontine
We noticed on Sep 15 and 16 (a couple of days ago) that some of our GAE
instances were running version 1.9.27 of the SDK, rather than the released
version 1.9.26.
(We coincidentally had several serious issues with our application.)
Could someone please advise on how this can happen, and what we
