Closed matthutchinson closed 6 years ago
Yeah, on Travis it seemed like it couldn't install the json gem. Not sure if that's just Travis or if there are deeper issues. Please LMK if you find problems
Alll green on Travis ! 💚
(apologies for the whitespace changes in my PR, my Vim is set to truncate leading whitespace)
This was fixed by #111
I maintain the lolcommits gem, (which has been using methadone for some years now). I'm working on making it Ruby 2.4.0 friendly. Among other issues I found that methadone was blowing up with this error when calling
go!
:Digging into this.. it turns out that
Logger
in Ruby 2.4.0 has a newinitialize
method, that takes new optional args and calls to set the logger level (defaulting to DEBUG). Here's the new method signature..This would be fine, except that
Methadone::CLILogger
overrides thelevel=
method and expects that a@stderr_logger
variable is set. The fix for this I'd propose, would be to set this instance variable first, before callingsuper(log_device)
. That way, it will always be present, when the RubyLogger
calls to setlevel=
in it's own initializer.I was preparing a fork/PR for this change when I noticed these:
The
sdoc
gem in your gemspec, requires an older version of json (1.8.3) which will not compile under Ruby 2.4 - switching to usesdoc ~> 1.0.0.rc1
(released on Christmas day) solves this (you could use this until the gem author releases a 1.0 final). I checked andrake rdoc
works fine with this.Ruby 2.4 outputs warnings when you use
Fixnum
orBignum
constants causing a bunch of your tests to fail, swapping these out withInteger
solves this (and is backward compatible with older Rubies)This article explains whats new in Ruby 2.4 (including the above changes I mentioned).
I'll issue a PR in a few secs, hopefully it will pass Travis for all Rubies...