| nipunn | |
| Sep 14 2015, 7:05 PM |
| F809593: Screenshot 2015-09-14 12.00.46.png | |
| Sep 14 2015, 7:05 PM |
Not totally sure how I got into this state. Didn't try to repro yet.
This doesn't seem problematic to me. It accurately represents the actions you took (submitting multiple accepts from the web UI and via email) and doesn't create any inconsistencies, problems with revision state, etc. It's a little odd, but the workflow was a little odd.
If you do something silly and processing that silly thing doesn't actually create problems, we try to just do the silly thing literally rather than second guess you. This is usually more clear.
For example, if you'd swapped the order of these actions and sent an "!accept" email and we ignored the action if it didn't prompt a state change, we would seem to ignore the email. A user might reasonably be confused that their email was ignored if their web-UI accept was 50 comments ago and they'd forgotten about it.
Am I missing anything, like a real problem or inconsistency this creates?
Nope totally sounds reasonable.
I think the thing that was weird to me was that I was able to accept from the UI after it was already in an accepted state, but since I had an old session, sure do it twice.
If you're running the notification server, the old session should have had a "Page has been updated, click to reload." badge on it. Not sure if you guys have that configured, but that can provide a cue that you're out of date.