-
Notifications
You must be signed in to change notification settings - Fork 696
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
[flyteagent] Add Output Prefix to GetTaskRequest #6265
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Future-Outlier <[email protected]>
Code Review Agent Run #89414cActionable Suggestions - 2
Review Details
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6265 +/- ##
==========================================
- Coverage 36.86% 36.86% -0.01%
==========================================
Files 1318 1318
Lines 134767 134788 +21
==========================================
+ Hits 49685 49686 +1
- Misses 80752 80770 +18
- Partials 4330 4332 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Changelist by BitoThis pull request implements the following key changes.
|
* @memberof flyteidl.admin.GetTaskRequest | ||
* @instance | ||
*/ | ||
GetTaskRequest.prototype.outputPrefix = ""; |
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.
Consider initializing outputPrefix
with null
instead of an empty string since the property is defined as nullable in the JSDoc comment. This would make the implementation consistent with the type definition.
Code suggestion
Check the AI-generated fix before applying
GetTaskRequest.prototype.outputPrefix = ""; | |
GetTaskRequest.prototype.outputPrefix = null; |
Code Review Run #89414c
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
/** GetTaskRequest outputPrefix */ | ||
outputPrefix?: (string|null); |
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.
Consider making the outputPrefix
property required in IGetTaskRequest
interface since it appears to be non-optional in the class implementation. The interface shows it as optional with ?
but the class property is defined without optional modifier.
Code suggestion
Check the AI-generated fix before applying
/** GetTaskRequest outputPrefix */ | |
outputPrefix?: (string|null); | |
/** GetTaskRequest outputPrefix */ | |
outputPrefix: string; |
Code Review Run #89414c
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
Tracking issue
#3936
Why are the changes needed?
What changes were proposed in this pull request?
How was this patch tested?
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This PR introduces a new output_prefix field to the GetTaskRequest message in the Flyte agent protocol, enabling specification of task output data locations. The implementation spans multiple language implementations including TypeScript, Go, Python, and Rust, with corresponding protobuf definition updates. The changes enhance task output handling by allowing clients to define output destinations through the new field.Unit tests added: False
Estimated effort to review (1-5, lower is better): 3