org.jruby.exceptions.ThreadKill: null

[kenips]

Just using debugger in JRuby and this shows as soon as I enter any command after it stops.

LoadError: load error: /usr/local/opt/rbenv/versions/jruby-1.7.4/gems/coderay-1.0.9/lib/coderay/scanner -- org.jruby.exceptions.ThreadKill: null from /usr/local/opt/rbenv/versions/jruby-1.7.4/gems/coderay-1.0.9/lib/coderay.rb:270:in `scanner'

[korny]

No idea what's happening there. Can you investigate what exactly is causing the problem?

[Byclosure]

The same error happens to me (no idea about the cause or solution for that also :/).

[korny]

Maybe it doesn't like autoload?

Can you provide a minimal test case for this so I can replicate it on my system?

[korny]

Can't replicate without more information. jruby-debug works for me.

[justincampbell]

This is also happening for me. I'm using Cucumber inside of Guard, on JRuby. I will try to reproduce in a new repo if I have time.

[kenips]

Using Guard here as well actually. No cucumber, just RSpec and Guard.

[adriancb]

+1 - Guard + RSpec on:

jruby 1.7.3 (1.9.3p385) 2013-02-21 dac429b on Java HotSpot(TM) 64-Bit Server VM 1.6.0_51-b11-457-11M4509 [darwin-x86_64]

[korny]

@kenips, @adriancb: Can you make a minimal test case, eg. in a new separate repo? I'd really like to debug this, but I still can't replicate the error.

[adriancb]

@korny - will do. It'll probably be over the next week or so. Thanks for looking into it.

[perlun]

Also seeing this. I strongly suspect we should try to fix that test case... @korny, have you tried to just run guard init using jruby? And then run guard without parameters, and pressing Enter (or writing all).

[djmaze]

Had the same problem. Somehow my terminal must have been messed up. After closing and opening a new terminal, the error did not come up again (yet).