-
Notifications
You must be signed in to change notification settings - Fork 63
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
NoMethodError: undefined method `tagged_classes' for Psych:Module on Ruby 2.2.0-preview1 #67
Comments
I met a same probrem on Ruby 2.2.0-dev and 2.2.0-preview1 |
I confirmed that I worked in master branch. I wait for release. |
@dtao Would it be possible for you to release |
Well, great! Yes, I will look into fixing this for Ruby 2.2.0. |
@sferik, what do you get for It's very strange—it seems this error must occur because it thinks the YAML engine is Syck, which it clearly isn't since the exception you're seeing shows that Actually, on that note, what do you get when you just type I've just installed Ruby 2.2.0-preview1 and am having trouble reproducing this. |
@dtao $ ruby -v
ruby 2.2.0preview1 (2014-09-17 trunk 47616) [x86_64-darwin13]
$ gem install safe_yaml
Fetching: safe_yaml-1.0.3.gem (100%)
Successfully installed safe_yaml-1.0.3
1 gem installed
$ irb
irb(main):001:0> require 'safe_yaml'
NoMethodError: undefined method `tagged_classes' for Psych:Module
from /Users/deepj/.gem/ruby/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml/load.rb:43:in `<module:SafeYAML>'
from /Users/deepj/.gem/ruby/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml/load.rb:26:in `<top (required)>'
from /Users/deepj/.rubies/ruby-2.2.0-preview1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Users/deepj/.rubies/ruby-2.2.0-preview1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Users/deepj/.gem/ruby/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml.rb:1:in `<top (required)>'
from /Users/deepj/.rubies/ruby-2.2.0-preview1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
from /Users/deepj/.rubies/ruby-2.2.0-preview1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
from /Users/deepj/.rubies/ruby-2.2.0-preview1/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
from (irb):1
from /Users/deepj/.rubies/ruby-2.2.0-preview1/bin/irb:11:in `<main>'
irb(main):002:0> YAML::VERSION
=> "2.0.6" |
OK, 1.0.4 released today, which should resolve this issue. |
safe_yaml 1.0.3 has some issues with Ruby 2.2.0: dtao/safe_yaml#67
I had this error after I anstalled jekyll and after I installed |
Needed to bump safe_yaml to get fix for dtao/safe_yaml#67
Needed to bump safe_yaml to get fix for dtao/safe_yaml#67
Running ruby 2.2.2p95 on my machine, I was not able to start the application locally: `jekyll --server` would return this error: ``` ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/runner.rb:385:in `block in require_program': program version required (Commander::Runner::CommandError) from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/runner.rb:384:in `each' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/runner.rb:384:in `require_program' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/runner.rb:52:in `run!' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/delegates.rb:8:in `run!' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/commander-4.1.6/lib/commander/import.rb:10:in `block in <top (required)>' ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml/load.rb:43:in `<module:SafeYAML>': undefined method `tagged_classes' for Psych:Module (NoMethodError) from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml/load.rb:26:in `<top (required)>' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml.rb:1:in `require' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/safe_yaml-1.0.3/lib/safe_yaml.rb:1:in `<top (required)>' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/jekyll-1.5.1/lib/jekyll.rb:21:in `require' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/jekyll-1.5.1/lib/jekyll.rb:21:in `<top (required)>' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/jekyll-1.5.1/bin/jekyll:7:in `require' from ~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/jekyll-1.5.1/bin/jekyll:7:in `<top (required)>' from ~/.rbenv/versions/2.2.2/bin/jekyll:23:in `load' from .rbenv/versions/2.2.2/bin/jekyll:23:in `<main>' ``` I found this to be a known issue (see [this](dtao/safe_yaml#67), [this](http://stackoverflow.com/questions/29245100/github-pages-error-running-jekyll-locally) and [this](eclipse-osgi-technology/osgi.enroute.site#8)), and was able to start the application by running `bundle update jekyll`.
A bit has changed - mostly adding the ServiceWatcher class in the hierarchy. safe_yaml needs upgraded because of: dtao/safe_yaml#67
At least, safe_yaml should be 1.0.4 for ruby >= 2.2.0 dtao/safe_yaml#67
Getting this error again with Ruby 2.2.3 and safe_yaml 1.0.3 and running jekyll 2.5.3 |
confirm, bug still appears, |
ixed with 1.0.4 |
Needed to bump safe_yaml to get fix for dtao/safe_yaml#67
I was seeing the problem described in dtao/safe_yaml#67. Upgrading to v1.0.4 fixes this.
Test against ruby-2-1-0-rc1
Closes codeforamerica#58. 2.4.2 is the latest version of ruby [supported by Heroku](https://devcenter.heroku.com/articles/ruby-support#supported-runtimes). The current version is causing deploys of this app to Heroku to fail. This also updates various dependencies in the lockfile using `bundle update #{name}` because of issues related to newer versions of ruby. - `json` [⚠](ruby/json#286) - `safe_yaml` [⚠](dtao/safe_yaml#67) - `webmock` [⚠] (bblimke/webmock#683) For folks that have this checked out locally, I also had to `brew install --force` to force an up to date build of `http_parse.rb`, which was throwing `Symbol not found: _rb_cFixnum`. Finally, this updates petharbor cassette to include URL encoded quotes - this is probably just an internal change to `URI.encode_www_form`.
I do not get this error on Ruby 2.1.2, 2.0.0, or 1.9.3.
The text was updated successfully, but these errors were encountered: