Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 13774 - Internal error when opening an item from CVS Resource History
Summary: Internal error when opening an item from CVS Resource History
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin McGuire CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 14009
Blocks:
  Show dependency tree
 
Reported: 2002-04-15 07:07 EDT by Vladimir Lahoda CLA
Modified: 2002-04-24 11:28 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Lahoda CLA 2002-04-15 07:07:40 EDT
I am getting this internal error when trying to open any revision of the file 
listed in the CVS Resource history view. (using build 20020321).
Steps to reproduce:
1. In the Packages view open context menu, select Team-> Show in Resource 
history
2. Select any revision from the list, select Open from the context menu. The 
internal error is reported with the following stack trace:


java.lang.IllegalArgumentException: 
	at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:50)
	at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:35)
	at org.eclipse.core.runtime.Status.setPlugin(Status.java:151)
	at org.eclipse.core.runtime.Status.<init>(Status.java:59)
	at
org.eclipse.ui.editors.text.StorageDocumentProvider.setDocumentContent
(StorageDocumentProvider.java:83)
	at
org.eclipse.ui.editors.text.StorageDocumentProvider.setDocumentContent
(StorageDocumentProvider.java:106)
	at
org.eclipse.ui.editors.text.FileDocumentProvider.setDocumentContent
(FileDocumentProvider.java:217)
	at
org.eclipse.ui.editors.text.StorageDocumentProvider.createDocument
(StorageDocumentProvider.java:126)
	at
org.eclipse.ui.editors.text.StorageDocumentProvider.createElementInfo
(StorageDocumentProvider.java:138)
	at
org.eclipse.ui.editors.text.FileDocumentProvider.createElementInfo
(FileDocumentProvider.java:379)
	at
org.eclipse.ui.texteditor.AbstractDocumentProvider.connect
(AbstractDocumentProvider.java:247)
	at
org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput
(AbstractTextEditor.java:1343)
	at
org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:992)
	at
org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:489)
	at org.eclipse.ui.internal.EditorManager.access$1
(EditorManager.java:487)
	at org.eclipse.ui.internal.EditorManager$2.run(EditorManager.java:471)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:56)
	at
org.eclipse.ui.internal.EditorManager.openInternalEditor(EditorManager.java:464)
	at
org.eclipse.ui.internal.EditorManager.openInternalEditor(EditorManager.java:533)
	at
org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:365)
	at
org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:268)
	at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:1293)
	at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:1254)
	at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:1246)
	at
org.eclipse.team.internal.ccvs.ui.actions.OpenLogEntryAction$1.run
(OpenLogEntryAction.java:75)
	at org.eclipse.team.ui.actions.TeamAction$1.run(TeamAction.java:153)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:56)
	at org.eclipse.team.ui.actions.TeamAction.run(TeamAction.java:150)
	at
org.eclipse.team.internal.ccvs.ui.actions.OpenLogEntryAction.run
(OpenLogEntryAction.java:66)
	at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:204)
	at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:407)
	at
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent
(ActionContributionItem.java:361)
	at
org.eclipse.jface.action.ActionContributionItem.access$0
(ActionContributionItem.java:352)
	at
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent
(ActionContributionItem.java:47)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:75)
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:637)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1420)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1208)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:722)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:705)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:777)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:319)
	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:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:196)
	at org.eclipse.core.launcher.Main.run(Main.java:555)
	at org.eclipse.core.launcher.Main.main(Main.java:396)
Comment 1 Kevin McGuire CLA 2002-04-17 14:34:10 EDT
I've tried in 0412 and can't get the error.
Please relog if you can reproduce this in M5
Comment 2 Kevin McGuire CLA 2002-04-19 11:46:06 EDT
From email from reporter:

I've just tested this bug in M5, getting still the same results as reported
in bugzilla.

Further testing revealed that it works with some CVS servers, but not with
others (but I can't figure out the difference yet) - so it is probably
problem of those servers' settings rather than bug in Eclispe.
Nevertheless, I think that Eclipse could react to such problem somehow
better tahn just throwing an internal error :-)

==================
My reply:

Thanks for the follow up.  If you attach to the bug the cvs log info we might 
be able to sort it out.  Some servers have been customized (unfortunately) and 
a small change in how information is presented will throw us off, since all we 
get back from the server is text that we must parse to figure out what's going 
on.

Obviously if we could try against the server in question that would be best, 
but I assume that isn't possible.

As for how the error is reported, the failure is in how the document provider 
is creating the status to tell us of an error, which then throws away the real 
error info - an IO exception of some kind from looking at the code.  You will 
see I've reported this separately to the UI team and have marked it as blocking 
your bug.
Comment 3 Kevin McGuire CLA 2002-04-23 15:01:16 EDT

*** This bug has been marked as a duplicate of 14235 ***
Comment 4 Kevin McGuire CLA 2002-04-23 15:02:02 EDT
modified wrong bug report
Comment 5 Kevin McGuire CLA 2002-04-24 11:28:50 EDT
Reporter is using CVS version 1.10.7 running on FreeBSD 3.4.

This bug relates to a known problem with that version of CVS, which we do not 
support (actually, never have).

Reporter will need to upgrade to CVS 1.11.1p1, which is a good idea anyway 
since 1.10.7 was known to have other problems.