mirror of
https://github.com/1f349/dendrite.git
synced 2024-11-23 20:21:38 +00:00
4c3a526e1b
When we're adding state to the database, we check which eventNIDs are already in a block, if we already have that eventNID, we remove it from the list. In its current form we would skip over eventNIDs in the case we already found a match (we're decrementing `i` twice) My theory is, that when we later get the state blocks, we are receiving "too many" eventNIDs (well, yea, we stored too many), which may or may not can result in state resets when comparing different state snapshots. (e.g. when adding state we stored a eventNID by accident because we skipped it, later we add more state and are not adding it because we don't skip it) |
||
|---|---|---|
| .. | ||
| postgres | ||
| shared | ||
| sqlite3 | ||
| tables | ||
| interface.go | ||
| storage_wasm.go | ||
| storage.go | ||