Description of problem:
When there are multiple browser sessions open for the same user, and a promotion fails with "×Failed to promote: Cannot promote a changeset while another is being promoted." (or possibly with other notifs), the notification goes to the wrong session. This only happens for async notifications.
<jsherrill> bbuckingham: jweiss i think this issue is a lot simpler, i think
we can just change synchronous_request to true on that one error
message and be ok
<jsherrill> i think that will fix the bug
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Changing to an ehnacement - basically we will have to track notices with sessions to that we can respond to the right session with the right notice. This will have to be a somewhat major rewrite of notifications as it stands now since they aren't tied to sessions at all.
Notifications are no longerused. i am closing this out. Please feel free to reopen if you disagree.