uninitialized constant SafeYAML::Parse::Date::DateTime (NameError) about safe_yaml

[javierbertoli]

As a quick fix, changing here

    class Date
        # This one's easy enough :)

to

    class Date
        require 'time'
        # This one's easy enough :)

seems to fix it

[electriquo]

i was having the same problem when upgrading from ruby version 2.4.2 to 2.5.0

$ ruby --version
ruby 2.5.0p0 (2017-12-25 revision 61468)
$ cat Gemfile.lock | grep -i 'test-kitchen ([0-9]'
    test-kitchen (1.19.2)

applying @javierbertoli quick fix resolved my pain.
wonder why i just got this error when the initial issue date it set back to Oct 18, 2015 and @javierbertoli resolution was not pushed to the upstream or any other suitable fix...

any idea?

[victort]

i'm having this error occur on debian/buster

$ kitchen
/var/lib/gems/2.3.0/gems/safe_yaml-1.0.4/lib/safe_yaml/parse/date.rb:22:in `<class:Date>': uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)
Did you mean?  SafeYAML::Parse::Date::DATE_MATCHER
	from /var/lib/gems/2.3.0/gems/safe_yaml-1.0.4/lib/safe_yaml/parse/date.rb:3:in `<class:Parse>'
	from /var/lib/gems/2.3.0/gems/safe_yaml-1.0.4/lib/safe_yaml/parse/date.rb:2:in `<module:SafeYAML>'
	from /var/lib/gems/2.3.0/gems/safe_yaml-1.0.4/lib/safe_yaml/parse/date.rb:1:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/safe_yaml-1.0.4/lib/safe_yaml/load.rb:14:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `rescue in require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
	from /var/lib/gems/2.3.0/gems/test-kitchen-1.19.2/lib/kitchen/loader/yaml.rb:21:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/test-kitchen-1.19.2/lib/kitchen.rb:42:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/test-kitchen-1.19.2/lib/kitchen/cli.rb:21:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/test-kitchen-1.19.2/bin/kitchen:10:in `<top (required)>'
	from /usr/local/bin/kitchen:22:in `load'
	from /usr/local/bin/kitchen:22:in `<main>'

$ ruby --version
ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]
$ gem list --local | egrep "test-kitchen|safe_yaml"
safe_yaml (1.0.4)
test-kitchen (1.19.2)```

[victort]

confirmed, @javierbertoli
that Works For Me™

thanks!

[silverhammermba]

@y0y0z My only guess is that somebody somewhere was doing a require 'date' or require 'time' which pulls in the DateTime class and this was happening before safe yaml got invoked.

Top level constant names are a nasty little bit of global state in Ruby...