Feature: Remove deleted file from openFiles map and set file path to null #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
overheadhunter
approved these changes
Apr 14, 2023
src/test/java/org/cryptomator/cryptofs/CryptoFileChannelWriteReadIntegrationTest.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Sebastian Stenzel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #170.
Before actually deleting files on the underlying file system, the openCryptoFile is removed from the (path, file)-mapping. Additionally, the
currentFilePathobject is null'ed, to indicate the openCryptoFile should not be used anymore. The usages ofcurrentFilePathare updated to be null safe.Note, that this only fixes a "symptom", there is still surface for bad timing. The root cause is described in #171.