Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better OmegaConf error reporting #798

Open
bwsw opened this issue Jun 27, 2024 · 0 comments
Open

Better OmegaConf error reporting #798

bwsw opened this issue Jun 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bwsw
Copy link
Contributor

bwsw commented Jun 27, 2024

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.

image

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.

@bwsw bwsw added the enhancement New feature or request label Jun 27, 2024
@bwsw bwsw added this to the 0.4.2 milestone Jun 27, 2024
@bwsw bwsw removed this from the 0.5.0 milestone Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant