Bug 306346 - CVS information seems to be completely broken in my workspace
Summary: CVS information seems to be completely broken in my workspace
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-18 07:27 EDT by Frederic Fusier CLA
Modified: 2019-09-06 16:16 EDT (History)
2 users (show)

See Also:


Attachments
SIOOBE displayed in the console (14.55 KB, text/x-log)
2010-03-18 07:27 EDT, Frederic Fusier CLA
no flags Details
Other exceptions when reconnecting the disconnected project (4.37 KB, text/x-log)
2010-03-18 08:57 EDT, Frederic Fusier CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Fusier CLA 2010-03-18 07:27:27 EDT
Created attachment 162390 [details]
SIOOBE displayed in the console

After having updated my Eclipse to 3.6M6 and after to I20100316-0859, I began to get troubles in the package explorer with CVS Tag information. I do not longer see the outcoming changes, then the repository label disappeared from the view and finally even some CVS functionality stopped to work (as Replace with...).

Looking at the console I saw several SIOOBE displayed which may explain this weird behavior (see the attached file)

Sorry, but I'm obliged to set this issue as blocker because I cannot longer use my workspace with such a problem and I really do not see how I can workaround it (-clean does not have any effect here...).
Comment 1 Pawel Pogorzelski CLA 2010-03-18 08:43:59 EDT
Frederic, could you disconnect the project with CVS data removal and reconnect it with the same repository?
Comment 2 Frederic Fusier CLA 2010-03-18 08:57:43 EDT
Created attachment 162395 [details]
Other exceptions when reconnecting the disconnected project

(In reply to comment #1)
> Frederic, could you disconnect the project with CVS data removal and reconnect
> it with the same repository?

I got other exceptions when disconnecting/reconnecting the offending project...
Comment 3 Frederic Fusier CLA 2010-03-18 09:00:56 EDT
(In reply to comment #2)
> Created an attachment (id=162395) [details]
> Other exceptions when reconnecting the disconnected project
> 
> I got other exceptions when disconnecting/reconnecting the offending project...

Sorry, I didn't remove the data when disconnecting... I'm currently doing it, but as it a project with lot of resources, it takes a long while before finishing...
Comment 4 Frederic Fusier CLA 2010-03-18 10:20:11 EDT
(In reply to comment #3)
> 
> Sorry, I didn't remove the data when disconnecting... I'm currently doing it,
> but as it a project with lot of resources, it takes a long while before
> finishing...

The reconnection never finished and I canceled it after more than one hour of refreshing tags dialog... I've opened bug 306369 for this issue
Comment 5 Frederic Fusier CLA 2010-03-18 10:44:13 EDT
I finally succeeded to retrieve CVS information... by deleting the project and reload it from the repository. Hence, reduce a little bit the severity as I'm no longer blocked but still let it critical as it took me more than 1h1/2 to workaround this issue and be able to work again with this workspace...
Comment 6 Pawel Pogorzelski CLA 2010-03-18 11:17:33 EDT
This is a result of corrupted CVS metadata. After discarding it (I agree this could be painful) everything goes back to normal. Frederic and I agreed to reduce the severity to major.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:16:24 EDT
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.