Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364599

Summary: Project disappears from synchronize view
Product: [Eclipse Project] Platform Reporter: Victor Homyakov <vkhomyackov>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: a.gurov, broot, david.balazic, juraj.misur, konrad_w, malgorzata.tomczyk
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Victor Homyakov CLA 2011-11-23 09:36:12 EST
1. Select two projects (with changes) in Project Explorer.
2. Invoke Team -> Synchronize with Repository. Switch to outgoing mode.
3. Open changed file from first project in Compare Editor, make some more changes and save.
After save the first project often disappears from Synchronize view, although it still has not committed changes. Project reappears after switching to incoming mode and then back to outgoing mode. The second project stays visible.

Another scenario:
Steps 1-2 are the same.
3. Commit two files: one from 1st project, one from 2nd.
After commit the first project disappears, as described above. Also as above project reappears after cycling incoming/outgoing modes.

Projects are in the same SVN repository.
Comment 1 Alexander Gurov CLA 2011-11-24 01:43:51 EST
Unfortunately I can't reproduce the issue with those steps. But one thing is clear: while switching between incoming/outgoing/both/conflicts modes there are no interaction between Team Component (which is responsible for handling those modes) and SVN team provider. So, it seems the problem is related to the Synchronize View itself. I'll move this report to the Team Component, if there is something I can help with - I'll be glad to help.
Also I'm not sure which Eclipse version it is related to, so I'll select 3.7, but Victor, if it is possible, please clarify this moment.

P.S.
As far as I remember, quite a time ago I've reported a similar issue (bug #230853) but since I can't reproduce the problem now I can't help with patches or detection of the problem reasons for the moment. Still, please check the older report too, it is possible that it will help to clarify conditions on the steps to reproduce.
Comment 2 Victor Homyakov CLA 2011-11-24 10:38:57 EST
(In reply to comment #1)
> Unfortunately I can't reproduce the issue with those steps.

Yes, it happens not always, and maybe depends on some previous actions (update part of project from Synchronize view, type of resources committed - Java/JavaScript/JSP/properties/XML, etc.). I am continuously seeing this behaviour since 3.7 release and still cannot find the minimal set of steps to reproduce this bug, except of "start Eclipse and work intensively with SVN for a while" (BTW, we in working group usually make frequent small commits/updates). My Synchronize View is set to Compressed Folders and All Models.

> But one thing is
> clear: while switching between incoming/outgoing/both/conflicts modes there are
> no interaction between Team Component (which is responsible for handling those
> modes) and SVN team provider. So, it seems the problem is related to the
> Synchronize View itself.

Agree.

> Also I'm not sure which Eclipse version it is related to, so I'll select 3.7,
> but Victor, if it is possible, please clarify this moment.

Sorry, I forgot to do this.

Eclipse: Eclipse Java EE IDE for Web Developers.
Version: Indigo Service Release 1
Build id: 20110916-0149

Subversive Integration for the Mylym Project: 0.7.9.I20110602-1700
Subversive JDT Ignore Extensions: 0.7.9.I20110602-1700
Subversive SVN Team Provider: 0.7.9.I20110602-1700
Subversive SVN Team Provider Revision Graph: 0.7.9.I20110602-1700

Subversive SVN 1.6 SVN Kit Connector: 2.2.2.I20110602-1700
Subversive SVN Connectors: 2.2.2.I20110602-1700

> As far as I remember, quite a time ago I've reported a similar issue (bug
> #230853)

One thing is similar to reproducing steps: some files are in src folders (Java sources), some files are in WebRoot (JavaScript, JSP), and others (XML, properties, etc.) are spreaded over the rest of project folders.
Comment 3 Victor Homyakov CLA 2011-11-30 03:04:47 EST
If you can make special build with additional debug logging in Synchronize View, I can install it and give you that logs when I detect that project was disappeared from this view.
Comment 4 Alexander Gurov CLA 2011-12-07 09:18:44 EST
I've stumbled upon the issue too. The actions were taken in this order:
1) start a workspace with the 170 outgoing changes in 5 projects in total and the Synchronize View representation is "Tree", "Incoming/Outgoing Mode"
2) do synhronize (there was 1 incoming modified file)
3) run update action over the project root where the incoming change appears.

After update is done the project disappears. It reappered after I've switched to the "Outgoing Mode" and back. Still this is first time I was able to reproduce the issue and I wasn't searching for it, so I can't tell anything more specific.

Eclipse version - Indigo SR1,
Subversive - 0.7.9.I20111119-1700
Comment 5 Alexander Gurov CLA 2012-01-28 14:29:55 EST
*** Bug 355366 has been marked as a duplicate of this bug. ***
Comment 6 Alexander Gurov CLA 2012-05-11 10:19:20 EDT
*** Bug 378164 has been marked as a duplicate of this bug. ***
Comment 7 Victor Homyakov CLA 2012-10-15 06:50:46 EDT
Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 1
Build id: 20121004-1855

Subversive SVN Team Provider 1.0.0.I20120818-1700

