[google-appengine] * TIME SENSITIVE * Capabilities API is not working during downtime

6 views
Skip to first unread message

Jeffrey Rosen

unread,
May 5, 2010, 4:43:05 PM5/5/10
to Google App Engine
The capabilities API is not returning as expected :(

I set up my app to use the following code from:

http://blog.notdot.net/2010/03/Handling-downtime-The-capabilities-API-and-testing

More specifically

datastore_write_enabled = capabilities.CapabilitySet('datastore_v3',
capabilities=['write']).is_enabled()

During this maintenance period, datastore_write_enabled is True

If you guys could please set it to False (I can't deploy to fix it)
that would be MUCH appreciated.

I have already gotten hundreds of messages complaining that my
promotion is busted (http://www.wolfire.com/humble)

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

Greg

unread,
May 5, 2010, 5:55:56 PM5/5/10
to Google App Engine
*** SECONDED ***

Well done to the team for the shorter than usual maintenance outage,
BUT COME ON GUYS... our customers and their customers get 500s instead
of the outage message - I'm livid.

We try to manage customer expectations about these outages to limit
the damage they do. We send out warning emails to customers, and then
show an outage message explaining what is going on (and that they were
warned about it). Except our customers get server errors, and we look
like LEMONS.

Now we're going to have to go away and write our own capabilities
test, because we can't trust yours. And if we can't trust the
capbilities API, it raises questions about what else we shouldn't be
trusting. Appengine is predicated on trust - users trust Google can
run the service better than we can.

I have no idea how the capabilities API works - it obviously isn't
automated, so I'm guessing someone forgot to change the settings. One
tiny task missed off the checklist - wait, you did have a checklist,
right? See how that one tiny task has got me questioning your whole
operation.

I love the Appengine concept. But for it to succeed, you have to win
trust, and to do that you have to get everything EXACTLY right. If you
don't have a seriously anal project manager running these maintenance
outages, get one.

Nick Johnson (Google)

unread,
May 7, 2010, 9:20:51 AM5/7/10
to google-a...@googlegroups.com
Hi Jeffrey,

You're quite right about the problems with the capabilities API during this downtime. Unfortunately, a bug prevented it from working correctly this time around, resulting in it incorrectly returning True for queries where it should return False. We've tracked down the bug, and are working on fixing it.

Our sincere apologies for the disruption caused.

-Nick Johnson
--
Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047
Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047
Reply all
Reply to author
Forward
0 new messages