in reply to Re^3: Reputation: -4 (+-0.5 -3.5)
in thread Reputation: -4 (+-0.5 -3.5)

Thanks, that explains it nicely!

It's interesting that it's not a transient issue: the votes are still fractional, so an update to votescast was likely permanently lost rather than you just seeing "torn values". 

Reputation: -8 (+1.5 -9.5)

[download]

Mike

Replies are listed 'Best First'.
Re^5: Reputation: -4 (+-0.5 -3.5)
by LanX (Saint) on Jul 21, 2019 at 21:00 UTC
    > It's interesting that it's not a transient issue:

    Looks logical to me, one down-vote only made it to rep but not to votescast, the DB wont store any other info.

    Seems like the desire to show "up" and "down" votes separately, came long after the DB model was established.

    This explains also why the display of it can be toggled in the settings.

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

[reply]

      the DB wont store any other info.

      It surely stores who cast the votes (to prevent duplicate votes). As such, there are two ways to update reputation as a vote is cast:

      • Increment or decrement it as appropriate.
      • Calculate it from the votes in the database.

      RMGir was pointing out the former approach was used; the latter would make the effect of the bug transient.

      Actually, the latter would avoid the bug completely.

[reply]
[d/l]
        > It surely stores who cast the votes (to prevent duplicate votes).

        yes, good point

        > Actually, the latter would avoid the bug completely.

        Everything::Experience.pm is not trivial to understand or to change

        and I'm suspecting a recent change to introduce this problem which can't be fixed without changing the data model.

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

[reply]

In Section Perl Monks Discussion