Details

    • Number of attachments :
      0

      Description

      When the NG server is not up, jruby --ng produces only the following error:

      ~/projects/jruby $ jruby --ng -e 1
      connect: Connection refused
      

      This error gives no indication as to the actual cause of the problem. If instead it reported "connect to Nailgun server: Connection refused" there would be less chance of confusing this error for a Ruby error.

      This actually confused the Travis CI folks into thinking there was a network connectivity problem or JRuby bug affecting RubyGems or Bundler, when in actuality the problem was caused by RVM using Nailgun and (probably) not having the server initialized before the command launched. A better error message would have shown the problem very quickly.

      We should fix this in the launcher, and possibly in our copy of ng client source. If we do the latter, we should also attempt to submit a patch back to the ng authors.

        Activity

        Show
        Hiro Asari added a comment - Fixed in: jruby-launcher (1.0.9 or so) https://github.com/jruby/jruby-launcher/commit/ccd1ebb7236ab80d39949fc01c32d59810b1c97c master https://github.com/jruby/jruby/commit/3efc165e4e59293f86d546a35543237ced84e75f jruby-1_6 https://github.com/jruby/jruby/commit/4eefc7d53862d7b94b8c6fe2cb3bca7ee7ea1ad9

          People

          • Assignee:
            Hiro Asari
            Reporter:
            Charles Oliver Nutter
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: