mirror of
https://gitlab.com/famedly/conduit.git
synced 2024-11-04 17:18:51 +01:00
Fix crash when a bad user ID is in the database
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:
parent
08072d2c8d
commit
4a12a7cbc8
1 changed files with 5 additions and 4 deletions
|
@ -405,10 +405,11 @@ async fn sync_helper(
|
||||||
continue;
|
continue;
|
||||||
}
|
}
|
||||||
};
|
};
|
||||||
lazy_loaded.insert(
|
|
||||||
UserId::parse(state_key.as_ref())
|
// This check is in case a bad user ID made it into the database
|
||||||
.expect("they are in timeline_users, so they should be correct"),
|
if let Ok(uid) = UserId::parse(state_key.as_ref()) {
|
||||||
);
|
lazy_loaded.insert(uid);
|
||||||
|
}
|
||||||
state_events.push(pdu);
|
state_events.push(pdu);
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue