diff options
author | Florian Klink <flokli@flokli.de> | 2024-03-20T18·21+0200 |
---|---|---|
committer | clbot <clbot@tvl.fyi> | 2024-03-24T17·39+0000 |
commit | c92ef2df64f4013e72037cefb548f68d158488cc (patch) | |
tree | d3d536e062a521fbcdcae8975d285315e47abb1b /tvix/castore/src/proto/grpc_directoryservice_wrapper.rs | |
parent | bd953d0703e072246fa7d7a79f9a46a8d2006a26 (diff) |
feat(tvix/castore/directory): add ClosureValidator r/7772
This can be used to validate a Directory closure (connected DAG of Directories), and their insertion order. Directories need to be inserted (via `add`), in an order from the leaves to the root. During insertion, we validate as much as we can at that time: - individual validation of Directory messages - validation of insertion order (no upload of not-yet-known Directories) - validation of size fields of referred Directories Internally it keeps all received Directories (and their sizes) in a HashMap, keyed by digest. Once all Directories have been inserted, a drain() function can be called to get a (deduplicated and) validated list of directories, in from-leaves-to-root order (to be stored somewhere). While assembling that list, a check for graph connectivity is performed too, to ensure there's no separate components being sent (and only one root). It adds a test suite for these cases, which is much nicer to test than where we previously had these checks (only in the gRPC server wrapper). Followup CLs will move the existing putters to use this. Change-Id: Ie88c832924c170a24626e9e3e91d868497b5d7a4 Reviewed-on: https://cl.tvl.fyi/c/depot/+/11220 Tested-by: BuildkiteCI Reviewed-by: raitobezarius <tvl@lahfa.xyz> Autosubmit: flokli <flokli@flokli.de>
Diffstat (limited to 'tvix/castore/src/proto/grpc_directoryservice_wrapper.rs')
0 files changed, 0 insertions, 0 deletions