in reply to ChatterBox XML Ticker randomly throwing messages away

What I don't understand, do you say I think the first step for debugging would be to check what is logged and when it happens.

Sorry no time to look deeper into this (too) ...

HTH! :)

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

  • Comment on Re: ChatterBox XML Ticker randomly throwing messages away

Replies are listed 'Best First'.
Re^2: ChatterBox XML Ticker randomly throwing messages away
by choroba (Archbishop) on Jul 05, 2019 at 20:58 UTC
    Yes, the first message isn't displayed, but it must be recorded in the DB, as reposting the same message fails with "Whoa cowboy". I have no idea how to check what is logged.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
Re^2: ChatterBox XML Ticker randomly throwing messages away
by Tanktalus (Canon) on Jul 07, 2019 at 23:33 UTC

    No, the message is not logged in the DB, at least not in the chat box portion. I can verify this because I store the PM ID numbers that come back with each message for the CB stats. When the stats service goes down and I miss it on reboot, I can see a "space" in the ID numbers. When this error is hit on my end, there is no gap.

    I no longer have pmdev access here (as per my own request years ago), but I seem to recall that there is a field in the user that stores the last message that that user posted, and is used for comparison to get the whoa-cowboy rejection message. It appears to me that the message gets to the server far enough to be saved to the user record, but fails between that and actually putting it into the CB table. I'd argue that it shouldn't get saved to the user record until it has been successfully saved to the CB table (or both as part of the same transaction), but that's just arguing about error handling and doesn't solve the underlying error.

    (Thanks, choroba, for posting this.)

      Thanks, great insight.

      > I no longer have pmdev access here

      I think the most efficient approach would be to make you pmdev again.

      > (as per my own request years ago),

      Shouldn't be a problem to leave afterwards again. :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

        The underlying reasoning for requesting my own removal has not changed. Well, it has, but not for the better. I have insufficient time for the projects on my to-do list, and that has gotten worse since my removal, not better. The trend line is in the wrong direction :P As much as I would love to support jdporter on this, the reality is that providing the above clues is about as much as I can do right now. Signing on as a pmdev again would imply things that would be untrue, which I consider to be a form of lying. (Which I do differentiate from "I did something once, and it's too much work to get myself removed, so I'm leaving it alone" - I had pmdev access for years after I stopped contributing in that way, too.)

        I wish I had time for that type of help again. If wishes were nickels, though, I'd be rich.