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

No stdout with drip on jruby- #4942

marvinTD opened this issue Jan 5, 2018 · 2 comments

No stdout with drip on jruby- #4942

marvinTD opened this issue Jan 5, 2018 · 2 comments


Copy link

marvinTD commented Jan 5, 2018

jruby -e 'puts "foobar"'

First run when there is no drip jvm started, I see the output. Once it starts using that idle jvm, there's no output. Similar experience when running rspec commands for a pretty barebones rails project.

I'm running rbenv to manage my versions. Additional details below

jruby --version
jruby (2.3.3) 2017-12-07 929fde8 OpenJDK 64-Bit Server VM 24.95-b01 on 1.7.0_95-b00 +jit [linux-x86_64]

Also had the same issue with --dev on. More stuff:

env | grep drip                                                                                                                                                        
env | grep DRIP                                                                                                                                                          
uname -a
Linux machine 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Also tested with openjdk 1.8 and experienced the same issue. Obtained my version of drip using:
curl -L > ~/bin/drip
Looks like it's 0.2.5

Copy link

marvinTD commented Jan 5, 2018


require_relative 'config/application'
require 'rubygems'
require 'bundler'

Bundler.require(:development, :test)

Copy link

headius commented Jan 25, 2018

Likely broken by work to make JDK 9 run better. Specifically, the logic that defaults to using real native stdio rather than JDK stdio.

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

No branches or pull requests

2 participants