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

Parsers: add exception title to ERROR_UNEXPECTED_PARSER_EXCEPTION #793

Merged
merged 1 commit into from
Mar 8, 2022

Conversation

sphuber
Copy link
Contributor

@sphuber sphuber commented Mar 5, 2022

Fixes #791

The exact exception and its stack trace was already added as a log to
the relevant process node, however, most often only the exit message is
shown. Currently this would only show the base message that an
unexpected exception occurred which is not very informative and one
would have to run other commands to find out more. By adding the
exception title in the exit message itself, one has more information
directly.

The exact exception and its stack trace was already added as a log to
the relevant process node, however, most often only the exit message is
shown. Currently this would only show the base message that an
unexpected exception occurred which is not very informative and one
would have to run other commands to find out more. By adding the
exception title in the exit message itself, one has more information
directly.
@sphuber sphuber requested review from mbercx and unkcpz March 5, 2022 15:09
Copy link
Member

@mbercx mbercx left a comment

Choose a reason for hiding this comment

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

Thanks @sphuber! I didn't field test this, but changes look pretty straightforward. 👍

This is good to go for me, but perhaps @unkcpz would still like to take a look since he opened the issue?

@sphuber
Copy link
Contributor Author

sphuber commented Mar 8, 2022

This is good to go for me, but perhaps @unkcpz would still like to take a look since he opened the issue?

I asked him to open it, so I think it is fine to merge.

@sphuber sphuber merged commit 0c8a611 into develop Mar 8, 2022
@sphuber sphuber deleted the fix/791/exit-code-350-include-exception-message branch March 8, 2022 08:25
mbercx pushed a commit to mbercx/aiida-quantumespresso that referenced this pull request Mar 17, 2022
…iidateam#793)

The exact exception and its stack trace was already added as a log to
the relevant process node, however, most often only the exit message is
shown. Currently this would only show the base message that an
unexpected exception occurred which is not very informative and one
would have to run other commands to find out more. By adding the
exception title in the exit message itself, one has more information
directly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parsers: improve the 350 exception message to include the title of the exception
2 participants