-
Notifications
You must be signed in to change notification settings - Fork 1
feat(core): enable actuators and operators to use Rich progress indicators #248
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
Conversation
Was printing first entity from samplestore because once this was relevant to the space - however this is no longer true and it could be anything.
…tors This allows actuators/explore operators that have steps that take significant time to execute to clearly notify users on their state, rather than relying on e.g. INFO logs which may be buried in other log output. Spinners and ProgressBars are supported in this initial implementation. Also unify all rich.Console related functionality for explore operations in a module (console_output.py)
random walk now outputs a progress bar as it processes entities - the bar also includes (number completed entities/total) and the elapsed time.
Actuator now outputs progress indicators using new RichConsoleQueue when waiting for an environment to be free; creating vllm deployment; waiting for it to be ready. Also pass requestid to create_environment so it can be referenced in the progress indicators
The code did not check if the port-forward process had exited, only if Popen raised an Exception. There are situations where the port-forward command could immediately fail that would not raise an exception. As it was the code would continue on as if the port-forward was up
|
Checks Summary Last run: 2025-11-26T16:31:38.177Z Code Risk Analyzer vulnerability scan found 2 vulnerabilities:
|
|
@christian-pinto can you check the changes to vllm_performance and the progress elements? |
christian-pinto
left a comment
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.
Let me run it now
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Outdated
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Outdated
Show resolved
Hide resolved
Looks good. THe only thing that is odd is that when a request starts running it disappears from the list. Is this intentional? |
Co-authored-by: Christian Pinto <christian.pinto@ibm.com> Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Yes because I thought the vllm bench serve output is there so wasn't necessary - can easily add an indicator like for when the test is running? Edit: I added it |
So an progress entry for a request is always present while running test-deployment-v1
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
|
This is what I see now experiment.mp4Three experiments submitted (BS==3) but only one is shown |
christian-pinto
left a comment
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 see the problem now. All the prints are using the definition as id. When entities require the same deployment they will all have use the same identifier for the prints.
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
plugins/actuators/vllm_performance/ado_actuators/vllm_performance/experiment_executor.py
Show resolved
Hide resolved
Filtering on ConstitutiveProperty type when that type is not the type of the field since intro of ConstitutivePropertyDescriptor. Use consitutive_property_values to avoid having to filter.
Co-authored-by: Alessandro Pomponio <10339005+AlessandroPomponio@users.noreply.github.com> Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Co-authored-by: Alessandro Pomponio <10339005+AlessandroPomponio@users.noreply.github.com> Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
…nce/experiment_executor.py Co-authored-by: Christian Pinto <christian.pinto@ibm.com> Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
AlessandroPomponio
left a comment
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.
LGTM thanks
christian-pinto
left a comment
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.
LGTM Thanks
All requests resolved
The PR also
progress_example.mp4