Hello Johan, I just reproduced the issue from within the datastore admin tool (no queued tasks, nothing external operating on this record)
1. Go to this record: https://appengine.google.com/datastore/edit?app_id=streamingservicesplatform&namespace=&version_id=338.351619451003591871&key=ahlzdHJlYW1pbmdzZXJ2aWNlc3BsYXRmb3JtcjALEgpTU1BBcnRpY2xlIiBjNGJmMDA5Mzk4Yjk0NTFjMTY2YzFiMmQwMWJkZjE5ZAw 2. The Link is this: http://indiatoday.intoday.in/site/Story/143334/Cover Story/http://indiatoday.intoday.in/site/story/upa-paralysed-decision- making-process-collapse-in-credibility-and-stall-in-governance Change it to this: http://indiatoday.intoday.in/site/story/upa-paralysed-decision-making-process-collapse-in-credibility-and-stall-in-governance 3. Click 'save entity' 4. Wait 5 minutes. 5. Entity reverts. Any insight or additional items you would like me to try would be appreciated. On Jul 5, 2:44 am, Johan Euphrosine <pro...@google.com> wrote: > Hi Tirrel, > > What happened when you tried to read the record just after writing, 1 > minute later, 2 minute later, etc until 5 minutes ? > > Are you sure that your application code doesn't interact with the > datastore on the same record elsewhere, on a request, tasksqueue or a > cron job ? > > We are currently monitoring your application, please try to reproduce > this issue so we can a closer look at what is happening. > > Thanks in advance. > > > > > > > > > > On Tue, Jul 5, 2011 at 10:10 AM, Tirrell Payton <tpay...@bt-software.net> > wrote: > > Indeed but thats the best way to be sure: > > 1. See behavior in code. Troubleshoot code. Same result. > > 2. Test behavior with remote api. Update record via remote api. > > Same result. > > 3. Test behavior directly in datastore admin. Same result. > > > Testing in the datastore admin quickly gets us through 'check your > > code' 'check the cache' 'can we see a code snippet', etc. > > Moreover, it ensures the good people at google are able to replicate > > the issue under the same circumstances as laid out at the beginning. > > > On Jul 4, 11:06 pm, "Brandon Wirtz" <drak...@digerat.com> wrote: > >> I view the DataStore Administrator as a "in case of emergency break glass > >> and slit your wrists" tool. > > >> -----Original Message----- > >> From: google-appengine@googlegroups.com > > >> [mailto:google-appengine@googlegroups.com] On Behalf Of Tirrell Payton > >> Sent: Monday, July 04, 2011 9:40 PM > >> To: Google App Engine > >> Subject: [google-appengine] Re: Database opaquely rolling back changes > > >> There is no code. I am doing this in the datastore administrator. > >> Select a record, update the field, click 'save entity' > > >> On Jul 4, 9:09 pm, Robert Kluin <robert.kl...@gmail.com> wrote: > >> > I'm guessing you've got a cache issue too. Either the changes you > >> > think are getting committed aren't (and your returning / caching) non > >> > committed data, or your seeing old cached data served. > > >> > Could you show us the actual code you use to save and fetch the results? > > >> > Robert > >> > On Jul 4, 2011 1:04 PM, "Tirrell Payton" <tpay...@bt-software.net> > >> > wrote:> APPID: streamingservicesplatform.appspot.com > > >> > > Database opaquely rolls back changes. > >> > > To reproduce: > > >> > > Bring up record: > > >> > ahlzdHJlYW1pbmdzZXJ2aWNlc3BsYXRmb3JtcjALEgpTU1BBcnRpY2xlIiBjNGJmMDA5Mz > >> > k4Yjk 0NTFjMTY2YzFiMmQwMWJkZjE5ZAw > > >> > > Change the link from this: > > >> >http://indiatoday.intoday.in/site/Story/143334/Cover> > >> > Story/http://indiatoday.intoday.in/site/story/upa-paralysed-decision- > >> > > making-process-collapse-in-credibility-and-stall-in-governance > > >> > > to this: > > >> >http://indiatoday.intoday.in/site/story/upa-paralysed-decision-making... > > >> > > Wait 5 minutes. > > >> > > Bring up record: > > >> > ahlzdHJlYW1pbmdzZXJ2aWNlc3BsYXRmb3JtcjALEgpTU1BBcnRpY2xlIiBjNGJmMDA5Mz > >> > k4Yjk 0NTFjMTY2YzFiMmQwMWJkZjE5ZAw > > >> > > Expected result, changes to the link are still there. > >> > > Actual result, database has 'rolled back' to the previous version of > >> > > this record. > > >> > > -- > >> > > 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-appengine@googlegroups.com. > >> > > To unsubscribe from this group, send email to > > >> > google-appengine+unsubscr...@googlegroups.com.> For more options, > >> > google-appengine+visit this group at > > >> >http://groups.google.com/group/google-appengine?hl=en. > > >> -- > >> 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-appengine@googlegroups.com. > >> To unsubscribe from this group, send email to > >> google-appengine+unsubscr...@googlegroups.com. > >> For more options, visit this group > >> athttp://groups.google.com/group/google-appengine?hl=en. > > > -- > > 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-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > Johan Euphrosine (proppy) > Developer Programs Engineer > Google Developer Relations -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
