Fix load error messages not having a stack trace #2508
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While implementing #2507, I forgot the
iterator_inputs=IteratorInputInfo(inputs=0)
which prevented the node from loading. Those were the errors messages that were logged:Pretty useless. No message, not even a stack trace. Turns out that
logger.warning(e.error)
only logs the error message but never the stack trace. So I usedexc_info=e.error
to get the stack trace.The full error with stack trace was this btw: