Fix error handling during insertion of client IPs (#9051)

You can't continue using a transaction once an exception has been
raised, so catching and dropping the error here is pointless and just
causes more errors.
This commit is contained in:
Erik Johnston 2021-01-08 14:15:20 +00:00 committed by GitHub
parent 195adf4025
commit fa5f5cbc74
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 25 additions and 32 deletions

1
changelog.d/9051.bugfix Normal file
View file

@ -0,0 +1 @@
Fix error handling during insertion of client IPs into the database.

View file

@ -470,15 +470,10 @@ class ClientIpStore(ClientIpWorkerStore):
for entry in to_update.items():
(user_id, access_token, ip), (user_agent, device_id, last_seen) = entry
try:
self.db_pool.simple_upsert_txn(
txn,
table="user_ips",
keyvalues={
"user_id": user_id,
"access_token": access_token,
"ip": ip,
},
keyvalues={"user_id": user_id, "access_token": access_token, "ip": ip},
values={
"user_agent": user_agent,
"device_id": device_id,
@ -503,9 +498,6 @@ class ClientIpStore(ClientIpWorkerStore):
"ip": ip,
},
)
except Exception as e:
# Failed to upsert, log and continue
logger.error("Failed to insert client IP %r: %r", entry, e)
async def get_last_client_ip_by_device(
self, user_id: str, device_id: Optional[str]