in reply to Discrepancy in reap notification message

Thanks for the tip. I have just put out a patch which changes this behavior. I ask everyone to keep an eye out for the new behavior and let me know if it's different/better.

I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
  • Comment on Re: Discrepancy in reap notification message

Replies are listed 'Best First'.
Re^2: Discrepancy in reap notification message
by LanX (Saint) on Apr 27, 2017 at 12:21 UTC
    Thanks for your contributions to develop our site! :)

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

Re^2: Discrepancy in reap notification message
by beech (Parson) on Apr 28, 2017 at 00:33 UTC

    Hi,

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

      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.

        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