#7016: Still having problems with Incoming Changes

Using #7016 I made a commit late yesterday afternoon on HEAD (not a branch this time) and then went home. This morning I come in, load up my project in IDEA and the file which I had committed yesterday is still open in the editor and shows the yellow Outdated banner across the top, claiming that the commit I made yesterday had outdated the version of the file I had checked out. I try doing a CVS Update but still the file shows as Outdated.

I go to the Commited Changes window and do a Refresh (this seems to be going much faster, by the way). It still shows the Outdated banner for the file even though the commit doesn't appear in the list of Incoming Changes. I close and re-open the project, the Outdated banner is still there, but now Incoming changes shows all the commits made yesterday including my own.

I go to the Incoming Changes window and do another Refresh. Finally, the Outdated banner disappears, but I'm still seeing an incorrect list of commits in the Incoming Changes, including commits from other branches (they seem to be commits containing files added on a branch) and a commit I made earlier in the week on HEAD, adding the files that I mentioned above. I am also still seeing "file foobar.java was initially added on branch FUNKY_RELEASE_BRANCH" commits. I really don't think those should be shown. They're an ugly artifact of the way CVS works and are not useful.

Come on guys, I know you can do this :)

7 comments

Any word on this? Still a problem in #7020. CVS Update, reload IDEA, still have some files that I committed on Friday that show today as outdated by the commit I made on Friday.

0

Same with subversion, although if I update the changes view the stuck Incoming Changes don't go away. This may be the highest ratio of apparent feature coolness to actual usefulness ever, purely due to this bug.

--Dave Griffith

0

Hello Dave,

DG> Same with subversion, although if I update the changes view the
DG> stuck Incoming Changes don't go away.

I managed to get past that by deleting the caches (explained somewhere else
on this ng, a while back). Haven't seen this problem since.

I'm using subversion, btw, and have no branches (yet).

HTH,
Andrei


0

Hello Dave,

Same with subversion, although if I update the changes view the stuck
Incoming Changes don't go away. This may be the highest ratio of
apparent feature coolness to actual usefulness ever, purely due to
this bug.


JIRA request with idea.log taken while pressing Refresh in Incoming Changes,
please?

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


0

Yep, it's broken for Subversion with me as well.

I'm completely up to date on the branch I'm on, but apparently I have 15 potential incoming changelists ranging all the way back to November last year!

0

Hello Simon,

Yep, it's broken for Subversion with me as well.

I'm completely up to date on the branch I'm on, but apparently I have
15 potential incoming changelists ranging all the way back to November
last year!


JIRA request with idea.log taken while pressing Refresh in Incoming Changes,
please?

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


0

I've trimmed the log file down, so that it starts from the refresh event:

http://www.jetbrains.net/jira/browse/IDEA-13321

0

Please sign in to leave a comment.