-
Notifications
You must be signed in to change notification settings - Fork 1
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
Enhanced translator error messages. #297
Comments
@marc-white I'm wrapping up the translator errors now - PR should be in ASAP. |
Once that's in, for speed I won't bother with a new draft release - I'll just do a local install of the updated |
@charles-turner-1 how are you traveling? Can I help at all? |
See #298 - got hung up trying to move all the error handling into a single decorator - struggling to get it to grab |
Closed by #298. |
Is your feature request related to a problem? Please describe.
#279 and #290 : when builds fail due to translator errors, it can be difficult to reliably identify which translator failed. This can be an issue at catalog build time if NCI datastores change.
Describe the feature you'd like
Translators to provide a class name when failing such that debugging translator failures is more straightforward.
Describe alternatives you've considered
<Replace this text with a clear and concise description of any alternative solutions or features you've considered.>
Additional context
The text was updated successfully, but these errors were encountered: