Today, my downvotes stopped working. I can press the buttons, but after refreshing downvote marks disappear, while upvote marks stay (which means that the scripts at least partially work; I also tried another browser). No message to the effect that I’m not allowed to downvote ever appears. I suppose I could’ve made 25000 downvotes, counting 10x post downvotes, to hit the 4*karma limit, but it seems unlikely, and there should be a message if that limit is reached in any case.
in one sentence… the vote processing mechanism required a reference to the global configuration for pylons and the pylons configuration import was missing.
not super interesting unfortunately :]
it was probably something like a munged automerge or something
Today, my downvotes stopped working. I can press the buttons, but after refreshing downvote marks disappear, while upvote marks stay (which means that the scripts at least partially work; I also tried another browser). No message to the effect that I’m not allowed to downvote ever appears. I suppose I could’ve made 25000 downvotes, counting 10x post downvotes, to hit the 4*karma limit, but it seems unlikely, and there should be a message if that limit is reached in any case.
Same here. And upvotes do not have the same problem, so I don’t think it’s a caching issue.
hmmm I can confirm this both here and on a local copy of the codebase, I’ll have a look and make sure Wes knows
It was a simple bug, fix is committed and a pull request is in, I’ll send an email out now to get this into production.
I would be very interested in a one-sentence description of the bug. Especially if it was not just a side-effect of some other change in the codebase.
in one sentence… the vote processing mechanism required a reference to the global configuration for pylons and the pylons configuration import was missing.
not super interesting unfortunately :]
it was probably something like a munged automerge or something
I would be very interested in a one-sentence description of the bug. Especially if it was not just a side-effect of some other change in the codebase.
hmmm I can confirm this both here and on a local copy of the codebase, I’ll have a look and make sure Wes knows
This happens to me, as well.