Bug is still not fixed... :(
Comment 8 Victor Homyakov CLA 2012-11-01 06:38:47 EDT
IMHO this bug is related to the "Models" support. Project doesn't disappear any more since I've disabled model support as noted in bug 388445, comment 6.

Eclipse SDK Version: 3.8.1 Build id: M20120914-1540

Subversive SVN Connectors 3.0.0.I20121013-1700
Subversive SVN JDT Ignore Extensions (Optional) 1.0.0.I20120601-1700
Subversive SVN Team Provider 1.0.0.I20120818-1700
SVNKit 1.7.5.v1 Implementation (Optional) 3.0.0.I20121013-1700
Comment 9 Malgorzata Janczarska CLA 2012-11-05 10:26:29 EST
(In reply to comment #4)
> I've stumbled upon the issue too. The actions were taken in this order:
> 1) start a workspace with the 170 outgoing...

Would it be possible that you attached such a workspace in zip? I doubt that even creating 170 random outgoing changes will guarantee reproducing this bug and without reproducing it it'll be hard to investigate.
Comment 10 Alexander Gurov CLA 2012-11-06 02:07:43 EST
(In reply to comment #9)
> (In reply to comment #4)
> > I've stumbled upon the issue too. The actions were taken in this order:
> > 1) start a workspace with the 170 outgoing...
> 
> Would it be possible that you attached such a workspace in zip? I doubt that
> even creating 170 random outgoing changes will guarantee reproducing this
> bug and without reproducing it it'll be hard to investigate.

Unfortunately that workspace is long gone now (since it was to large to attach it anyway I didn't bother to preserve it) and I did not encounter the issue anymore.
Comment 11 Victor Homyakov CLA 2012-11-06 05:00:17 EST
(In reply to comment #10)
> > Would it be possible that you attached such a workspace in zip? I doubt that
> > even creating 170 random outgoing changes will guarantee reproducing this
> > bug and without reproducing it it'll be hard to investigate.
> 
> Unfortunately that workspace is long gone now (since it was to large to
> attach it anyway I didn't bother to preserve it) and I did not encounter the
> issue anymore.

Great. I meet this problem every day when enable "Allow models to participate in synchronizations" on all workspaces I had since Eclipse 3.7.
Comment 12 Malgorzata Janczarska CLA 2012-11-06 05:07:03 EST
(In reply to comment #11)
> Great. I meet this problem every day when enable "Allow models to
> participate in synchronizations" on all workspaces I had since Eclipse 3.7.

So maybe you could prepare a sample workspace where this problem is reproduceable and attach it together with information what models do you have installed and steps to reproduce.
Comment 13 Victor Homyakov CLA 2012-11-09 02:37:20 EST
(In reply to comment #12)
> So maybe you could prepare a sample workspace where this problem is
> reproduceable and attach it together with information what models do you
> have installed and steps to reproduce.

It isn't so easy and will take more time. I don't have a "sample workspace", and my current workspace is ~800Mb big:

~/work/Eclipse 3.8
.metadata 430758K
project1  164728K
project2  227329K
project3  153420K
project4  14169K
project5  540225
Comment 14 Juraj Misur CLA 2012-11-21 18:25:34 EST
Here you can download eclipse with workspace (linux 64).
http://www.sendspace.com/file/mgibfe

Steps taken:
1. Downloaded Eclipse IDE for Java Developers 
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/juno/SR1/eclipse-java-juno-SR1-linux-gtk-x86_64.tar.gz
2. Downloaded Subversive
http://www.eclipse.org/downloads/download.php?file=/technology/subversive/1.0/builds/juno/Subversive-1.0.0.I20120818-1700.zip
from
http://www.eclipse.org/subversive/latest-releases.php
3. Installed Subversive SVN Team Provider and Subversive SVN integration for Mylyn
4. After restart picked SVNKit 1.7.5
5. Checked out h2database sources (1 revision below head)
http://code.google.com/p/h2database/source/checkout
6. Modified file which is updated in head to initiate conflict during synchronization (TriggerObject.java)
7. Modified another file which was not updated in head revision (build.bat)
8. Synchronize with repo and go to synchronize view
9. In outgoing mode see conflict in TriggerObject and outgoing change for build.bat
(workspace prepared until this point)

To reproduce:
Click synchronize, file tree will disappear and 'No changes in SVN (h2)' appears.
This also happens when I do Mark as Merged on the conflicted file.
Comment 15 Alexander Gurov CLA 2012-12-27 11:46:40 EST
*** Bug 392294 has been marked as a duplicate of this bug. ***
Comment 16 David Balažic CLA 2016-10-06 11:33:14 EDT
I see this (or something similar) in Eclipse Neon.1 (v4.6.1),subversive 4.0.2:

I performed a merge that resulted in some conflicts.

I went to "Team Synchronizing" view and in "Synchronize" view switched to "Conflicts Mode". There I doubleclicked a conflicted file and the compare editor appeared.
There I did some changes and saved them by ctrl-s.
After that all items in the "Synchronize" view disappeared.

Switching to some other mode (like "Outgoing") and back restores the content.
Comment 17 Eclipse Genie CLA 2020-04-16 03:19:32 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.