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

stack trace is confusing #37

Open
bacalec opened this issue Sep 15, 2023 · 0 comments
Open

stack trace is confusing #37

bacalec opened this issue Sep 15, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@bacalec
Copy link

bacalec commented Sep 15, 2023

Bossman failed and output started with a long stack trace that included non relevant diagnostic and suggestion:
"│ 22 │ raise BossmanError("Repository not initialized or needs migration, please run `bossm │"

Output ended with the error message:
"error: [Errno 11] Resource temporarily unavailable: '.bossmancache'"

I didn't notice it but I noticed that there was a bossman process still running. After this process was finished, i was able to run bossman.

It would be more clear if stack trace was not displayed with the verbosity by default.

@ynohat ynohat added the enhancement New feature or request label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants