[google-appengine] a transaction committed _and_ errored?

I'm trying to figure out and diagnose an odd problem, and my best guess so far is that a datastore transaction successfully stored data* and* also returned an error message. (I happen to be using Python, but this might be a general datastore issue) The code goes about like this: txn(key): x

[google-appengine] Re: Unexpected Entity Group transaction contention

Multi-entity transactions would allow me to redesign my app to not have the parent-child relationship and then the contentious operations on children would be just fine as those child entities would be unrelated in the new version. I'm sure multi-entity transactions are going to come with

[google-appengine] Unexpected Entity Group transaction contention

Re-reading the documentation, this kinda makes sense, but it bit me recently so I want to tell the story and see what others think. I make an entity Parent(). Some time later I make an entity Child(parent=some_parent) and I do this in a transaction. I do this a bunch, concurrently from

[google-appengine] Docs List API change?

Anyone else notice that suddenly the Docs List API returns next-URI links greater than 500 characters and now they can't be stored in a StringProperty? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web

[google-appengine] Enforced Rate in task queues ruining performance

Why do we sometimes get vastly underperforming task queues? I've attached a screenshot showing how we're getting 0.62/s on a task queue that's configured to run at 10/s. (and another getting 1.25/s where it should be 10/s). What's the magic word to tell AppEngine yes, really, run at full speed?

[google-appengine] Slow log propagation

I'm seeing right now, and a coworker of mine saw in the last couple days, really slow log propagation. It's now Tue Jul 19 13:27:55 UTC 2011 and I haven't seen an INFO log statement since 2011-07-19 11:36:30.982 (UTC) However, if I drop the log console back to 'all requests' I do get current

[google-appengine] vacuum_indexes consistently fails. blocking development.

I've had a production issue open since April with no resolution: http://code.google.com/p/googleappengine/issues/detail?id=4914 My app still has zombie indexes. No amount of update_indexes with a trimmed index.yaml followed by vacuum_indexes makes these things go away. Please fix this bug. We

[google-appengine] Re: Where to post production issues? (2 months with no response)

Hey, you got them to nice you! Lucky you! My issue has been ignored since April! http://code.google.com/p/googleappengine/issues/detail?id=4914 On Jul 11, 2:59 pm, Robby Walker robby.wal...@gmail.com wrote: As far as I can tell, the correct place to post production issues is the AppEngine code

[google-appengine] Re: Error code 203

I am also seeing this and have found no other way to contact the App Engine team as noted. I've added myself to an issue, commenting and starring it, but no response over there either. Just now in the logs from aprigoninjadev.appspot.com 2011-02-14 08:36:39.916 A serious problem was

[google-appengine] Re: Any interest in a Boston-area users group?

Did this ever happen? I have interest in seeing such a thing happen. -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to

[google-appengine] Index Error is impossible to debug

Why does adding this to my index.yaml fail to build an index? - kind: FooBar ancestor: yes properties: - name: __key__ direction: desc That should be a simple enough index, yes? What's the problem? Banging my head against this problem for the last few hours has really soured me on the whole