Charles Oliver Nutter

No longer needed.

The resulting YAML does not appear to verify at any of the online YAML verifiers I tried: https://www.google.com/search?q=yaml+verifier ```yaml --- &1 !ruby/object:Set hash: :one: true :two: true *1: true ```...

@asomov Is this alias output a bug? SnakeYAML Engine emitter: ``` --- &1 !ruby/object:Set hash: :one: true :two: true *1: true ``` libyaml emitter: ``` --- &1 !ruby/object:Set hash: :one:...

> I fed the YAML output from JRuby to MRI's YAML.load without any problems. That may simply be because CRuby uses less-strict YAML 1.1. JRuby's YAML engine is YAML 1.2.

@asomov Thanks for the quick turn around on that fix Andrey! I'm out of town for the weekend but I will confirm this early next week.

@asomov Sorry for the delay, I have confirmed the fix. @mcorino I believe this will be fixed with the patch from @asomov and an additional patch I will work out...

I have filed an issue for the additional Set allocation bug: #8360

Filed https://github.com/ruby/psych/issues/689 for the issue in Psych (needs SnakeYAML-Engine update and release).

@perlpunk So the fix is really that SnakeYAML-Engine should be inserting the space, as shown in the output for ruby33 in https://github.com/jruby/jruby/issues/8352#issuecomment-2395561779 Is that correct? @asomov Perhaps you can coordinate...

@perlpunk Thanks for your help!