1.7.2 error messages better than 1.6.8

robin2 · February 15, 2013, 10:41am

It seems that JRuby 1.7.2 produces much more informative error messages
when run in scriptingContainer compared with 1.6.8.

I can’t find any explanation for this change. Is it a different default
setting in 1.7.2 and is it possible to get the same behaviour from
1.6.8?

…R

robin2 · February 15, 2013, 1:55pm

Hi Robin

I’m not sure, but I think it might have gotten better thanks to the
improvements Charles made after my bug report:
=> JRUBY-6791

We are much happier with 1.7.2, although I think in certain cases the
stack traces could have more information about the ruby files/positions.

Reto

Am 15.02.2013 um 10:41 schrieb Robin McKay:

robin2 · February 15, 2013, 3:50pm

Thanks Reto,

Looking at the bug report I’m not clear whether you were reporting a
problem in 1.7.0 that worked properly in 1.6.8 or whether you were
commenting on a new feature in 1.7.0.

Can you clarify, please? as I am interested to know if the better error
reports could be obtained in 1.6.8

…R

“Reto Schüttel” [email protected] wrote in post #1097066:
Hi Robin

I’m not sure, but I think it might have gotten better thanks to the
improvements Charles made after my bug report:
=> JRUBY-6791

We are much happier with 1.7.2, although I think in certain cases the
stack traces could have more information about the ruby files/positions.

Reto

Am 15.02.2013 um 10:41 schrieb Robin McKay:

robin2 · February 15, 2013, 4:30pm

Hi Robin

The fixes discussed in this bugreport first appeared in public releases
of the 1.7.x family.

Before that I used the following snipped:

gist.github.com

https://gist.github.com/retoo/89e907998765d6d60f63#file-log_1-6_error-rb

log_1.6_error.rb

  # original log_error method
  def self.log_single_error(exception)
    message = "\n#{exception.class} (#{exception.message}):\n"
    message << exception.annoted_source_code.to_s if exception.respond_to?(:annoted_source_code)
    message << "  " << exception.backtrace.join("\n  ")
    $stderr.puts("#{message}\n\n")
  end


  def self.log_and_exit_if_error

This file has been truncated. show original

Now you can wrap your application with:

log_and_exit_if_error do
app = Application.startup
app.run_whatever
app.shutdown
end

Please Note: This is meant to wrap your whole application lifecycle, it
shouldn’t be needed in more than one place!

But I’m not really sure if this is really the same problem.

Good luck
Reto

Am 15.02.2013 um 15:50 schrieb Robin McKay:

robin2 · February 15, 2013, 4:49pm

Thanks again, Reto

I don’t think that is what I am looking for. As far as I can see the
better error trace in 1.7.2 comes from the Java side when it experiences
an error caused in the JRuby code in scriptingContainer so I don’t think
a JRuby fix will work.

I’m rather hoping one of the JRuby team will comment from their
knowledge of what changes they made between 1.6.8 and 1.7.x

…R

“Reto Schüttel” [email protected] wrote in post #1097098:
Hi Robin

The fixes discussed in this bugreport first appeared in public releases
of the 1.7.x family.