Skip to content

Issues: kubernetes-sigs/yaml

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

8 Open 49 Closed
8 Open 49 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

panic while unmarshall (go-yaml/yaml issue #1050)
#117 opened Sep 28, 2024 by pohly
yaml.Marshal() can not be forced to leave strings quoted
#108 opened Feb 29, 2024 by spkane
1
8
Possibility to use YAML anchors lost from v1.3.0 to v1.4.0
#107 opened Feb 29, 2024 by dmaphy
4
Richer typed errors lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#67 opened Nov 5, 2021 by smlx
6
Unmarshal loses type information kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#45 opened Nov 19, 2020 by philomory
1
28
Int overflow on 32 bits arches lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#23 opened Jun 29, 2019 by eclipseo
8
Should this library move to yaml.v3 kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#18 opened Apr 26, 2019 by errordeveloper
1
6
Strict unmarshalling should be case-sensitive kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#15 opened Apr 26, 2019 by martina-if
1
@neolit123
20
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.