On Tuesday 14 March 2006 08:04 pm, Charles O Nutter wrote:
Still not there yet. I've got a java proxy that is getting an "Wrong # of
arguments". I'll dig into it
David
> Ok, I'll be watching for it!
>
> On 3/14/06, David Corbin <[EMAIL PROTECTED]> wrote:
> > On Monday 13 March 2006 10:22 p
Ok, I'll be watching for it!On 3/14/06, David Corbin <[EMAIL PROTECTED]> wrote:
On Monday 13 March 2006 10:22 pm, Charles O Nutter wrote:> Try it now; it was almost the same issue that was causing some other> flow-control stuff to blow up. I believe it is occurring when you have a> return cross fra
On Monday 13 March 2006 10:22 pm, Charles O Nutter wrote:
> Try it now; it was almost the same issue that was causing some other
> flow-control stuff to blow up. I believe it is occurring when you have a
> return cross frame boundaries, as with a block call that does return and
> runs in a differen
Try it now; it was almost the same issue that was causing some other flow-control stuff to blow up. I believe it is occurring when you have a return cross frame boundaries, as with a block call that does return and runs in a different EvalState. I'm continuing to isolate it to a specific case that
Excellent, I'll have a look!On 3/13/06, David Corbin <[EMAIL PROTECTED]> wrote:
Finally! This shows the NPE. Sorry it took so long, but I had a lot of Javacode in the original failure, and it took me a while to figure out what wasreally causing the issue.cutrequire 'test/unit'
class Conte
Finally! This shows the NPE. Sorry it took so long, but I had a lot of Java
code in the original failure, and it took me a while to figure out what was
really causing the issue.
cut
require 'test/unit'
class ContextStack
def inContext &proc
begin
proc.call
ensure
e
On Thursday 09 March 2006 02:09 pm, Charles O Nutter wrote:
> The fix is in! I am still working on designing good test cases for it,
> however. Let me know how it goes.
Still no luck. And unfortunately, I can't work on it this weekend due to
networking problems. But I'll continue to try to shri
The fix is in! I am still working on designing good test cases for it, however. Let me know how it goes.On 3/9/06, Charles O Nutter <
[EMAIL PROTECTED]> wrote:Don't worry about it, I've got a patch coming. I think I found the issue...there were a number of places where currentException wasn't being
Don't worry about it, I've got a patch coming. I think I found the issue...there were a number of places where currentException wasn't being set that broke retry and break when en ensure was present. I've got a couple cases, and will be committing in a minute.
On 3/9/06, David Corbin <[EMAIL PROTEC
I understand. I've narrowed it down some, but have a ways to go.
Unfortunately, so far, my working is dependent on our Java code, which makes
it that much more annoying.
David
On Thursday 09 March 2006 12:21, Charles O Nutter wrote:
> Ok ok, I'll check again. If you can narrow it down at all
Ok ok, I'll check again. If you can narrow it down at all it would be great...I believe I can fix it for you, but having a test case to commit would make me feel better about it.On 3/8/06,
David Corbin <[EMAIL PROTECTED]> wrote:
On Wednesday 08 March 2006 14:18, Charles O Nutter wrote:> Ok, it loo
On Wednesday 08 March 2006 14:18, Charles O Nutter wrote:
> Ok, it looks like some of the "branch-only" changes I started making to the
> evaluator are also required for HEAD to work 100% with the new exception
> subsystem. I merged the appropriate changes to HEAD. I would wager this
> will fix you
Ok, it looks like some of the "branch-only" changes I started making to the evaluator are also required for HEAD to work 100% with the new exception subsystem. I merged the appropriate changes to HEAD. I would wager this will fix your issue, but give it a quick run and let me know what you see.
On
I think I can tackle this one. I'll take a look this evening.
On 3/7/06, David Corbin <[EMAIL PROTECTED]> wrote:
> Digging in the problem is that the EvaluateState#currentException is null, and
> the "ExceptionRethrower" tries to throw a null. I've not been able to
> produce a small test-case yet
Digging in the problem is that the EvaluateState#currentException is null, and
the "ExceptionRethrower" tries to throw a null. I've not been able to
produce a small test-case yet, so I was wonderinf if anyone could give some
pointers about what to look at in the debugger.
I'm trying to call a
I'm getting this after my java code throws an exception. I haven't got it
boiled down to Ia simple demo, but I thought this might help in the mean
time
NativeException: java.lang.NullPointerException: null
org.jruby.evaluator.EvaluationState$ExceptionRethrower.execute(EvaluationState
16 matches
Mail list logo
