Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314776 - [regression] error parsing in Bugzilla connector does not work properly
Summary: [regression] error parsing in Bugzilla connector does not work properly
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P2 major (vote)
Target Milestone: 3.4   Edit
Assignee: Robert Elves CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 17:01 EDT by Steffen Pingel CLA
Modified: 2010-06-01 16:42 EDT (History)
0 users

See Also:


Attachments
error message (38.54 KB, image/png)
2010-05-27 17:02 EDT, Steffen Pingel CLA
no flags Details
initial fix (8.71 KB, text/plain)
2010-05-27 18:17 EDT, Steffen Pingel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2010-05-27 17:01:10 EDT
Steps:
1. Start with empty workspace so that Eclipse.org repository does not have credentials
2. Submit new bug to Eclipse.org

An unknown error is displayed instead of the expected repository properties dialog or an authentication error.

I have noticed this in other cases as well where issue submission failed due to a invalid security token or mid air collision. Instead of getting a meaningful message I got the message shown in the screenshot.
Comment 1 Steffen Pingel CLA 2010-05-27 17:02:05 EDT
Created attachment 170270 [details]
error message
Comment 2 Steffen Pingel CLA 2010-05-27 18:17:29 EDT
Created attachment 170283 [details]
initial fix
Comment 3 Steffen Pingel CLA 2010-05-27 18:18:44 EDT
Args, patch was meant for bug 310871.
Comment 4 Steffen Pingel CLA 2010-05-29 14:43:43 EDT
I am marking this major since it's a serious usability regression and there is no possible work-around to discover the actual error when task submission fails.
Comment 5 Robert Elves CLA 2010-06-01 16:42:08 EDT
There was a small error committed as part of bug#301870. This has now been resolved and errors now propagate correctly.