Bugzilla – Full Text Bug Listing
| Summary: | Problems submitting reports to QNX PRZilla | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Alex Chapiro <achapiro> | ||||||||||||||||
| Component: | Mylyn | Assignee: | Robert Elves <robert.elves> | ||||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||||
| Severity: | normal | ||||||||||||||||||
| Priority: | P3 | CC: | mik.kersten | ||||||||||||||||
| Version: | 0.4 | ||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Hardware: | PC | ||||||||||||||||||
| OS: | Windows XP | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Alex Chapiro
The New Repository Task action is now in the New wizards as it should be (fyi that fix was part of bug 133196 which will also provide additional UI consistency). That exception occurred because the platform could not be resolved, and I've added a guard to prevent it. But that exception is innocuous and shouldn't have prevented a bugzilla submission. Are you able to submit bugs, or is the login-related error causing that to fail? If so, what is the exact text on the login screen? Created attachment 37072 [details]
Error message
This is the error message I got while creating Bugzilla report.
Using the Eclipse update site, last Friday I installed the latest available version of Mylar including bugzilla repository support. I was looking for New report wizard in File->New->other->Mylar (as defined in the documentation), but didn't find it overthere. That's why I opened this wizard from the task list. I easy can submit reports via the web interface. My credentials are correct and enough to do it. The Fine->New->Other->New Repository Task shortcut was just added yesterday, so for now the right way to create new bugzilla reposts is via the task list. We still have no indication of the source of the failure, assuming that your login information is correct and that you use the right path to the bugzilla server (e.g. https://bugs.eclipse.org/bugs). Are you able to create Bugzilla queries and post comments? Rob: please look into this once you have input on the above. For starters we need to clean up the exception handling for LoginException, and consider including the stack in that failure so that we can better diagnose. I have the permission to update Eclipse Bugzilla. However this case I reported about happend when I tried to create report using our corporative Bugzilla repository, which should be the same. I just don't want to contaminate Eclipse repository with my test reports. Connection seems to be OK because I validated it when added repository. Besides that, I see bugs assigned to me in the task list. Alex, could you double check that the output for your corporate bugzilla server has not been modified (i.e. html output is different on the new bug page compared to unmodified bugzilla output). Currently we parse these pages to get the necessary bug information. This unfortunately is a very brittle solution but will have to hold us over until some form of web services api is implemented. Of course they are slightly different. Moreover, in Eclipse Bugzilla there is one more (2-nd) page in the new bug creating process. Should I change the status of this bug report to Resolved-Later? Could you attach a screenshot (or better yet the html) of the suspect page(s)? That would help us determine a solution. Created attachment 37235 [details]
Two Input new Bug pages
Here you go
Is PRZilla an internal Bugzilla customization by qnx or an externally available product? This is the Bugzilla customisation not a separate product Unfortunately we do not support customized bugzilla repositories. We do our best to keep the repository support within Mylar generic but changes to Bugzilla presentation layer are problematic due to the current reliance on screen scraping. This being said, you could extend Mylar to work with your particular repository. If possible, could you post on this report what is and is not working so that we have a record to refer to when/if we start on such an extension? Thanks. I list below some discrepancies in behavior between WEB interface and Mylar client I ran into while testing Mylar. 1)Search report - selection of Product does not affect content of Components combo. 2) Search report - keywords search. Opens Search view, informs that several occurences was found, but view itself is empty. 3)While connecting to Eclipse bugzilla, I provide any User ID and password, then press Validate button and always get message box "Autentificational redentials are valid. Maybe the cause of such behavior is that my workspace already has one repository, but this looks confusing. 4) Bug editor image looks corrupted (see next attachment). It does not happen always. I easy reproduce it if I scroll long report to the bottom, then start to scroll up. Probably, this is SWT issue. 5) In bug report I typed new comment, then pressed Submit. The only result was this button disabling. Stil had "*" in the Editor tab, editor content has not changed. If I re-opened updated report, I saw there is no submitted changes. 6)This is rather request: no search in report, I tried a big one, and it was very problematic to find something in it. 7) A lot of fields editable throug the WEB interface are not editable in the client editor. Created attachment 37322 [details]
Editor corrupted display
Great. Thanks for this feedback Alex. 1)Search report - selection of Product does not affect content of Components combo. Yes. This should be submitted as a new bug report. If you could submit this it would be great. We would like to be able to credit the individuals who bring up these bugs. 2) Search report - keywords search. Opens Search view, informs that several occurences was found, but view itself is empty. I assume this is due to the QNX Bugzilla issues. I'll investigate handling this better as part of bug# 132395. 3)While connecting to Eclipse bugzilla, I provide any User ID and password, then press Validate button and always get message box "Autentificational redentials are valid. Maybe the cause of such behavior is that my workspace already has one repository, but this looks confusing. I'm unable to reproduce this one. Can you provide more context? 4) Bug editor image looks corrupted (see next attachment). It does not happen always. I easy reproduce it if I scroll long report to the bottom, then start to scroll up. Probably, this is SWT issue. I'm in the process of fixing this at the moment. FormText widget has turned out to be problematic so will be moving to StyledText. 5) In bug report I typed new comment, then pressed Submit. The only result was this button disabling. Stil had "*" in the Editor tab, editor content has not changed. If I re-opened updated report, I saw there is no submitted changes. This again is probably the result of the problems communicating with QNX bugzilla. We'll need handle this error properly. I'll tack this on to the previously mentioned report. 6)This is rather request: no search in report, I tried a big one, and it was very problematic to find something in it. Yes. This is another candidate for a new bug report (feature request). 7) A lot of fields editable throug the WEB interface are not editable in the client editor. We are aware of attachments and keywords. The others should be modifiable. There was a bug which was causing changes to the combo boxes to be ignored but I have fixed that as part of my recent work on the bug editor. >>3)While connecting to Eclipse bugzilla, I provide any User ID and password I made a mistake typing: http://bugs.eclipse.org/bugs (instead of https) and got validation OK. I think it is still a bug. OK, I'll open a couple of new reports as you asked (not the bug mentioned above - it is up to you). That's such a common typo.. Rob, make sure that validation fails for that. Alex: Regarding the bug submission problems you mentioned, we are going to move to an xml/rdf based solution for gathering bug information. This may solve the problems you encountered when submitting to your corporate Bugzilla server. Watch bug# 136219 for updates on the xml/rdf conversion. Alex, The rdf/xml conversion has been completed. Could you try the latest developer release of Mylar against your internal custom bugzilla and let us know if you have any difficulties. Thanks. Developer Release Update Site: download.eclipse.org/technology/mylar/update-site/dev Created attachment 41737 [details]
Problem illustration
I updated plugins and tried to create new bug report. A sort of small browser window came up. When I clicked to it, I got the frozen IDE (see my attachment)
Rob: this happened to me yesterday too, when my internet connection died on submission (browser window came up, disappeared, and Eclipse froze as in the screenshot and needed to be killed). Seems that we recently blotched sometihng with the error handling--I just tried and you can replicate it by trying to assign a non-existant Assigned To email address. Alex: are queries and opening existing reports working? Created attachment 41759 [details]
mylar/context/zip
Done. Fix is in head. Here is context for new bug submission fix.
Reply to comment #21 Query and report opening work fine. I noticed just a few minor issues: - bugzilla URL in my case is quite long, everybody uses alias "przilla"; browser understands it well, but I couldn't use it while defining the new task repository - All the lists in combo boxes seem to be unsorted It was a real pain to find target milestone for example - in Task List there are no column titles ("Description" is an exception) Good to hear. Regarding your comments: - We do not support these kinds of aliases because the URL is used to uniqely identify the task. - Rob is working on fixing this now. - That's correct, the first column is just icon/activation, and the next three are status columns that don't have enough room for text. However, we do plan on adding support for configurable columns (bug 126788). We will have a new build available for you to try submission on again today, since our goal is to have 0.5.2 (scheduled for Friday) to support custom repositories such as QNX's. Alex: could you try the latest dev build and let us know what errors you get on new bug submission if you see any? http://www.eclipse.org/mylar/dl.php Creation of the new report still does not work. After filling the form I press Finish and get a small dialog (the same I mentioned in the previous message). There is only one button OK. I press it and just return to the same form for a new report creation. Thanks God, it does not create a new report:-). THere is nothing in Eclipse Error Log. Alex, I assume this is a browser dialog again, what is the error message? No Error. See attachment. Created attachment 41915 [details]
Browser dialog
From the looks of this there may be a problem with the email address. Could you confirm that your user name and password are valid in the Task Repositories view? Note that we require the User Name to be the email address used with Bugzilla. If I validate settings, I get a message "Authentication credential is valid". I can submit requests, I can open any particular report, but I cannot create new one or edit existing one. Of course I can do it using WEB interface. What can I check more? Is your bugzilla username your email address, or are these different in PRZilla? Have you ever seen PRZilla give that "Confirm Match" message when submitting via the web UI? We need to figure out why it's unsuccessfully trying to match an email address. Created attachment 42052 [details]
Login screen
This is a snapshot of my login screen. I've never seen "Confirm Match" message before.
We still haven't narrowed this down since we can't reproduce. However, today's 0.5.2 release fixed a problem that was related. Please try that and let us know if anything different happens on trying to submit a new report. Now i've got an exception while create new query: An internal error occurred during: "Synchronizing queries: bugzilla". java.lang.AbstractMethodError: org.eclipse.mylar.provisional.tasklist.AbstractRepositoryConnector.getChangedSinceLastSync(Lorg/eclipse/mylar/provisional/tasklist/TaskRepository;Ljava/util/Set;Ljava/util/Date;)Ljava/util/List; at org.eclipse.mylar.provisional.tasklist.SynchronizeQueryJob.run(SynchronizeQueryJob.java:84) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) Before that I updated to 0.5.2, cleaned repository list and create new repository item/ While creating repository item I validated my Bugzilla credentials. It appears as though you have two conflicting versions of Mylar installed. Make sure you've updated all of the features to 0.5.2. Partial updates can happen if you used "Search for updates to the currently installed features". For more information please see: http://www.eclipse.org/mylar/doc/faq.php#install Cleaning solved the last problem (I managed to get rid of 0.5.2 & 0.5.1 features, but not 0.5.0 because uninstall option for these features stayed always disabled). However either update or create new report caused the same Confirm Match message. I've no idea what's wrong. Do you have plugin versions that provide runtime tracing? One more thing I can try tomorrow. I'll create new copy of Eclipse with new workspace and fresh install MyLar to be sure that there is no impact of any old garbage (I have some suspicions that this is a case). Runtime tracing wouldn't help us here since the only error we get is bugzilla's error page. However I'll look into dumping the error page and what got submitted to the error log. Note that if you can't uninstall, you could always delete the old plugins and features from their respective directories. With a clean install, let us know what fails and we'll go from there. Thanks for your patience Alex! I'm sorry, but clean installation RC5 + 0.5.2 didn't change anything. Error log is empty. Any ideas? Could it be helpful if I trace transaction under debugger to grab any data of interest? Okay, there is a new dev build available for you that will output to the log all the attributes being sent when this error occurs. Hopefully from that we can track down the problem. The dev build update site is: download.eclipse.org/technology/mylar/update-site/dev OK, I see now where the bug is. They stored originator's name as "AChapiro@qnx.com", I connected to repository as "achapiro@qnx.com" which is equivalent. However somewhere (in your code or in Bugzilla server) IDs are compared as a case sensitive values. When I connected to repository as "AChapiro@qnx.com", the update transaction completed successfully. Below is the .log file content (after error). !SESSION 2006-05-24 17:12:54.453 ----------------------------------------------- eclipse.buildId=I20060519-1206 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.mylar.core 1 0 2006-05-24 17:40:53.593 !MESSAGE Mylar: bug_status=NEW | resolution= | bug_id=27121 | rep_platform=All | product=TOOLS | op_sys=All | component=TOOLS-IDE | version=unknown | priority=Medium | bug_severity=Non-critical | assigned_to=AChapiro@qnx.com | target_milestone=IDE 4.0 | reporter=MKisel@qnx.com | dependson= | blocked= | bug_file_loc= | newcc=achapiro@qnx.com | keywords= | creation_ts=2005-09-02 08:55 | short_desc=Stacksize field in Project Properties->Compiler tab has no effect | delta_ts=2005-12-07 13:27:23 | cc=Tools_IDE_Mgrs@qnx.com | longdesclength=6 | , source: java.lang.Class I guess under certain conditions/commands Bugzilla doesn't like different capitalization of email addresses. So all is working now I take it? Yes, it works ok when I update existing report. I didn't try to create new one, but I believe it should work (next time I create new report, I'll try it). What I want to mension is: - I never input "AChapiro", always "achapiro"; this is the Bugzilla who capitalizes the first two letters; - It newer causes any problem while I get an access through WEB interface. Sounds like you have it working. I'm going to mark this report resovled but feel free to re-open or open a new report if you discover any problems. Actually, I just have a work around :-) Speaking in general, it does not work. Rob, should we consider always treating the email address as lower case (via String.toLowerCase)? I can't re-produce with Bugzilla 2.22 so assume this is unique to PRZilla. This is not likely something we will be able to fix on our end. We'd like to put this information in the online FAQ. I'm curious, are you able to force your email to lower case in your PRZilla email preferences? I just don't understand what is the difference between xxxx@yyyy.com and XXXX@YYYY.com? As a mail addresses they are similar, don't they? At least, it is very confusing. Our Bugzilla administrator told me that she could enforce using small letters in ID, but in my oppinion it is barely better because for example some people could like to type e-mail address starting with capital letter(s). One particular clue: our Bugzilla uses network identification service to validate user's credentials. And it seems to work OK when I connect to the repository using MyLar, but it fails with the same ID and password while updating or creating new report. It looks starnge for me, doesn't it? Anyway, it's up to you how and when to treat this problem. I just step aside :-) |