-
Notifications
You must be signed in to change notification settings - Fork 518
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
Plain equal sign (=) as node content results in an error #89
Comments
we are hitting this too |
workaround yaml/pyyaml#89 Allow `-` as a filename to read from stdin
Since the bug is that
You can isolate the fix to your own loader too:
|
Includes pyaml hack for parsing bug, see: yaml/pyyaml#635 yaml/pyyaml#89 prometheus-operator/prometheus-operator#4955
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Remarshal doesn’t seem to be maintained anymore. It is also affected by upstream bugs like yaml/pyyaml#89 which affects e.g. prometheus-operator CRDs.
Has someone bisected this issue yet and can share a range of versions which are affected (probably open end because the issues isn't fixed yet)? I see this issue is being referenced as upstream issue by a lot of bugs, among them some Helm Charts rolled out with Ansible. The version range helps in mitigating downstream issues - a fix is very welcome as well of course. I guess they affected pyyaml version has made it in a lot of downstream tools. In there environment it's impossible or hard to apply the workaround (thanks) without ugly patches. |
See yaml/pyyaml#89 for more info
See yaml/pyyaml#89 for more info
See yaml/pyyaml#89 for more info
…ing an item that is a plain `=` (equal sign), see yaml/pyyaml#89
Running this code:
Gives this error:
yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:value' in "<string>", line 1, column 1: = ^
There was, in the past, a ticket against PyYAML; but I suspect it got lost in a migration. See https://web.archive.org/web/20100707124750/http://pyyaml.org:80/ticket/140
The SnakeYAML people had a discussion of correct behaviour in this sort of situation at https://code.google.com/archive/p/snakeyaml/issues/192, the conclusion of which was (loosely paraphrased) "an equals sign is unambiguously a string value, and so doesn't need quoting, provided that you ignore the Value Key Language-Independent Type facility which never really worked anyway."
The equivalent fix to the one in SnakeYAML would be to remove the following lines from resolver.py:
I've also found it is possible to work around the issue with the following:
The text was updated successfully, but these errors were encountered: