in reply to Re: Discrepancy in reap notification message
in thread Discrepancy in reap notification message

Hi,

So what is supposed to happen, who is supposed to get the notification, root, OP or consider-er?

  • Comment on Re^2: Discrepancy in reap notification message

Replies are listed 'Best First'.
Re^3: Discrepancy in reap notification message
by jdporter (Paladin) on Apr 28, 2017 at 02:10 UTC

    I'm asking people who vote 'reap' and find that they have cast the deciding vote -- the one which actually triggers the reap -- to take note of what notification they see in their cb nodelet, if any.

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

        Perfect. I think we can call this issue "closed". :-) Thanks, beech and everyone!

        I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

      I just got this message - this is exactly what it looks like, including the "no such node" message and link:

      You said "Reaped node at: [id://1204763] because [hippo]: Duplicate of [1204762]" to [no such node, ID 113]

      Update: On a different reaping, after the above, I got: You said "Reaped node at: ..." to root

        That's so odd, I must conclude that it was due to some transient database flakiness.

        I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
Re^3: Discrepancy in reap notification message
by LanX (Saint) on Apr 28, 2017 at 01:30 UTC