-
Notifications
You must be signed in to change notification settings - Fork 266
fix: file stream sharing #1363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix: file stream sharing #1363
Changes from 7 commits
2739e85
ec701cf
2a70ae1
18716e4
c660094
d648b5e
9952eab
4e724f5
c9e04a2
f241cc2
eabc64e
2db45c1
611907b
cd2a151
fd3062a
543acdb
795891b
42a7402
c689d74
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -2,6 +2,7 @@ | ||||||||||||||||||||||||||||||||||||||||
| using System.Threading; | |||||||||||||||||||||||||||||||||||||||||
| using System.Runtime.Versioning; | |||||||||||||||||||||||||||||||||||||||||
| using System.Security.AccessControl; | |||||||||||||||||||||||||||||||||||||||||
| using System.Collections.Concurrent; | |||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||
| namespace System.IO.Abstractions.TestingHelpers; | |||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||
|
|
@@ -32,16 +33,19 @@ public NullFileSystemStream() : base(Null, ".", true) | ||||||||||||||||||||||||||||||||||||||||
| private readonly IMockFileDataAccessor mockFileDataAccessor; | |||||||||||||||||||||||||||||||||||||||||
| private readonly string path; | |||||||||||||||||||||||||||||||||||||||||
| private readonly FileAccess access = FileAccess.ReadWrite; | |||||||||||||||||||||||||||||||||||||||||
| private readonly FileShare share = FileShare.Read; | |||||||||||||||||||||||||||||||||||||||||
| private readonly FileOptions options; | |||||||||||||||||||||||||||||||||||||||||
| private readonly MockFileData fileData; | |||||||||||||||||||||||||||||||||||||||||
| private bool disposed; | |||||||||||||||||||||||||||||||||||||||||
| private static ConcurrentDictionary<string, byte> _fileShareNoneStreams = []; | |||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||
| /// <inheritdoc /> | |||||||||||||||||||||||||||||||||||||||||
| public MockFileStream( | |||||||||||||||||||||||||||||||||||||||||
| IMockFileDataAccessor mockFileDataAccessor, | |||||||||||||||||||||||||||||||||||||||||
| string path, | |||||||||||||||||||||||||||||||||||||||||
| FileMode mode, | |||||||||||||||||||||||||||||||||||||||||
| FileAccess access = FileAccess.ReadWrite, | |||||||||||||||||||||||||||||||||||||||||
| FileShare share = FileShare.Read, | |||||||||||||||||||||||||||||||||||||||||
| FileOptions options = FileOptions.None) | |||||||||||||||||||||||||||||||||||||||||
| : base(new MemoryStream(), | |||||||||||||||||||||||||||||||||||||||||
| path == null ? null : Path.GetFullPath(path), | |||||||||||||||||||||||||||||||||||||||||
|
|
@@ -54,6 +58,11 @@ public MockFileStream( | ||||||||||||||||||||||||||||||||||||||||
| this.path = path; | |||||||||||||||||||||||||||||||||||||||||
| this.options = options; | |||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||
| if (_fileShareNoneStreams.ContainsKey(path)) | |||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
| Access | Share | Result |
|---|---|---|
| Read | Read | ok |
| Read | ReadWrite | ok |
| Read | Write | throw |
| Read | None | throw |
| Write | Read | throw |
| Write | ReadWrite | ok |
| Write | Write | ok |
| Write | None | throw |
| ReadWrite | Read | throw |
| ReadWrite | ReadWrite | ok |
| ReadWrite | Write | throw |
| ReadWrite | None | throw |
I think it would be a great idea to also handle these cases correctly. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. I briefly mentioned an approach to this in a previous comment, where instead of just using the ConcurrentDictionary as effectively a concurrent hashmap, we actually use the value of entries to store the share they were opened with, and check against it where we currently just check for existence.
This is the approach I am planning to go for and start working on, but let me know if you think there's a better idea I'm overlooking or something I'm missing!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fear the solution is not so easy, as you can have multiple streams with e.g. read access and read share open at the same time and only when all streams got disposed should you be able to open the file with write access. So you would need to create a disposable access reference for each stream and remove this instance upon disposal of the stream from some kind of storage.
For reference: in Testably.Abstractions I used a ConcurrentDictionary<IStorageLocation, ConcurrentDictionary<Guid, FileHandle>> with a custom FileHandle class (see here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, multiple streams of the same file open at once...
Thanks for the reference, I'll checkout how its handled in Testably.Abstractions, maybe some of it could be directly ported over?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe I have implemented this functionality and the correct handling of the cases described above in this thread, currently using ConcurrentDictionary<string, ConcurrentDictionary<Guid, (FileAccess access, FileShare share)>> (behaviour covered in MockFileStreamTests.cs). Do review when you get the chance and let me know any pain points, things I may have missed, or desired changes! (maybe a type alias/class like Testably's FileHandle for the access/share tuple...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may want to add some normalization before using the path as the dictionary key. Relative paths passed to the ctor could resolve to the same file system object. The
mockFileDataAccessordoes like this:System.IO.Abstractions/src/TestableIO.System.IO.Abstractions.TestingHelpers/MockFileStream.cs
Line 57 in 72ea54d
System.IO.Abstractions/src/TestableIO.System.IO.Abstractions.TestingHelpers/MockFileSystem.cs
Line 476 in 72ea54d
System.IO.Abstractions/src/TestableIO.System.IO.Abstractions.TestingHelpers/MockFileSystem.cs
Lines 131 to 142 in 72ea54d
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your comment and comprehensive snippets! This is a great point.
I added a private
NormalizePathmethod to theMockFileSystemclass largely based on the above, which should handle relative paths passed to the ctor pointing to the same object.I recognise there is a slight duplication of logic here, and maybe a more rigorous refactor with a general-use, shared
FixPathmethod somewhere (or potentially just makingFixPathpublic?), instead of having these two private methods, would be preferred - this could be worth some discussion.Please let me know your thoughts, and if you think the normalization implemented is sufficient!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to de-duplicate this logic into an internal method that can be used whenever we need to normalize a path to ensure it is done the same everywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. I have been digging around the codebase, and it seems to me a good approach to this would be to move the
FixPathmethod (and associated other methods) logic from theMockFileSystemclass into thePathVerifierclass, updating bothMockFileSystemandMockFileStreamaccordingly?As usual, its possible I'm missing something here or overlooking a more apt approach that those with more experience in this codebase may be able to see, so please do let me know if you think there's a better approach!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds reasonable...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be covered in eabc64e (explicit API test runs in following commit), let me know if there are any other desired changes here!