Stop swallowing LoadClientAppError's in the SuperNode #6561
Description
Type
Feature
Description
Currently, in run_clientapp.py around line 145, if there is a failure in loading the client app, it swallows the reason and returns a generic error
if isinstance(ex, LoadClientAppError):
reason = "An exception was raised when attempting to load `ClientApp`"
e_code = ErrorCode.LOAD_CLIENT_APP_EXCEPTION
results in
- Round 1 (fit): client=None, ValueError: Message contains an Error (reason: An exception was raised when attempting to loadClientApp). It originated during client-side execution of a message.
When you don't have access to the supernode logs, it makes it impossible to debug this. In this case, the real cause was due to a ModuleNotFoundError for a library that we use in the client app that not all supernodes were updated to include yet. It took much longer than it needed to to debug that since the error was not appropriately bubbled up to the superlink.
Planned Implementation
No response
Additional Context
No response