I noticed that whenever an action fails, regardless of the cause, the exception is always silenced and logged with a simple print. I traced the implementation and found that this behaviour is controlled by the following logic:
Is there something I'm missing or is there currently no way to allow the exceptions to propagate normally? Is this a conscious decision? I found that https://github.com/BlueBrain/nexus-forge/pull/281 adds a way to manipulate this behaviour, although only for "debug" purposes and the PR is not merged.
Hello!
Issue
I noticed that whenever an action fails, regardless of the cause, the exception is always silenced and logged with a simple
print. I traced the implementation and found that this behaviour is controlled by the following logic:Current API
The exceptions are only re-raised if the following conditions are met: https://github.com/BlueBrain/nexus-forge/blob/8a900ecf191b14490e7c85254d2c41cf2ec5c8a6/kgforge/core/commons/execution.py#L170-L171
I traced the code and the
catch_exceptionsflag is set toTrueby default: https://github.com/BlueBrain/nexus-forge/blob/8a900ecf191b14490e7c85254d2c41cf2ec5c8a6/kgforge/core/commons/execution.py#L110-L113And there seems to be no way to change it's value, since the public API of the
Storedoes not allow for this argument to be passed, for example: https://github.com/BlueBrain/nexus-forge/blob/8a900ecf191b14490e7c85254d2c41cf2ec5c8a6/kgforge/core/archetypes/store.py#L99-L112Is there something I'm missing or is there currently no way to allow the exceptions to propagate normally? Is this a conscious decision? I found that https://github.com/BlueBrain/nexus-forge/pull/281 adds a way to manipulate this behaviour, although only for "debug" purposes and the PR is not merged.