Came across the issue when testing the shell-on-error implementation.
If the debugger returns the ErrDebugExit error, the error string gets wrapped in the main solve goroutine after the gRPC call. Error check on ErrDebugExit fails afterwards because we lose the original error from the gRPC call.
This PR overrides the solve error to the original error, so the error check on ErrDebugExit succeeds.
Came across the issue when testing the
shell-on-errorimplementation.If the debugger returns the
ErrDebugExiterror, the error string gets wrapped in the main solve goroutine after the gRPC call. Error check onErrDebugExitfails afterwards because we lose the original error from the gRPC call.This PR overrides the solve error to the original error, so the error check on
ErrDebugExitsucceeds.