Incoming changes stuck with several 2 months old subversion changesets

Using 7.0 once I refresh the Incoming change list I get 2 old changesets that I have incorporated 2 weeks ago. I am using subversion.

Where is the info stored?
How do I clear this up?
How can I help debugging this?

Thanks

Jacques

8 comments

Hello Jacques,

Using 7.0 once I refresh the Incoming change list I get 2 old
changesets that I have incorporated 2 weeks ago. I am using
subversion.

Where is the info stored?


system\vcsCache

How do I clear this up?


Delete the directory. Only it won't help if the changelists are still within
range of initial loading interval - they'll appear again.

How can I help debugging this?


Please create a JIRA issue, attach idea.log and describe what files are incorrectly
reported as incoming and what happened to them previously.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

What, you mean like
http://www.jetbrains.net/jira/browse/IDEA-13671
http://www.jetbrains.net/jira/browse/IDEA-13728
(no progress since mid-July but both still problematic)

The Incoming view is really useful but it's going to be less so if every
time I rename a file I end up with more cruft that won't disappear ...
R

0

Dmitry,

Do you need me to provide anything more?
Robert seemed to have provided you with everything already.
My 2 stuck changesets do have a bunch of renames as well. I renamed a package from "cluster" to "cluster2".

Jacques

0

Dmitry?

I really would like to see these stuck changeset go away... especially the extra warning in all editors of the files that are in these 2 stuck changeset (which unfortunately were big :( )

Thanks

Jacques

0

Hello Dmitry,
Do you have any update on this bug? Is there any hope to see it fixed
in a 7.0 point release?
R

0

It would be nice to see it fixed, I think I've got five outstanding changelists now which are inaccurate.

0

Same here.
It is inconvenient to have them in the Incoming tab.
It is much more inconvenient to have the out-of-date warning in every editor of these changesets. In my case these were big changeset so a lot of editors have this now. Frustrating.

0

I'm seeing this problem on one of my projects too. Does JetBrains need more log files to help figure it out?

0

Please sign in to leave a comment.