I wanted to see the 'like history on a post and clicked on the heart rather than the number next to it. That cleared my and reduced the counter and now I get this message when I try to restore it:
HOWEVER, my user avatar was still there. By the time I managed to capture screenshots and compose this message, I was able to refresh the page and see the heart filled in and the correct count.
This does complicate the poor aim with a mouse click situation, but also raises the question of how to clear/withdraw a reliably. I’m done fiddling with this for today and will let someone test that.
Sorry, guys. I left out a step and also misreported the procedure. The trigger for the bug was when I tried to close the queue (or whatever you guys call it) and clicked the instead of the queue count.
I don’t recall the exact steps from yesterday but was able to reproduce it here just now.
Set the
expand the queue
clear the
restore the
You should get the error message when trying to restore the heart. See if you can reproduce the behavior with the steps above before delving in to the following detail. It gets pretty weird.
For the record, I’m a developer of industrial automation, robotics, and vision systems so my bug reports are usually very reliable.
P.S. I can barely see the dividing line below. Does it render with decent contrast for anyone? (Please report your active theme.)
I made this happen one time on @sam’s post and then refreshed the page to see if that would clear the hung state of the . When I refreshed the page to test more, the behaved as expected. @Jagster’s post also worked as it should right after the refresh (I hadn’t done anything with it prior to the refresh). I could set and clear the heart.
HOWEVER, after a short time, I was not able to clear the on Sam’s post and then Jakke’s psot was hanging in the set() state as reported in the OP, throwing the error:
See if you can reproduce it with the steps above. I think it has to do with setting and then clearing with the queue open in the same page visit.
If I can report any more detail on how to reproduce this, I will. Jakke’s post changing behavior without a refresh was very odd.
I tried to reproduce this issue here on meta and I am able to reproduce it. I think it’s rate limiting issue. When I click the like 3-4 time in less that 30 seconds I get rate limiting error saying I have to wait for 30 seconds to perform this action again. I repeated this 2 times. After that I got this same error.
I think that’s due to discourse thinks you are a bot and trying to do something wrong.
So perhaps we can classify this as “quirky behavior unless you refresh the page”.
Makes sense, though the error message doesn’t communicate this because it appears to be a system message (from the program execution environment/shell, not the Discourse application itself) rather than than a user error message.
…and 24 hours later, I still can’t clear either "heart: from Sam’s or Jakke’s posts. This might be the edit_window_time expiring. (setting name is pseudocode.)
and reduced the counter and now I get this message when I try to restore it:
