826: Publishing screenshot comment reviews fails and duplicates comments

timw.a******@gmai***** (Google Code) (Is this you? Claim this profile.)
chipx86
chipx86
March 24, 2009
What's the URL of the page containing the problem?
http://server/r/123/s/456/

What steps will reproduce the problem?
1. Comment on a portion of a screenshot
2. Comment on a portion of another another in the same review request
3. Edit the review (add some review text separate from the comments)
4. Publish the review
5. Re-visit the review request page

What is the expected output? What do you see instead?
Expected:
After 5, the review is published, and it shows up as you just left it in
step 4.

Actual:
After 4, multiple "error" boxes appear in the page body. The still-draft
review now has four comments, where each entered comment has been
duplicated and attached to a seemingly-unrelated screenshot (from a
different review request).

What operating system are you using? What browser?
Ubuntu 8.10 x86_64's Firefox 3.0.5

Please provide any additional information below.
I traced the HTTP traffic, and the POSTs seem to be reasonable.
As in Issue 820, I see comments double-posting (once on entry, and once
milliseconds before the publish POST occurs).

Once the described error has occurred, I notice in the Admin tool that the
review indeed links to 4 comments, and the most recent two are linked to
unrelated screenshots.
#1 timw.a******@gmai***** (Google Code) (Is this you? Claim this profile.)
I have not had this problem since correcting an issue in my database (probably
related to a local test I was running). I haven't reproduced this issue within the
last day. I'll post again if I have not seen it for another two days.
#2 timw.a******@gmai***** (Google Code) (Is this you? Claim this profile.)
I have seen this occur once more (on someone else's computer/account). I have only
just applied the fix for issue 820 (and updated to the latest code), so I will give
this another 3-4 days to see if it's fixed.
chipx86
#3 chipx86
If you could show me the URLs that it attempted to POST to (using Firebug) that would
help. I just fixed a problem that may be relatd to this (might be the same bug) but
I'm unsure if the problem I hit was due to the new version of jQuery.
  • +NeedInfo
  • +chipx86
david
#4 david
  • -NeedInfo
    +Incomplete