| Summary: | Every modification of bug report is wrongly recognized as unsuccessful due to problems with mail settings in Bugzilla server. | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | xrealine |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | Robert Elves <robert.elves> |
| Severity: | minor | ||
| Priority: | P4 | CC: | robert.elves |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Server 2003 | ||
| Whiteboard: | |||
|
Description
xrealine
I don't understand this bug at all. (In reply to comment #1) > I don't understand this bug at all. Steps to reproduce: 1) Connect to the local Bugzilla repository in Eclipse IDE via "Add Task Repository" 2) Open the Bugzilla's task ("Open Repository Task ...") 3) Submit a new comment (type a note in "New Comment" and press "Submit") The system responds: "Submit failed: A repository error has occurred..." 4) Refresh the bug report ("Synchronize Incoming Changes") The submitted note is there! It appears Bugzilla cannot send you email... Can you send me the exact details in the error message to webmaster@eclipse.org ? There was an error sending mail from '####@###.com' to '#####@###.com': Couldn't connect to ###.###.###.### After receiving details, looks like you're connecting to an internal bug repository. That Bugzilla is unable to send mail to (someone). Please ask your IT team for assistance, since this is not an Eclipse-related issue. (In reply to comment #4) > After receiving details, looks like you're connecting to an internal bug > repository. That Bugzilla is unable to send mail to (someone). Please ask > your IT team for assistance, since this is not an Eclipse-related issue. Problem with sending mail is not the issue: the user doesn't need mailing notifications at all. I would agree closing this bus as a NOT_ECLIPSE if the issue is completely on server side. It means Bugzilla returns the general error for any Eclipse request. > Problem with sending mail is not the issue: the user doesn't need mailing
> notifications at all. I would agree closing this bus as a NOT_ECLIPSE if the
> issue is completely on server side. It means Bugzilla returns the general error
> for any Eclipse request.
If you are using Eclipse Mylyn with an internal Bugzilla repository that I cannot see, and the internal Bugzilla repository that I cannot see is generating an error, how is that an Eclipse bug?
Before transferring the bug to Mylyn, I would like to make sure that the return code is handled correctly by Eclipse. Could you refer me to the appropriate source code? The warning message in parseHtmlError()[BugzillaClient.java is confusing: "A repository error has occurred:" and , I guess, an error core exception should not be called in this case. This is a known issue with a few possible solutions. Please see the last few comments on bug#268207 to see if either apply to your particular situation. It would be great if you could post a comment there as well if either solution worked for you (or didn't). Thanks! *** This bug has been marked as a duplicate of bug 268207 *** re-opened because of #293873 is different from #268207: the bug reports a wrong notification, it's not related to any connection failure comment on bug#268207: "In my particular case the local Bugzilla server was connected successfully and the attachment was uploaded. But the user is wrongly notified that the operation was failed!" Okay so the cookie issue is not what we're seeing here then. What language is your Bugzilla server localized to (if at all)? There is no localization - English US is installed only. Thanks, Evgeny (In reply to comment #11) > comment on bug#268207: "In my particular case the local Bugzilla server was > connected successfully and the attachment was uploaded. But the user is wrongly > notified that the operation was failed!" > > Okay so the cookie issue is not what we're seeing here then. What language is > your Bugzilla server localized to (if at all)? Have you been able to fix this by resolving the administrators email issue (i.e. by disabling email for the account in question)? (In reply to comment #13) > Have you been able to fix this by resolving the administrators email issue > (i.e. by disabling email for the account in question)? Sometimes this workaround does not applicable. For example, when mail server is temporary down. Thus, the customer would like to have a general fix. Could you post a sample of the complete html error response returned when this happens? Sent by e-mail. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |