Bound schema-ordered observation admission - #479
Merged
Conversation
WalkthroughИзменена канонизация schema-ordered наблюдений: сценарии сортируются по ChangesКанонизация schema-ordered наблюдений
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Collaborator
Author
|
@coderabbitai review |
✅ Action performedReview finished.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Что изменено
ScenarioId, независимо от порядка входа;ResourceExhaustedдо чтения источника;observation.rs.Корневая причина
Предыдущая фиксированная мультипликативная хеш-функция с линейным пробированием допускала квадратичную работу на враждебно подобранных opaque ID. Порядок ранних ошибок также зависел от порядка сценариев клиента.
Эффект
Admission имеет ограничение
O(n · w · log n)приO(n)scratch-памяти, не придаёт смысла opaque ID и сохраняет allocation-free exact replay после роста scratch.Проверка
BTreeMap/BTreeSetoracle;cargo test -p labcolors-core --all-targets --quiet: 895 passed, 6 ignored, интеграционные наборы пройдены;cargo clippy -p labcolors-core --all-targets -- -D warnings;cargo fmt --all -- --check;cargo package -p labcolors-core --allow-dirty;Summary by CodeRabbit
Улучшения
Тесты
Проверки