Incoming changes stuck with several 2 months old subversion changesets Follow
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?
Please sign in to leave a comment.
Delete the directory. Only it won't help if the changelists are still within
range of initial loading interval - they'll appear again.
Please create a JIRA issue, attach idea.log and describe what files are incorrectly
reported as incoming and what happened to them previously.
"Develop with Pleasure!"
What, you mean like
(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 ...
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".
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 :( )
Do you have any update on this bug? Is there any hope to see it fixed
in a 7.0 point release?
It would be nice to see it fixed, I think I've got five outstanding changelists now which are inaccurate.
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.
I'm seeing this problem on one of my projects too. Does JetBrains need more log files to help figure it out?