You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Readers/transformers/writers can have unexpected errors, e.g. because of malformed data or missed edge cases. We should probably have a more "forgiving" strategy that allows not completely failing on generic errors, but still preserving any context-aware or useful errors that could help with debugging/fixing the input data.
Example:
This line is quite error prone if something is malformed, makes me wonder if we should have a global try/except so the datastream.process() wouldnt fail 🤔
Some grants failed to be processed by the datastreams code. We need to add error logging logic to find these and address separately (in invenio-vocabularies)
Readers/transformers/writers can have unexpected errors, e.g. because of malformed data or missed edge cases. We should probably have a more "forgiving" strategy that allows not completely failing on generic errors, but still preserving any context-aware or useful errors that could help with debugging/fixing the input data.
Example:
This line is quite error prone if something is malformed, makes me wonder if we should have a global try/except so the
datastream.process()
wouldnt fail 🤔Originally posted by @ppanero in #167 (comment)
The text was updated successfully, but these errors were encountered: