-
Notifications
You must be signed in to change notification settings - Fork 622
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Extend context and name propagation in errors (#5396)
Add error context related to particular operator during graph construction and pipeline build: * error propagation in Pipeline::Build() is adjusted * Python calls to backend: Pipeline::AddOperator now augment errors with context. * OpSpec building errors propagate the proper operator name. Replace most of the SchemaName() occurrences that were used to indicate the name operator with the fully formatted operator name in the correct API. Make sure that the naming information is added as soon as possible, so it can be accessed in partially constructed schema with the correct values present. Note: This PR mostly adds the context like: ``` Error in <device> operator `nvidia.dali.fn.operator_name`, which was used in the pipeline definition with the following traceback: <traceback> encountered: <Original error message> ``` to places where it was not previously used, but we are processing a single operator. Error messages are adjusted to show the user-facing input/output/argument name (in uniform way) rather than the internal one. Otherwise the checks and messages are preserved. The types of error messages are not adjusted. Signed-off-by: Krzysztof Lecki <[email protected]>
- Loading branch information
Showing
21 changed files
with
295 additions
and
197 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.