chore(deps): bump ordered-float from 5.2.0 to 5.3.0#23
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [ordered-float](https://github.com/reem/rust-ordered-float) from 5.2.0 to 5.3.0. - [Release notes](https://github.com/reem/rust-ordered-float/releases) - [Commits](reem/rust-ordered-float@v5.2.0...v5.3.0) --- updated-dependencies: - dependency-name: ordered-float dependency-version: 5.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
2 tasks
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
This was referenced Jul 6, 2026
pilotspacex-byte
added a commit
that referenced
this pull request
Jul 11, 2026
… replicas (#281) HIGH-2 (tasks #22 + #23): the replica-side drain already understood in-stream SELECT context (drain_replicated_commands binds each command to the selected db), but the master never emitted it — every replicated write applied to the replica's db 0 regardless of which db it executed in on the master. And a client could not even READ a replica's non-zero dbs: SELECT is flagged W in the metadata table, so the READONLY guard rejected it. Master side: - ReplicationState grows per-shard `stream_db: Vec<AtomicI64>` (-1 = unknown): the logical-db context of the LAST data command recorded into the shard's replication backlog. - New `record_local_write_db(ctx, db, bytes)` prepends a `SELECT <db>` record via the existing `record_local_write` primitive whenever the writing connection's db differs from the stream context. Both records stay in the same synchronous stretch as the mutation (exactly-once contract unchanged; SELECT bytes advance the offset like any stream bytes). - All db-scoped record sites switched to the db-aware variant: the three KV legs (main, MOVE, COPY), the MULTI/EXEC body loop, the GRAPH.* WAL-record leg, and the FT.* index-def leg. The TEMPORAL.INVALIDATE-AT leg keeps the primitive (db-agnostic record, leaves the context untouched — which stays truthful). - FULLRESYNC snapshot capture resets the shard's stream_db to -1 in the SAME synchronous stretch as the RDB capture (Redis's `slaveseldb = -1` idiom): every byte at offset >= snapshot_offset starts from "db unknown", so the first post-snapshot write re-establishes the context with an explicit SELECT and a fresh replica (whose drain starts at db 0) can never bind a write to the wrong db. Redundant re-SELECTs for already-attached replicas are idempotent. Replica side: - `ReplicaTaskConfig::stream_db` (AtomicUsize) preserves the drain's db context ACROSS reconnects: a +CONTINUE partial resync replays backlog bytes that only carry SELECT at db CHANGES — if the stream was in db N when the link dropped, the resumed bytes have no fresh SELECT and a 0-reset drain would misapply them to db 0. Seeded into stream_commands on entry, persisted after every drain, reset to 0 on +FULLRESYNC. In-memory only: a replica process restart starts at offset 0 and always full-resyncs. - READONLY guards (monoio dispatch, tokio sharded dispatch, handler_single) now serve SELECT on replicas — connection-state only, Redis parity. New e2e replica_applies_multi_db_stream (RED before the fix — failed at the READONLY SELECT assertion, then would misapply db-2 writes to db 0): db-0 write flows, SELECT 2 + SET on the master, db-0 hop-back sentinel; asserts the db-2 write lands in db 2 on the replica, did NOT leak into db 0, and the db-0 sentinel did not leak into db 2. Verification: lib 4111 green, replication_streaming 5/5 (incl. new test), replication_graph 3/3, replication_hardening 5/5, tokio replication_test 5/5, fmt clean, clippy clean on default and runtime-tokio,jemalloc. author: Tin Dang Co-authored-by: Tin Dang <tindang.ht97@gmail.com>
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.
Bumps ordered-float from 5.2.0 to 5.3.0.
Release notes
Sourced from ordered-float's releases.
Commits
6cca9b8v5.3.0a980aa3Rkyv v0.8 compatibility (#182)09998b4Fix broken link in docsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)