Community
Participate
Working Groups
When comparing workspace copy against the repository version (from the Synchronize view), I'm getting the following NPE: null Error Mon Nov 23 11:30:32 EST 2009 An internal error occurred during: "Updating Compare Editor". java.lang.NullPointerException at org.eclipse.team.internal.ccvs.core.filehistory.CVSFileRevision.getAuthor(CVSFileRevision.java:39) at org.eclipse.team.internal.ui.history.FileRevisionTypedElement.fetchAuthor(FileRevisionTypedElement.java:145) at org.eclipse.team.internal.ui.mapping.ResourceDiffCompareInput.updateAuthorInfo(ResourceDiffCompareInput.java:332) at org.eclipse.team.internal.ui.mapping.ResourceCompareInputChangeNotifier.fetchAuthors(ResourceCompareInputChangeNotifier.java:312) at org.eclipse.team.internal.ui.mapping.ResourceCompareInputChangeNotifier$3.run(ResourceCompareInputChangeNotifier.java:304) at org.eclipse.team.internal.core.BackgroundEventHandler$RunnableEvent.run(BackgroundEventHandler.java:176) at org.eclipse.team.internal.ui.mapping.CompareInputChangeNotifier$InputChangeEventHandler.executeRunnableNow(CompareInputChangeNotifier.java:146) at org.eclipse.team.internal.ui.mapping.CompareInputChangeNotifier$InputChangeEventHandler.doDispatchEvents(CompareInputChangeNotifier.java:101) at org.eclipse.team.internal.core.BackgroundEventHandler.dispatchEvents(BackgroundEventHandler.java:394) at org.eclipse.team.internal.core.BackgroundEventHandler.processEvents(BackgroundEventHandler.java:374) at org.eclipse.team.internal.core.BackgroundEventHandler$1.run(BackgroundEventHandler.java:203) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Eric are you getting it all the time? This looks like a common scenario, and you're the first one who noticed it. Is there something special about your configuration?
I suspect it's something either in the cvs server or the content of the files I'm working with, because, as you say, this is a common operation that many people perform every day. My cvs server is CVSNT 2.5.04 running on Mac OS X 10.6.2 (Snow Leopard). Would gathering some client/server interaction logging help here? I'm not setup with a Galileo SDK right now so I can't look at the code in the stack above, but regardless of the cause I don't think an NPE and error dialog should result in any case.
You're absolutely right, it should not happen. Next time you get the error please open the Error Log and CVS console (go to Console view and select CVS in the drop down menu) and look for something suspicious. This could help us finding the cause.
(In reply to comment #3) > You're absolutely right, it should not happen. Next time you get the error > please open the Error Log and CVS console (go to Console view and select CVS in > the drop down menu) and look for something suspicious. This could help us > finding the cause. It's happening on every file that I try to compare in Synchronize view. Curiously, the CVS console is empty right after I see the error (I cleared it before trying). Error Log only has a report with the stack trace above.
Make sure that "Quietness Level" on Team > CVS > Connection (tab) is set to "Verbose".
(In reply to comment #5) > Make sure that "Quietness Level" on Team > CVS > Connection (tab) is set to > "Verbose". It is. Now I'm noticing other odd behavior, including the History View being empty for many files in this project. It still baffles me why the CVS Console is not showing any activity (except when I commit). I've tried restarting Eclipse several times to no avail. Any other ideas for getting CVS activity logged correctly?
(In reply to comment #6) > Now I'm noticing other odd behavior, including the History View being empty for > many files in this project. This might be the same issue as described in bug 293551.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
