Community
Participate
Working Groups
Every now and then it appears that submitting bugzillas to Eclipse.org ends with errors that are hard to understand for beginners. A common symptom of these tasks is that all email fields have dropped the @domain parts so that the bugzilla server does no longer recognize the users. Explicitely syncing the opened task normally cures this. Note: Steffen said this might be related with auth failures due to expired cookies.
I have experienced this problem as well. I don't have steps to reproduce but I run into every once in a while.
(In reply to comment #1) > I have experienced this problem as well. I don't have steps to reproduce but I > run into every once in a while. What is your way to fix it? Do you have an workaround? I only see that the value for REPOSITORY_SETTING_SHORT_LOGIN is set in applyToInternal so do you open the BugzillaRepositorySettingPage.
Created attachment 187921 [details] mylyn/context/zip
The workaround is to run the query again. Usually the Bugzilla connector has refreshed the login in the mean time. Does Bugzilla send an HTTP header that could be used to verify if a user is logged in?
*** Bug 339278 has been marked as a duplicate of this bug. ***
In the xml returned from bugzilla you only have user names and no email address. With anonymous you get <reporter name="Frank Becker">Frank</reporter> Logged in you get <reporter name="Frank Becker">Frank@Frank-Becker.de</reporter> I found that something change my user and password for an test bugzilla so these fields are empty and this is the same as anonymous. I think we should disable the submit button when we are not logged in. Thoughts?
I think this problem is actually related to a query running as anonymous and not limited to submission. We need to find a way to verify on a per request basis whether the session has expired and a new login is required.