Ceedling: Fresh install of Ruby 3.2.1 and Ceedling 0.31.1 on Windows 10 fails with weird error.

I installed msys64, and in msys64 installed ruby. I updated to the latest version of gem, then installed ceedling. Once I corrected a PATH issue, I experienced, in sequence:

  1. There was a cheery deprecation warning on each invocation of ceedling related to the “did you mean” system.
  2. After the two-line fix in the Thor gem, I got rid of that only to be faced with File.exists? (and later Dir.exists?) errors any time I tried to use ceedling for anything.
  3. Fixing those (in a surprisingly large number of spaces) led to a final problem I have no idea how to fix. I generated an example project with ceedling example, cded to the generated directory, and got this:
 $ ./ceedling
/usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:432:in `visit_Psych_Nodes_Alias': Alias parsing was not enabled. To enable it, pass `aliases: true` to `Psych::load` or `Psych::safe_load`. (Psych::AliasesNotEnabled)
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:30:in `visit'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:6:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:35:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:340:in `block in register_empty'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:340:in `each'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:340:in `register_empty'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:148:in `visit_Psych_Nodes_Sequence'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:30:in `visit'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:6:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:35:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:347:in `block in revive_hash'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `each'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `each_slice'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `revive_hash'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:169:in `visit_Psych_Nodes_Mapping'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:30:in `visit'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:6:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:35:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:347:in `block in revive_hash'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `each'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `each_slice'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:345:in `revive_hash'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:169:in `visit_Psych_Nodes_Mapping'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:30:in `visit'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:6:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:35:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:320:in `visit_Psych_Nodes_Document'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:30:in `visit'
        from /usr/lib/ruby/3.2.0/psych/visitors/visitor.rb:6:in `accept'
        from /usr/lib/ruby/3.2.0/psych/visitors/to_ruby.rb:35:in `accept'
        from /usr/lib/ruby/3.2.0/psych.rb:334:in `safe_load'
        from /usr/lib/ruby/3.2.0/psych.rb:369:in `load'
        from /usr/lib/ruby/3.2.0/psych.rb:671:in `block in load_file'
        from /usr/lib/ruby/3.2.0/psych.rb:670:in `open'
        from /usr/lib/ruby/3.2.0/psych.rb:670:in `load_file'
        from vendor/ceedling/bin/ceedling:278:in `<main>'

All the usual stuff to help figure out the problem:

  • uname -a → MINGW64_NT-10.0-19045 DESKTOP-HJV57MC 3.4.6.x86_64 2023-02-15 18:03 UTC x86_64 Msys
  • msys installation → msys2-x86_64-20221028.exe
  • ruby --version → ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-cygwin]
  • ceedling version → Ceedling:: 0.31.1 CMock:: 2.5.4 Unity:: 2.5.4 CException:: 1.3.3

Is there a known-good pairing of Ruby version and Ceedling version so I can continue evaluating the suite?

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Comments: 22 (10 by maintainers)

Most upvoted comments

I’m kind of shocked that in a point release there’s major, breaking API changes in Ruby, mind. That’s … serious cringe!