-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improve no-debug
option / Improve error messages
#194
Comments
you can turn it around to have a --quiet option to turn off output and a --verbose when you want all details |
On top of whatever changes we make to |
The only extra thing that And, I think for a user this traceback is really useless. If a production software on your machine, like your vscode, produces an error there is no traceback to the typescript blob displayed. Probably just a more or less useful message. This is also what we should aim for. Useful error message from a which a user knows what to do without reading the traceback call 100% agree with @Luthaf that the one you got is really bad. Of course you find it annoying to add alias metatens-models="metatensor-models --debug" |
--debug
optionno-debug
option / Improve error messages
I'm finding it very difficult to work without the
--debug
option. When that option isn't on, you can get very cryptic error messages that would be especially unhelpful for the users (and anyone trying to fix the issues). Take this as an example:where the "hello" key is not present in the
.xyz
file. This results in:which completely hides the error message. Given that some training runs might be very expensive, I think it's a bad idea to have the user re-run it with
--debug
, especially because all issues witheval
only show up at the end of training. I think the easiest solution would be to remove the flagThe text was updated successfully, but these errors were encountered: