On Sat, 15 Jul 2017 09:47:40 -0700, jan-olof.hen...@bredband.net wrote:
> On Sat, 15 Jul 2017 07:15:05 -0700, jan-olof.hen...@bredband.net
> wrote:
> > On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> > > I dug at this bug a few months back, but lost my notes on my
> > > findings.
> > >
On Sat, 15 Jul 2017 09:47:40 -0700, jan-olof.hen...@bredband.net wrote:
> On Sat, 15 Jul 2017 07:15:05 -0700, jan-olof.hen...@bredband.net
> wrote:
> > On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> > > I dug at this bug a few months back, but lost my notes on my
> > > findings.
> > >
On Sat, 15 Jul 2017 07:15:05 -0700, jan-olof.hen...@bredband.net wrote:
> On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> > I dug at this bug a few months back, but lost my notes on my
> > findings.
> >
> > As I recall it, the 128655 happens in BOOTSTRAP.nqp in
> > find_best_dispatchee
On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> I dug at this bug a few months back, but lost my notes on my findings.
>
> As I recall it, the 128655 happens in BOOTSTRAP.nqp in
> find_best_dispatchee() the non-native candidate ends up being first in
> the list and that's why it's use