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.

Sign up for GitHub

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

Jump to bottom

[feature] error reporting line number #297

Closed
pjm-tusimple opened this issue Dec 7, 2022 · 2 comments
Closed

[feature] error reporting line number #297

pjm-tusimple opened this issue Dec 7, 2022 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@pjm-tusimple
Copy link

is it possible for the errors to throw a line in the yaml file? Knowing where the exception was thrown will help a lot.
@kvid
Copy link
Collaborator

kvid commented Dec 10, 2022

As far as I know, pyyaml does not support line numbers out of the box, but it might be possible via subclassing. However, an easier approach, is to specify node name and other context to locate the root cause, similar to suggestions in #207.

@pjm-tusimple
Copy link
Author

As far as I know, pyyaml does not support line numbers out of the box, but it might be possible via subclassing. However, an easier approach, is to specify node name and other context to locate the root cause, similar to suggestions in #207.

Yes, it does look similar. Thanks for pointing that out.

@kvid kvid mentioned this issue May 21, 2024
Open
@kvid kvid added the duplicate This issue or pull request already exists label Jul 6, 2024
@kvid kvid closed this as not planned Won't fix, can't repro, duplicate, stale Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kvid @pjm-tusimple