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
Currently the full C++ backtrace is not exposed to the Python wrappers so cannot be parsed, e.g. by BioSimSpace. This is used in various places to provide additional contextual information to the user. Currently the output implies that the functionality can be exposed by calling sire.error.enable_backtrace_exceptions(), but this function doesn't appear to be exposed (yet).
In this case, we only get the last error message. I would like to be able to parse the full trace to see if this was due to the presence of CMAP records, which are currently unsupported, e.g. in relation to this issue.
(The only function that currently appears to be exposed through sire.error is get_last_error_details.)
The text was updated successfully, but these errors were encountered:
Okay, I figured out that this functionality resides in the sire.legacy.Error package, not sire.error as described by the error message above. I'll leave this open for now, although I imagine that it will be resolved as the full 2023 API is fleshed out.
Thanks - yes, I forgot to expose this in sire.error. Yes, this will need fleshing out and fixing before the 2023.1 release.
I made the change to disable backtraces by default as they were a major performance hit in key parts of the code. Ideally I'd like to find a way to automatically enable them when needed... but am not sure this is possible?
Currently the full C++ backtrace is not exposed to the Python wrappers so cannot be parsed, e.g. by BioSimSpace. This is used in various places to provide additional contextual information to the user. Currently the output implies that the functionality can be exposed by calling
sire.error.enable_backtrace_exceptions()
, but this function doesn't appear to be exposed (yet).For example:
In this case, we only get the last error message. I would like to be able to parse the full trace to see if this was due to the presence of CMAP records, which are currently unsupported, e.g. in relation to this issue.
(The only function that currently appears to be exposed through
sire.error
isget_last_error_details
.)The text was updated successfully, but these errors were encountered: