-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[core][dashboard] Add repr_name as part of actor state #33555
Conversation
Signed-off-by: rickyyx <[email protected]>
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.
only nit comments
Signed-off-by: rickyyx <[email protected]>
The cpp-tests-asan is flaky due to this: #33475 |
cc @wuisawesome can you review the gcs.proto change |
Adding frontend changes to the PR as well. |
Signed-off-by: rickyyx <[email protected]>
Added frontend changes. |
Signed-off-by: rickyyx <[email protected]>
Signed-off-by: rickyyx <[email protected]>
Some test failiure seems related? |
@@ -30,6 +30,7 @@ export type Actor = { | |||
[key: string]: number; | |||
}; | |||
exitDetail: string; | |||
reprName: string; |
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.
Isn't this supposed to be optional? Or does it always exist?
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.
it will always exist, as an empty string if no repr is defined on the actor.
Signed-off-by: rickyyx <[email protected]>
Lmk when tests pass! |
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail.
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail.
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail. Signed-off-by: bhuang <[email protected]>
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail. Signed-off-by: Jonathan Carter <[email protected]>
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail. Signed-off-by: elliottower <[email protected]>
…3555) This PR adds the actor's repr name as part of the PushTaskReply when executing actor creation task on the executor, and stores it as part of GCS actor table. A couple of places where the repr name will now show up: Task summary (we will likely use "group_name" in the future) Repr name on actor table as another column Repr name on actor detail. Signed-off-by: Jack He <[email protected]>
Why are these changes needed?
If an actor has
__repr__
defined, one could retrieve the actor's repr name in the actor data.Example:
This PR adds the actor's repr name as part of the
PushTaskReply
when executing actor creation task on the executor, and stores it as part of GCS actor table.A couple of places where the repr name will now show up:
Related issue number
Closes #
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.