-
Notifications
You must be signed in to change notification settings - Fork 141
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
Error Reference cannot tell the specific line on the spec #452
Comments
Original discussion is from #451.
|
On Wed, Aug 30, 2017 at 03:20:55AM +0000, 梁辰晔 (Liang Chenye) wrote:
Now, we can only tell the markdown place. For some config items
which include several 'MUST/SHOULD', it might be difficult for user
to find out the detailed error.
This is really an argument to re-open opencontainers/runtime-spec#634,
which I'd requested last month [1]. It's not a runtime-tools issue,
it's a runtime-spec issue.
On Wed, Aug 30, 2017 at 03:22:59AM +0000, 梁辰晔 (Liang Chenye) wrote:
For poststart and poststop the requirement is indirect, via this and
this. Perhaps we should expand Error.Reference to an array of
strings so we can represent trails like that?
This is the runtime-tools issue I was trying to get at. An example
that is completely separate from opencontainers/runtime-spec#634 is
the environment-variable check [2], where the violated requirement is
in POSIX which is included via a spec condition. I think there are a
few checks like that where the violation requires references to
several locations, and to support those we'd want:
References []string
instead of our current [3]:
Reference string
[1]: opencontainers/runtime-spec#634 (comment)
[2]: #451 (comment)
[3]: https://github.com/opencontainers/runtime-tools/blob/12b47b989d39e3e750fff2631e929f455b6eef3f/error/rfc2199.go#L49
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now, we can only tell the markdown place. For some config items which include several 'MUST/SHOULD', it might be difficult for user to find out the detailed error.
The text was updated successfully, but these errors were encountered: