-
Notifications
You must be signed in to change notification settings - Fork 582
fix(Ray): Retain the original function name when patching Ray tasks #4858
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
Merged
+23
−4
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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.
Potential bug: Adding the
_tracingparameter without checking for its existence can cause aValueErrorif the user's function already has a parameter with that name, crashing the application.Description: The Ray integration modifies the signature of a user's function to add a
_tracingparameter. However, it does not first check if a parameter with that name already exists. If a user decorates a function that already has a_tracingparameter, the code attempts to add a duplicate. This will causeinspect.signature.replace()to raise aValueErrorbecause duplicate parameter names are not allowed. This error is unhandled and will crash the application when the function is decorated, preventing the application from starting.Suggested fix: Before appending the
_tracingparameter to theparamslist, iterate through the existing parameters to check if one with the name_tracingalready exists. If it does, do not append the new parameter.severity: 0.7, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.