Skip to content
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

vdk-jupyter: job run messages #1908

Merged
merged 16 commits into from
Apr 19, 2023

Conversation

duyguHsnHsn
Copy link
Collaborator

@duyguHsnHsn duyguHsnHsn commented Apr 18, 2023

What:
More informative and easy to understand Run message are introduced:

  • On failure return more detailed error message (where the failure happened, what is the error)
  • On success return "Success"

Here are some screenshots of the newly introduced dialogs:
Screenshot 2023-04-18 at 10 46 03
Screenshot 2023-04-18 at 10 42 31
Screenshot 2023-04-18 at 14 43 25
Screenshot 2023-04-18 at 14 33 12

Why:
Currently, when we run a Job from the VDK menu in Jupyter UI we get an alert with the execution status of the job.
If the users wants to see the actual error, he needs to checks the logs.
This might lead to user confusion and expects users to know that status 0 means success and anything else means error.
With the new implementation it is easier for the user to see the status of the run and the user should not check the logs to see what the error was.

Tests: jest tests

Signed-off-by: Duygu Hasan hduygu@vmware.com

Copy link
Contributor

@yonitoo yonitoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Left a minor comment.

@duyguHsnHsn duyguHsnHsn enabled auto-merge (squash) April 19, 2023 07:17
@duyguHsnHsn duyguHsnHsn merged commit c2aa726 into main Apr 19, 2023
3 of 4 checks passed
@duyguHsnHsn duyguHsnHsn deleted the person/hduygu/jupyter-ui-job-run-messages branch April 19, 2023 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants