Skip to content

Show CLI errors generated by exp show #4062

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
merged 2 commits into from
Jun 12, 2023
Merged

Show CLI errors generated by exp show #4062

merged 2 commits into from
Jun 12, 2023

Conversation

mattseddon
Copy link
Contributor

@mattseddon mattseddon commented Jun 8, 2023

1/3 main <- this <- #4075 <- #4077

Related to iterative/dvc#9565

This issue was reported on Discord today: https://discord.com/channels/485586884165107732/842220310585147452/1116030033480392836

The user seems to be experiencing a CLI error which means that their experiments appear as if they have no data (technically correct). That means that any attempt to open the experiments webview will result in the setup page being shown.

Now when the CLI throws an error we will let the user open the experiments webview and show an error state. The error state will be shown any time the webview is open and the CLI throws an error. IMO this is more useful than adding an experiments error state to the setup webview (I did originally add both but changed my mind).

Demo

Screen.Recording.2023-06-08.at.1.20.18.pm.mov

Note: A user will still see this if they purposefully go to the setup page when there is a CLI error.

image

This is an edge case though as I believe the most confusing thing was the redirect to setup when there was an error. If we run into this again then I'll add an error state to the Experiments section of the setup page.

@mattseddon mattseddon added the product PR that affects product label Jun 8, 2023
@mattseddon mattseddon self-assigned this Jun 8, 2023
@mattseddon mattseddon force-pushed the show-exp-show-error branch 2 times, most recently from 405bfc7 to 9044141 Compare June 8, 2023 04:21
@mattseddon mattseddon marked this pull request as ready for review June 8, 2023 04:36
@mattseddon mattseddon requested review from sroy3 and julieg18 as code owners June 8, 2023 04:36
@mattseddon mattseddon requested a review from shcheklein June 8, 2023 04:36
Copy link
Contributor

@julieg18 julieg18 left a comment

Choose a reason for hiding this comment

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

Great work!

The test coverage on the diff in this pull request is 80.3% (85% is the threshold).
This pull request will bring the total coverage in the repository to 95.1% (-0.1% change).

Is this expected?

@mattseddon mattseddon enabled auto-merge (squash) June 12, 2023 18:47
@codeclimate
Copy link

codeclimate bot commented Jun 12, 2023

Code Climate has analyzed commit efea638 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 80.3% (85% is the threshold).

This pull request will bring the total coverage in the repository to 95.1% (-0.1% change).

View more on Code Climate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product PR that affects product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants