2023-09-21 22:32:44 +03:00
|
|
|
mod digests;
|
|
|
|
|
mod errors;
|
2024-03-03 14:46:54 +02:00
|
|
|
mod hashing_reader;
|
2023-09-21 22:32:44 +03:00
|
|
|
|
|
|
|
|
pub mod blobservice;
|
2024-06-17 01:10:55 +02:00
|
|
|
pub mod composition;
|
2023-09-21 22:32:44 +03:00
|
|
|
pub mod directoryservice;
|
|
|
|
|
pub mod fixtures;
|
chore(tvix): move store/fs to castore/fs
With the recent introduction of the RootNodes trait, there's nothing in
the fs module pulling in tvix-store dependencies, so it can live in
tvix-castore.
This allows other crates to make use of TvixStoreFS, without having to
pull in tvix-store.
For example, a tvix-build using a fuse mountpoint at /nix/store doesn't
need a PathInfoService to hold the root nodes that should be present,
but just a list.
tvix-store now has a pathinfoservice/fs module, which contains the
necessary glue logic to implement the RootNodes trait for a
PathInfoService.
To satisfy Rust orphan rules for trait implementations, we had to add a
small wrapper struct. It's mostly hidden away by the make_fs helper
function returning a TvixStoreFs.
It can't be entirely private, as its still leaking into the concrete
type of TvixStoreFS.
tvix-store still has `fuse` and `virtiofs` features, but they now simply
enable these features in the `tvix-castore` crate they depend on.
The tests for the fuse functionality stay in tvix-store for now, as
they populate the root nodes through a PathInfoService.
Once above mentioned "list of root nodes" implementation exists, we
might want to shuffle this around one more time.
Fixes b/341.
Change-Id: I989f664827a5a361b23b34368d242d10c157c756
Reviewed-on: https://cl.tvl.fyi/c/depot/+/10378
Autosubmit: flokli <flokli@flokli.de>
Tested-by: BuildkiteCI
Reviewed-by: sterni <sternenseemann@systemli.org>
2023-12-17 00:16:22 +02:00
|
|
|
|
|
|
|
|
#[cfg(feature = "fs")]
|
|
|
|
|
pub mod fs;
|
|
|
|
|
|
2024-05-01 12:53:09 +03:00
|
|
|
mod path;
|
2024-05-01 20:25:04 +03:00
|
|
|
pub use path::{Path, PathBuf};
|
2024-05-01 12:53:09 +03:00
|
|
|
|
2023-09-21 22:32:44 +03:00
|
|
|
pub mod import;
|
|
|
|
|
pub mod proto;
|
2023-11-13 14:32:24 +02:00
|
|
|
pub mod tonic;
|
2023-09-21 22:32:44 +03:00
|
|
|
|
2023-10-05 10:57:27 +03:00
|
|
|
pub use digests::{B3Digest, B3_LEN};
|
refactor(tvix/castore): use Directory struct separate from proto one
This uses our own data type to deal with Directories in the castore model.
It makes some undesired states unrepresentable, removing the need for conversions and checking in various places:
- In the protobuf, blake3 digests could have a wrong length, as proto doesn't know fixed-size fields. We now use `B3Digest`, which makes cloning cheaper, and removes the need to do size-checking everywhere.
- In the protobuf, we had three different lists for `files`, `symlinks` and `directories`. This was mostly a protobuf size optimization, but made interacting with them a bit awkward. This has now been replaced with a list of enums, and convenience iterators to get various nodes, and add new ones.
Change-Id: I7b92691bb06d77ff3f58a5ccea94a22c16f84f04
Reviewed-on: https://cl.tvl.fyi/c/depot/+/12057
Tested-by: BuildkiteCI
Reviewed-by: flokli <flokli@flokli.de>
2024-07-29 14:34:50 +02:00
|
|
|
pub use errors::{Error, ValidateDirectoryError, ValidateNodeError};
|
2024-03-03 14:46:54 +02:00
|
|
|
pub use hashing_reader::{B3HashingReader, HashingReader};
|
2023-09-21 22:32:44 +03:00
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
mod tests;
|
2024-03-23 21:49:49 +01:00
|
|
|
|
|
|
|
|
// That's what the rstest_reuse README asks us do, and fails about being unable
|
|
|
|
|
// to find rstest_reuse in crate root.
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
#[allow(clippy::single_component_path_imports)]
|
|
|
|
|
use rstest_reuse;
|
