[#IDEA-13426] Incoming changes inaccurate

IDEA: Feedback

Incoming changes inaccurate

Created: 25 Jun 07 18:51 Updated: 29 Apr 08 15:51

Component/s:

Version Control Integration. Subversion

File Attachments:	1. idea.log (101 kb) 2. Incoming Changelists Log.txt (42 kb) 3. log.txt (70 kb)
Environment:	Windows XP, Subversion 1.4 client, Subversion 1.3 server

Build:	7,027
Severity:	Medium

Description

« Hide

I'm still getting a single incoming changelist from two months ago, despite my code-base being completely up to date. I've attached the log file fragment created when updating the incoming changes tab.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dmitry Jemerov - 25 Jun 07 18:54

What happened to the directory D:\code\projects\spinal_tap\release_2\nhs\spinal_tap_management_interface_ea\webapp\src\java-test\com\qxlva\nhs\mi\exceptions ? Was it deleted and then recreated?

[ Permlink | « Hide ]

Simon Knott - 25 Jun 07 19:05

It was indeed.

[ Permlink | « Hide ]

Dmitry Jemerov - 25 Jun 07 20:21

Is it now versioned?

[ Permlink | « Hide ]

Simon Knott - 27 Jun 07 14:37

Yes, it's now versioned

[ Permlink | « Hide ]

Simon Knott - 31 Jul 07 16:28

My incoming list of changes now has two erroneous entries on it, the first is still the one mentioned previously. The new changelist that has appeared looks like it's being caused by the following scenario:

1) Deleted a file from module_1.
2) File recreated in module_2 at a later date.
3) Moved file from module_2 to the old location in module_1 - this file has yet to be committed.
4) Incoming changelist now present for step 1.

[ Permlink | « Hide ]

Sean Stephenson - 15 Nov 07 06:26

I am also experiencing this issue with SVN with a revision from October. Although my project is up to date, this particular revision remains in my incoming changes list. I have tried closing IntelliJ and deleting the system/vcsCache folder just to see if that would fix it. The list is, of course, cleared after that, but the same revision comes back into the incoming changes list after I refresh it for the first time. I have attached a log file which appears to have some messages about it.

[ Permlink | « Hide ]

Richard Osbaldeston - 10 Dec 07 13:19

Just adding myself to the suffers list. We've recently replaced the trunk with a branch and now I'm seeing all the changes from last May, April and March appearing as incoming on the trunk all the time. I think the guy who merged simply deleted everything on the trunk and replaced it with the contents of the branch. i.e. not integrate or anything fancy.

[ Permlink | « Hide ]

scott leberknight - 10 Dec 07 20:01

I also have this problem for one of my projects in SVN. I have two entries that never go away, one form last August and now one from last week. One involved renaming a file with different capitalization and another involved adding a file named the same as a file that had previously been deleted. Doing an "svn ls" on the repository shows that the repository is correct, i.e. the files IntelliJ thinks are incoming and never go away are not in the SVN repo.

[ Permlink | « Hide ]

David Linsin - 13 Feb 08 17:21

I have the same problem, after I changed module settings and there were incoming changes waiting. A dirty workaround was to delete the corresponding directory in IDEA's configuration directory. Under Windows it's in $USERDIR\.IntelliJIdea70\system\vcsCache\.

[ Permlink | « Hide ]

Simon Knott - 13 Feb 08 17:51 - edited

I must admit that I've given up on looking at the "Incoming Changes" tab. I now have 17 inaccurate incoming changes and combined with http://www.jetbrains.net/jira/browse/IDEA-15413, it's just not usable. It's a bit of a shame really.

Oh, I should add that clearing the VCS cache does nothing either, since I regularly have to clear that as a workaround to IDEA-16528!

[ Permlink | « Hide ]

Richard Osbaldeston - 25 Feb 08 18:49 - edited

Just created one of these persisting commits so I'll document how I did it here. What happened in this instance was I renamed a badly capitalized filename. So I changed the name via IntelliJ and committed, no obvious problems. But when I went to update later I got messages about checking out the svn_base/tmp versions of this file. What seems to be going on is I'm using Windows and while svn might understand case, windows doesn't and was trying to override the same working files for both entries. So I had to fix this with command-line svn (a recent cygwin version) with an mix of svn cleanup, svn remove & svn commit on the capitalized filename.

Now in IntelliJ I'm seeing this command line commit as incoming. Despite already being committed and trying project updates. I've tried killing the $USERDIR\.IntelliJIdea70\system and even checking out a clean copy of the project (without .iws) but as so as I scan for updates it reappears.

Could these problems be related to using more than one (IntelliJ IDEAs) implementations of svn?

Just tried #7718 and it reappeared - guess I'm stuck with a non-functioning indicator for the next several months again!??

[ Permlink | « Hide ]

Benjamin Schmid - 13 Mar 08 11:20

Hi! I',m also on the list of sufferes.

I want to second the previous comment: I also did a case-only renaming and this file could be the root for these troubles.

[ Permlink | « Hide ]

Brendon McLean - 29 Apr 08 15:51

We're also suffering with this. Performed a case-only rename by doing the following:

Had a directory called "Notes"
Create a new directory called "notes"
copied contents of "Notes" to "notes"
@1157: committed the add of "notes"
@1162: committed the deletion of "Notes" (done separately because the filesystem is case-insensitive)

Idea now sees changeset 1162 in the "Incoming" tab. That was the checkin for deleting "Notes". Interestingly, in the "Changed Files" tree, it is showing "notes" as deleted rather than "Notes".