Bug 372384 - [regression] submitting very long comment fails without error
Summary: [regression] submitting very long comment fails without error
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P1 major (vote)
Target Milestone: 3.7   Edit
Assignee: Frank Becker CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 371662 (view as bug list)
Depends on:
Blocks: 168204
  Show dependency tree
 
Reported: 2012-02-23 13:57 EST by Sam Davis CLA
Modified: 2012-03-01 16:48 EST (History)
1 user (show)

See Also:


Attachments
mylyn/context/zip (1.94 KB, application/octet-stream)
2012-02-24 12:54 EST, Frank Becker CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Davis CLA 2012-02-23 13:57:25 EST
Submitting a very long comment (stack traces) fails without giving an error. I tried repeatedly and it didn't work until I shortened the comment.
Comment 1 Steffen Pingel CLA 2012-02-23 14:50:46 EST
I have the impression that there is a regression that errors are no longer properly shown in the task editor when submission fails. I just saw a similar problem when changing the product of an Eclipse.org bug but not selecting all required details.
Comment 2 Sam Davis CLA 2012-02-23 15:44:06 EST
I think you are right. When I try to change the priority of this bug, it doesn't tell me that I'm not allowed.
Comment 3 Steffen Pingel CLA 2012-02-23 16:52:17 EST
Thanks for verifying. This maybe related to the changes for bug 168204. Frank, let me know if you have time to look into this.
Comment 4 Frank Becker CLA 2012-02-24 00:45:16 EST
I start with this bug later today.
Comment 5 Frank Becker CLA 2012-02-24 12:54:26 EST
Yes this was related to bug 168204 but now we have fixed this.
Comment 6 Frank Becker CLA 2012-02-24 12:54:28 EST
Created attachment 211591 [details]
mylyn/context/zip
Comment 7 Steffen Pingel CLA 2012-03-01 16:48:20 EST
*** Bug 371662 has been marked as a duplicate of this bug. ***