Bugzilla – Full Text Bug Listing
| Summary: | Could not create New Repository Task editor for Bugzilla | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> |
| Component: | Mylyn | Assignee: | Robert Elves <robert.elves> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | wmitsuda |
| Version: | dev | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Eugene Kuleshov
I'm running bootstrapped on (what should be) the same code without any problems but will test the dev build itself.... Can't reproduce with 3.3 dev build. Any particular steps to reproduce? Works for me too... I tried all possible options to create new Bugzilla task and they all failing leaving those two exception stack traces in the log. I can't even create new editor from the bug report... I am running 20070112-1800 dev build. Could not create editor via factory: org.eclipse.mylar.internal.bugzilla.ui.tasklist.BugzillaTaskEditorFactory@57b1ed Unable to create editor ID org.eclipse.mylar.tasklist.ui.taskEditor: assertion failed: I tried few things (switched workspace uninstalled few plug-ins) and got it working now, though I saw some scary exceptions in the logs... java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:157) at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:730) at org.eclipse.mylar.tasks.core.TaskList.getTask(TaskList.java:376) at org.eclipse.mylar.internal.team.ContextActiveChangeSetManager.initContextChangeSets(ContextActiveChangeSetManager.java:129) at org.eclipse.mylar.team.AbstractContextChangeSetManager.enable(AbstractContextChangeSetManager.java:36) at org.eclipse.mylar.internal.team.ContextActiveChangeSetManager.enable(ContextActiveChangeSetManager.java:104) at org.eclipse.mylar.team.MylarTeamPlugin$1.run(MylarTeamPlugin.java:69) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3442) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3082) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1945) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1909) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:425) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(EclipseAppContainer.java:522) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:147) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:170) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:339) at org.eclipse.core.launcher.Main.basicRun(Main.java:283) at org.eclipse.core.launcher.Main.run(Main.java:984) at org.eclipse.core.launcher.Main.main(Main.java:959) It is probably result of some plug-ins I've been trying. Just curious, do you know what specifically could have caused it? It seems like an odd startup problem. I added a null test into TaskList.getTask(..) to avoid such NPEs. I've been playing with coverclipse plugin. Seems like it does not work in Eclipse 3.3M4. Ayways, EclEmma works and look better... Anyway, it does not sound reasonable for me to suppose this is caused by another unrelated plugin... (In reply to comment #9) > Anyway, it does not sound reasonable for me to suppose this is caused by another > unrelated plugin... Yes, we should try to be as defensive as possible to plug-ins using or misusing the Task List, or causing startup problems. So if there is anything else we can do here to improve on that please post. By the way, does anyone else looses .keyring? Happens to me twice in a last month... Loosing passwords, and last time was something with the format and I had to kill it. This has happened to me at least a few times, and I haven't been able to figure out when. I use a runtime workspace, and it does not always happen when I upgrade Eclipse releases, even though it does happen always for the non-runtime workspace. But I have lost it between Eclipse sessions too, most recently last week. (In reply to comment #12) > This has happened to me at least a few times, and I haven't been able to figure > out when. I use a runtime workspace, and it does not always happen when I > upgrade Eclipse releases, even though it does happen always for the non-runtime > workspace. But I have lost it between Eclipse sessions too, most recently last > week. Good. At least I am not alone and it seems like there is a concurrency issue in Platform.*AuthorizationInfo(..) methods. We had to workaround it in TaskRepository, but if someone else (CVS, Subclipse, etc) would write it at the same time it could crash. (In reply to comment #11) > By the way, does anyone else looses .keyring? Happens to me twice in a last > month... Loosing passwords, and last time was something with the format and I > had to kill it. > I think it is related to switching between Eclipse versions, i.e. when you open the same workspace on 3.2 and then on 3.3. This would be something related to the way Platform authorization info works, because I have seem the same thing happens with CVS passwords. I once had this problem too with a RCP application I was writing, but I haven't time to investigate and the documentation doesn't help... If anyone has more info, please let me know. |