TudbuT/conduit
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix crash when a bad user ID is in the database

Browse source 
To my understanding, a bad user ID can sometimes make it into the
database, which lead to a panic prior to this change.
This commit is contained in:
LordMZTE 2022-03-31 20:59:59 +02:00
parent 08072d2c8d
commit 4a12a7cbc8
No known key found for this signature in database
GPG key ID: B64802DC33A64FF6
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
src/client_server/sync.rs
View file

@ -405,10 +405,11 @@ async fn sync_helper(
continue;
}
};
lazy_loaded.insert(
UserId::parse(state_key.as_ref())
.expect("they are in timeline_users, so they should be correct"),
);
// This check is in case a bad user ID made it into the database
if let Ok(uid) = UserId::parse(state_key.as_ref()) {
lazy_loaded.insert(uid);
}
state_events.push(pdu);
}
}