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

augur curate could have a more helpful error message #1539

Closed
genehack opened this issue Jul 11, 2024 · 0 comments
Closed

augur curate could have a more helpful error message #1539

genehack opened this issue Jul 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@genehack
Copy link
Contributor

Context

When #1530 popped up, it was from a large "curate" pipeline where the parse-genbank-location invocation was in the middle of the stack — and because the error was happening during the output validation, I initially inferred that the problem was in a latter step because I could see the command running and seeming to finish.

This would have been much easier to figure out if the error message included the sub-command name. Currently that message is:

            Something unexpected happened during the augur curate command.
            To report this, please open a new issue including the original command:
                <https://github.com/nextstrain/augur/issues/new/choose>

Description

Add the subcommand name to the error message

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

1 participant