You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, when OmegaConf contains incorrect keys, the system results in an error, including a stack trace, exception, and actual error. We do not need to display the service information except the actual problem.
The actual report can be like:
[ERROR] Configuration parsing error: the key local is not known in the object NvInferDetector.
If we can display a YAML block containing the error, it would be awesome.
The text was updated successfully, but these errors were encountered:
Now, when OmegaConf contains incorrect keys, the system results in an error, including a stack trace, exception, and actual error. We do not need to display the service information except the actual problem.
The actual report can be like:
[ERROR] Configuration parsing error: the key
local
is not known in the objectNvInferDetector
.If we can display a YAML block containing the error, it would be awesome.
The text was updated successfully, but these errors were encountered: