AnkhSVN2019 icon indicating copy to clipboard operation
AnkhSVN2019 copied to clipboard

Illegal characters in path in EmulateFileIOPermissionChecks

Open PhilJollans opened this issue 4 years ago • 1 comments

I have received this report by Email on 16-July-2020

System.ArgumentException: Illegal characters in path.
at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
at SharpSvn.SvnTools.GetNormalizedFullPath(String path)
at SharpSvn.SvnTools.GetNormalizedDirectoryName(String path)
at Ankh.Scc.StatusCache.SvnStatusCache.StoreItem(SvnItem item)
at Ankh.Scc.StatusCache.SvnStatusCache.GetAlreadyNormalizedItem(String path)
at Ankh.Scc.StatusCache.SvnStatusCache.get_Item(String path)
at Ankh.Scc.PendingChangeManager.ItemRefresh(String file)
at Ankh.Scc.PendingChangeManager.OnTickRefresh()
at Ankh.Scc.Commands.PendingChangeTicker.OnExecute(CommandEventArgs e)
at Ankh.Commands.CommandMapItem.OnExecute(CommandEventArgs e)
at Ankh.Commands.CommandMapper.Execute(AnkhCommand command, CommandEventArgs e)

svn-version=1.9.5
os-version=10.0.18362.0
ankh-version=1.0.0.10
sharpsvn-version=1.9005.3940.224
command=TickRefreshPendingTasks
vs-version=16.0.30309.148 

PhilJollans avatar Sep 26 '20 05:09 PhilJollans

This doesn't make a lot of sense to me.

The function GetNormalizedFullPath does not call FileIOPermission.QuickDemand, so I don't see how the stack trace could be generated.

In fact, I would expect this function to manipulate the path as a string and not to access the file system in any way, and not to check the file permissions.

This makes the error quite baffling.

I am looking at the source of SvnTools.cpp in my version of SharpSVN (1.12), which might differ from the version in SharpSvn 1.9. However, I don't think there has been any change in this function since about 2013, so that is probably not the explanation.

I propose taking no action on this issue, unless there is a new error report with SharpSvn 1.12.

PhilJollans avatar Oct 04 '20 20:10 PhilJollans