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

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.
  • Comment on Re^5: Discrepancy in reap notification message

Replies are listed 'Best First'.
Re^6: Discrepancy in reap notification message
by Eily (Monsignor) on May 03, 2017 at 07:58 UTC

    Hi jdporter
    I just got the message:

    You said "Reaped node at: [id://1189369] because [[afoken]]: insulting" to root
    With the square brackets and ampersand visible.

      Ok, I just put in a patch to try to "fix" that. Keep an eye out.

      I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
        UPDATE
        never mind, just a race condition :)

        ORIG
        I seem to remember considering Reaped: Double post saying reap : duplicate .

        But now it says Reason: [pryrt]: duplicate

        Just for completeness, there is a a chance that this was a race condition and pryrt considered at the same time and this is not a bug ...

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

Re^6: Discrepancy in reap notification message
by marto (Cardinal) on May 04, 2017 at 08:47 UTC

    I considered a duplicate of mine for reaping, and received 2 messages telling me.it had been reaped.

      Well that's expected, because you have two roles in the process.

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

Re^6: Discrepancy in reap notification message
by davies (Monsignor) on May 03, 2017 at 10:19 UTC

    And I got the same sort of thing after voting on a consideration.

    You said "Reaped node at: [id://1189354] because [[afoken]]: at best unhelpful" to root

    Regards,

    John Davies