Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353933

Summary: When server is slow, changes are submitted but remain outgoing
Product: z_Archived Reporter: Sam Davis <sam.davis>
Component: MylynAssignee: Mylyn Inbox <mylyn-inbox>
Status: RESOLVED DUPLICATE QA Contact: Frank Becker <eclipse>
Severity: normal    
Priority: P3 CC: robert.elves
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Sam Davis CLA 2011-08-04 14:40:25 EDT 
When submitting a comment to a very slow Bugzilla server, the comment remains outgoing even after it was successfully submitted, and one has to refresh the task to see that it was submitted.
Comment 1 Sam Davis CLA 2011-08-04 23:18:01 EDT 
This is because the submit times out. Perhaps in this case, the task should remember that the submit timed out and should force a sync before allowing the user to submit again, so that the user has a chance to see that they already submitted. If it could detect that the comment about to be submitted were a duplicate that would be even better.

For new tasks, it could sync the queries on that repository and detect a the duplicate task, but that might not be a good idea as it could introduce a long delay even when the original submission was not successful.
Comment 2 Steffen Pingel CLA 2011-08-11 06:57:15 EDT 
.

*** This bug has been marked as a duplicate of bug 202211 ***