128+ character long key weird behaviour

[Diliz]

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:

• Key size in dicts seems to be limited to 128 characters go-yaml/yaml#849

• yq/pkg/yqlib/encoder_yaml.go

  Line 11 in f15500b

  yaml "gopkg.in/yaml.v3"

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

[DMaxter]

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]

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]

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]

@mikefarah is there plans to move to goccy?