Skip to content
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

Several warnings in output #155

Closed
eproxus opened this issue Nov 21, 2013 · 3 comments
Closed

Several warnings in output #155

eproxus opened this issue Nov 21, 2013 · 3 comments

Comments

@eproxus
Copy link

eproxus commented Nov 21, 2013

When creating a gist (both with and without -p), several warnings are printed out:

$ gist -p mysql/attributes/server.rb
/usr/local/bin/gist:937: warning: already initialized constant JSON::NaN
/Users/user/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/json/common.rb:99: warning: previous definition of NaN was here
/usr/local/bin/gist:939: warning: already initialized constant JSON::Infinity
/Users/user/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/json/common.rb:101: warning: previous definition of Infinity was here
/usr/local/bin/gist:941: warning: already initialized constant JSON::MinusInfinity
/Users/user/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/json/common.rb:103: warning: previous definition of MinusInfinity was here
/usr/local/bin/gist:960: warning: already initialized constant JSON::UnparserError
/Users/user/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/json/common.rb:128: warning: previous definition of UnparserError was here
https://gist.github.com/xxx

The gist creation still works.

@ConradIrwin
Copy link
Collaborator

@eproxus It looks like JSON is being automatically loaded into Ruby when you run gist. The warnings are harmless, but still should not happen.

Do you have anything configured in the environment variable $RUBYOPT?

@eproxus
Copy link
Author

eproxus commented Jan 14, 2014

No, it's empty.

@jhirbour
Copy link

jhirbour commented Feb 5, 2014

I was having the same issue when I was using the homebrew version. When I installed them gem directly the error messages went away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants