-
Notifications
You must be signed in to change notification settings - Fork 204
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
Transport
: Bug fix in rename
method
#6735
Merged
khsrali
merged 17 commits into
aiidateam:main
from
ayushjariyal:issue_6725_rename_function_bug
Feb 10, 2025
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
cfd8b31
Solving bug in rename function
790204e
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] d4b2b4d
Applying review on issue 6735
ayushjariyal a826a4c
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 484a9f7
Resolved merge conflict in rename method
ayushjariyal 051ef84
Solve merge conflicts
ayushjariyal 2023dbe
applying review
ayushjariyal e2c34db
Update docstring
ayushjariyal abcc1b7
Merge branch 'main' into issue_6725_rename_function_bug
ayushjariyal ba66b33
Adding test_rename function
ayushjariyal 6b6746e
Adding test_rename function
ayushjariyal 7fffa13
applying review
ayushjariyal 778148d
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] b722475
Applying review
ayushjariyal cda46d0
applying review
ayushjariyal 35372ae
fix test_rename function
ayushjariyal 383defc
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 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 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 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 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.
The docstring on line 1360 needs fixing. (github does not allow me to comment on that line)
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.
In the docstring on line 1360, it states that OSError is used for both cases—when oldpath and newpath both are not found—which needs to be fixed. However, is it okay to use specific errors (FileNotFoundError and FileExistsError) instead of OSError?
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.
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.
In general. you are right
FileNotFoundError
might be a better fit for such cases, as withOSError
is not immediately clear what's the error case.However, please note
OSError
is the parent ofFileNotFoundError
For the sake of consistency --I assume--
OSError
was chose to raise from ourTransport
class with proper message. This way it's easier to handle, when adopting any of theTransport
plugins.