Karol Bucek
Karol Bucek
seems that, for whatever reason, this failed the CI build completely, any chance to look into that?
as noted previously, this isnt a good work-around https://github.com/jruby/warbler/issues/432#issuecomment-404799363 ... likely a JRuby 9.2 bug
seems like a JRuby compatibility issue with IBM Java ... if anyone can confirm its still present on latest or JRubies (1.7.26/9.1.1.0) it would be worth looking into.
yes, please possibly add a test regardless of CI
jruby-jars 9.2.0 seems to be having issues with Bundler, so likely this would be a duplicate of https://github.com/jruby/warbler/issues/432 message should confirm, also degrading jruby-jars to `< 9.2` could confirm whether...
Ruby threads use Java threads the problem is the way they're used in Rails - simply not "thread-safe" code. For Trinidad/JRuby-Rack there would be a better solution to this leveraging...
it dead locks - that's all there is (for now) ... I have not looked deeper and I have not tracked if anyone else did ... sorry
seems to have been handled at https://github.com/jruby/jruby-rack/pull/214 and is now available in 1.1.22
@JasonLunn unfortunately its not release ready - quite far from it. that one features might be semi-complete ... although only on my fork. am also thinking about forms of monetization...
as I said its likely quite broken, you're on your own here - the ext parts are a WiP. might drop a pre-release in a week or two.