Bug 8282 - File not being tracked in Git cannot be manipulated
Summary: File not being tracked in Git cannot be manipulated
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-11-08 12:14 UTC by Chris Hatton
Modified: 2013-12-05 18:35 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Chris Hatton 2012-11-08 12:14:42 UTC
I am working with a project that is managed by Git. If I create a new (untracked) file in the project, it cannot be Moved, Renamed or manipulated with MonoDevelops filesystem operations. The following exception is thrown.

However if I explicitly add and commit the file to the Git SCM with an external tool, the file can be manipulated normally in MonoDevelop.


Installation UUID: 215c7942-12e8-4ddd-b0d4-3b63be7064aa
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (
	Package version: 210090011
Mono for Android: Not Installed

Apple Developer Tools:
	 Xcode 4.5 (1839)
	 Build 4G182
Monotouch: 6.0.6
Build information:
	Release ID: 30004007
	Git revision: ea0108260c6a376ecaeffcdb7d03387bd51edda3
	Build date: 2012-09-17 14:09:17+0000
	Xamarin addins: ec43fd5cb223ead4234a9858d1b56eef03dad53a-dirty
Operating System:
	Mac OS X 10.7.5
	Darwin Chris-Hattons-Mac-Mini.local 11.4.2 Darwin Kernel Version 11.4.2
	    Thu Aug 23 16:25:48 PDT 2012
	    root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64

System.InvalidOperationException: Operation is not valid due to the current state of the object
  at System.Linq.Enumerable.Single[VersionInfo] (IEnumerable`1 source, System.Func`2 predicate, Fallback fallback) [0x00038] in /private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System.Core/System.Linq/Enumerable.cs:2330 
  at System.Linq.Enumerable.Single[VersionInfo] (IEnumerable`1 source) [0x00006] in /private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System.Core/System.Linq/Enumerable.cs:2346 
  at MonoDevelop.VersionControl.Repository.GetVersionInfo (FilePath localPath, Boolean getRemoteStatus) [0x0008f] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/Repository.cs:160 
  at MonoDevelop.VersionControl.Git.GitRepository.MoveFile (FilePath localSrcPath, FilePath localDestPath, Boolean force, IProgressMonitor monitor) [0x00000] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl.Git/MonoDevelop.VersionControl.Git/GitRepository.cs:1266 
  at MonoDevelop.VersionControl.VersionControlFileSystemExtension.MoveFile (FilePath source, FilePath dest) [0x00024] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/VersionControlFileSystemExtension.cs:57 
  at MonoDevelop.Core.FileService.InternalMoveFile (System.String srcFile, System.String dstFile) [0x00017] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core/FileService.cs:176 
  at MonoDevelop.Core.FileService.MoveFile (System.String srcFile, System.String dstFile) [0x00000] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core/FileService.cs:162 
  at MonoDevelop.Ide.ProjectOperations.TransferFiles (IProgressMonitor monitor, MonoDevelop.Projects.Project sourceProject, FilePath sourcePath, MonoDevelop.Projects.Project targetProject, FilePath targetPath, Boolean removeFromSource, Boolean copyOnlyProjectFiles) [0x00514] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.4-branch/ea010826/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/ProjectOperations.cs:1675
Comment 1 Chris Hatton 2012-11-08 12:25:54 UTC
Important update! This looks like an edge-case. The Git Repo contains
submodules, one of which somehow became 'removed' from the root repositories
list of submodules. It is still in place on disk, and is still a valid repo in
its own right (hence how I could add it manually to get the positive result
above), but it is no longer attached to the main project Git repo.

I would still consider this a bug because I would expect it to revert to
performing the Git operations on the submodule repo, whether or not it be
attached to the main Git repo.

At the very least, if Git operations fail, I would expect the file
manipulations to be performed on the filesystem regardless, perhaps with a
warning that the Git configuration is unexpected.
Comment 2 Chris Hatton 2012-11-08 12:27:00 UTC
To clarify, the file manipulation fails for files in the detached submodule, but behaves normally in the main Git repo.
Comment 3 Alan McGovern 2012-11-20 11:20:41 UTC
What exactly do you mean by a 'detached submodule' ? Do you mean that git had a submodule checked out and then someone decided that the project didn't need that submodule before and removed it from the git config, but the actual files from that submodule were still left on disk when you updated to that commit?
Comment 4 PJ 2013-11-19 17:05:20 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 PJ 2013-12-05 18:35:39 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.