Skip to content
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
This repository was archived by the owner on Nov 16, 2023. It is now read-only.

Could BridgeRuntimeError contain more specific information about the failure? #225

@daholste

Description

@daholste

When calls into the bridge fail, the exception

nimbusml.internal.utils.entrypoints.BridgeRuntimeError: Returned 
code is -1. Check the log for error messages. 

is thrown. The specific exception the bridge encounters (like : *** System.InvalidOperationException: 'Sequence contains no matching element'...) appears only in the stdout

For our scenario, we don't keep a record of the stdout. We do have a try/catch around nimbus calls, and we write any exception nimbus throws to our logs. Because of this practice, our logs only contain BridgeRuntimeError: Returned code is -1 and not more specific debug info

If it would be possible to add more specific info to the BridgeRuntimeError, it would definitely be appreciated in our scenario

Metadata

Metadata

Assignees

Labels

P1Needs to be fixed soon.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions