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
When we create VRS IDs or query metakb, we need to have error handling that describes the problem (network error, translation error, no matches found, etc). In some cases like within annotate_all, there can be non-descript messages outputted in the command line.
is it good enough for an error? Do we just have to redirect them to the logs file everytime?
The text was updated successfully, but these errors were encountered:
Still might need more work, as some logs can be misleading and we may want to suppress them: below the main problem is that the validation error is occurring but the traceback mentions a "timestamp_str" KeyError.
quinnwai
changed the title
feature/error-handling
feature/specialized-error-handling
Apr 9, 2024
When we create VRS IDs or query metakb, we need to have error handling that describes the problem (network error, translation error, no matches found, etc). In some cases like within annotate_all, there can be non-descript messages outputted in the command line.
is it good enough for an error? Do we just have to redirect them to the logs file everytime?
The text was updated successfully, but these errors were encountered: