-
Notifications
You must be signed in to change notification settings - Fork 32
Fix file:copy to return error when target file exists without REPLACE_EXISTING
#577
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
Open
DharshiBalasubramaniyam
wants to merge
4
commits into
ballerina-platform:master
Choose a base branch
from
DharshiBalasubramaniyam:file-copy-replace-false-fix
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
57b3fcb
Handle file already exists error when replace false
DharshiBalasubramaniyam 5ee5178
[Automated] Update the native jar versions
DharshiBalasubramaniyam 3c8b115
Fix FileNotFoundError when removing source file
DharshiBalasubramaniyam a8b03de
Refactor testCopyFileToNonExistentFileReplaceFalse test cases to use …
DharshiBalasubramaniyam File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
What's the purpose of this logic? Can't we just do this?
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.
Before copying the file without
REPLACE_EXISTING, we need to ensure that the file not already exist, Thats why i am removing the file early is it already exists.remove()can fail for two different reasons:FileNotFoundError– which is expected (the file already doesn’t exist → fine).When we write
check remove(...), any error (includingFileNotFoundError) will cause the test to fail immediately — even though that particular error is not actually a problem for this setup.The current code distinguishes between those cases:
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 this test is not ideal in that case, because it tests multiple things.
Why do we need to remove the file first?
Maybe what we should do is to remove the file using a
BeforeTestfunction. Shall we do that?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 have now changed the test case to use a
BeforeTestfunctionI removing the file first because, the test is
testCopyFileToNonExistentFileReplaceFalse(); Copy a file to a non-existent destination file, without usingREPLACE_EXISTINGSo, before running the test, we need to guarantee that the destination (
tmpdir + copyFile) truly does not exist — otherwise the test wouldn’t actually be testing the correct scenario.