Notes API causes ResourceConflict
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Servers |
Fix Released
|
High
|
Chad Miller |
Bug Description
Traceback (most recent call last):
Module /srv/ubuntuone.
raise ResourceConflic
Module /srv/ubuntuone.
**params)
Module /srv/ubuntuone.
resp, data = self.resource.
Module /srv/ubuntuone.
self.
Module /srv/ubuntuone.
res = func(*args, **kwargs)
Module /srv/ubuntuone.
Record(
Module /srv/ubuntuone.
return func(request, *args, **kwargs)
Module /srv/ubuntuone.
return self.view_
Module /srv/ubuntuone.
response = callback(request, *callback_args, **callback_kwargs)
Module /srv/ubuntuone.
response = self.get_
Module /var/lib/
return self.applicatio
ResourceConflict: ' ('conflict', 'Document update conflict.')'
lib/ubuntuone/
The documents PUT in the db have no _rev, so all PUTs after the first will have a ResourceConflict.
The incorrect handling of ResourceConflicts in general is Bug#499301 .
Changed in ubuntuone-servers: | |
assignee: | nobody → Chad Miller (cmiller) |
status: | New → In Progress |
description: | updated |
Changed in ubuntuone-servers: | |
importance: | Undecided → High |
visibility: | private → public |
tags: | added: christmas-bug |
What the heck. Here's what Snowy does:
http:// git.gnome. org/browse/ snowy/tree/ api/handlers. py
if update. has_key( 'latest- sync-revision' ):
new_ sync_rev = update[ 'latest- sync-revision' ]
if new_sync_rev != current_sync_rev + 1:
# TODO: Return a more useful error response?
return rc.BAD_REQUEST