Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upUse UnmarshalStrict for yaml Unmarshalling #4017
Comments
This comment has been minimized.
This comment has been minimized.
|
Related to #1275 and as per IRC, @fabxc said: "I still think we should be using https://github.com/ghodss/yaml " |
This comment has been minimized.
This comment has been minimized.
|
so basically if the other devs agree, replace |
This comment has been minimized.
This comment has been minimized.
|
Does ghodss/yaml handle YAML anchors?
…On Tue, Mar 27, 2018 at 1:34 PM Krasi Georgiev ***@***.***> wrote:
so basically if the other devs agree, replace gopkg.in/yaml with
ghodss/yaml or just add PR to use UnmarshalStrict
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4017 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAANaC_fZRqY8Qy-BQsjqScpOp7xrErQks5tiiOtgaJpZM4S8vs_>
.
|
This comment has been minimized.
This comment has been minimized.
|
It uses the same YAML library but just performs a conversion to JSON, which
is then parsed through the much saner encoding/json.
On Tue, Mar 27, 2018 at 1:43 PM Tobias Schmidt <notifications@github.com>
wrote:
… Does ghodss/yaml handle YAML anchors?
On Tue, Mar 27, 2018 at 1:34 PM Krasi Georgiev ***@***.***>
wrote:
> so basically if the other devs agree, replace gopkg.in/yaml with
> ghodss/yaml or just add PR to use UnmarshalStrict
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#4017 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAANaC_fZRqY8Qy-BQsjqScpOp7xrErQks5tiiOtgaJpZM4S8vs_
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4017 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEuA8uyp0MSzgWjV2kFLGvnAe9cY4pk9ks5tiiXxgaJpZM4S8vs_>
.
|
This comment has been minimized.
This comment has been minimized.
|
I still fail to see the benefits of switching the data to a format that's not the one we're trying to parse. |
brian-brazil
closed this
in
#4033
Apr 4, 2018
jojohappy
referenced this issue
Sep 19, 2018
Merged
Refactor bucket configuration flags for Object Store #500
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
krasi-georgiev commentedMar 27, 2018
The yaml library we are using now support
UnmarshalStrictwhich will return an error for for unknowns, or double definitionshttps://godoc.org/gopkg.in/yaml.v2#UnmarshalStrict
After start using
UnmarshalStrictCheckOverflowwill be no longer neederprometheus/util/yaml/yaml.go
Lines 22 to 31 in dfd6709