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.

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

128+ character long key weird behaviour #2077

Open
Diliz opened this issue Jun 21, 2024 · 4 comments
Open

128+ character long key weird behaviour #2077

Diliz opened this issue Jun 21, 2024 · 4 comments
Labels

Comments

@Diliz
Copy link

Diliz commented Jun 21, 2024

Describe the bug
When I use 128+ character long keys, it have the following issue.

Note that any how to questions should be posted in the discussion board and not raised as an issue.

Version of yq: v4.34.1
Operating system: on all operating systems
Installed via: binary from release and from source code as well

Input Yaml
data1.yml:

iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii: true
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii: true

Command
The command you ran:

yq '.' data1.yml

Actual behavior

? iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
: true
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii: true

Expected behavior

iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii: true
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii: true

Additional context

What seems to be related:

Maybe I'm wrong, but maybe fully switching to goccy would solve this issue ?

@DMaxter
Copy link

DMaxter commented Jun 23, 2024

This seems a duplicate of #1192 . I have already opened a MR go-yaml/yaml#1031 however, it may need some tests and ensuring backwards compatibility according to the maintainer. If you could help me, maybe we can make it go through

@Diliz
Copy link
Author

Diliz commented Jun 24, 2024

The go-yaml library seems pretty inactive from my point of view, a lot of issues and pull requests opened with no response, never merged, no updates since 2022, other peoples are asking if this project is dead or not since nobody got time to look for issues and prs: go-yaml/yaml#1034

@DMaxter
Copy link

DMaxter commented Jun 25, 2024

The maintainer sometimes answers discussions, maybe we are lucky. In the mean time somebody made a much more complete PR than mine, here is the link so we can keep track of it go-yaml/yaml#1037

@Diliz
Copy link
Author

Diliz commented Jul 3, 2024

@mikefarah is there plans to move to goccy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants