nvrl 1477fe85d5 fix(drive): give each share root its own parent key in batch enumeration ...

enumerate_nodes and enumerate_nodes_light cached parent keys per batch by
the link's parent id. Every parentless link in a volume landed on None, so
when several share roots were enumerated together, the first root's share
key was used for the rest and they were dropped with "missing key".

Name a parent key by where it comes from: Parent(folder) for a link with a
parent, Root(link) for a parentless one. The batch cache and the
parent-key single-flight now both use that identity. The single-flight
previously keyed a root and its children on the same link id, although a
root resolves to its share key and its children to its node key, so two
concurrent cold loads could hand one of them the wrong key.

Fixes #2

2026-10-01 18:06:58 +02:00

..

examples

renamed for crate

2026-06-28 11:47:54 +02:00

src

fix(drive): give each share root its own parent key in batch enumeration

2026-10-01 18:06:58 +02:00

tests

fix(drive): give each share root its own parent key in batch enumeration

2026-10-01 18:06:58 +02:00

Cargo.toml

chore(VER) bumped to 0.7.1

2026-09-29 21:14:35 +02:00

LICENSE

renamed for crate

2026-06-28 11:47:54 +02:00