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

Confusing UX of system diagnose command #1069

Closed
sergiimk opened this issue Feb 10, 2025 · 0 comments · Fixed by #1076
Closed

Confusing UX of system diagnose command #1069

sergiimk opened this issue Feb 10, 2025 · 0 comments · Fixed by #1076
Assignees
Labels
bug Something isn't working

Comments

@sergiimk
Copy link
Member

Describe the bug

We currently include running kamu system diagnose as a first post-install step.

When people run it they will see output like:

podman installed... ok
podman can pull images... ok
podman rootless run check... ok
podman volume mounts work... ok
Directory is not kamu workspace

Last line here is confusing to some people as it looks like an error.

Steps To Reproduce

Current Behavior

Expected Behavior

We should improve the message to explain that this is a normal situation, e.g.

podman installed... ok
podman can pull images... ok
podman rootless run check... ok
podman volume mounts work... ok
Directory is not kamu workspace - some checks were skipped
Your installation is healthy

kamu system info

-

Logs

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants