This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
save_channels uses a conditional check #320
Comments
bbangert
added a commit
that referenced
this issue
Feb 1, 2016
…dge-case During monthly rotation, if a user drops the connection after the monthly rotation has begun, but before it completed, then the message table will be updated but not the router table. This means that the next call will fail since put_item wasn't called with overwrite=True. This patch fixes that and includes an integration test to verify the fix. Closes #320
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apparently using
put_item
in boto causes a conditional check to exist on the update. It's rather important that the channels are just saved out, otherwise the rest of the router table update won't proceed, and the transport won't resume.The put_item should be replaced with a direct table update like our other functions to ensure the channels are correctly saved. An errback should be added to the table rotation that disconnects users that rotation fails for, since the pauseProducing means we will be unable to do anything with the user until they reconnect.
The text was updated successfully, but these errors were encountered: