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>
53 lines
1.8 KiB
Rust
53 lines
1.8 KiB
Rust
mod from_addr;
|
|
mod grpc;
|
|
mod memory;
|
|
mod nix_http;
|
|
mod sled;
|
|
|
|
#[cfg(any(feature = "fuse", feature = "virtiofs"))]
|
|
mod fs;
|
|
|
|
use futures::Stream;
|
|
use std::pin::Pin;
|
|
use tonic::async_trait;
|
|
use tvix_castore::proto as castorepb;
|
|
use tvix_castore::Error;
|
|
|
|
use crate::proto::PathInfo;
|
|
|
|
pub use self::from_addr::from_addr;
|
|
pub use self::grpc::GRPCPathInfoService;
|
|
pub use self::memory::MemoryPathInfoService;
|
|
pub use self::nix_http::NixHTTPPathInfoService;
|
|
pub use self::sled::SledPathInfoService;
|
|
|
|
#[cfg(any(feature = "fuse", feature = "virtiofs"))]
|
|
pub use self::fs::make_fs;
|
|
|
|
/// The base trait all PathInfo services need to implement.
|
|
#[async_trait]
|
|
pub trait PathInfoService: Send + Sync {
|
|
/// Retrieve a PathInfo message by the output digest.
|
|
async fn get(&self, digest: [u8; 20]) -> Result<Option<PathInfo>, Error>;
|
|
|
|
/// Store a PathInfo message. Implementations MUST call validate and reject
|
|
/// invalid messages.
|
|
async fn put(&self, path_info: PathInfo) -> Result<PathInfo, Error>;
|
|
|
|
/// Return the nar size and nar sha256 digest for a given root node.
|
|
/// This can be used to calculate NAR-based output paths,
|
|
/// and implementations are encouraged to cache it.
|
|
async fn calculate_nar(
|
|
&self,
|
|
root_node: &castorepb::node::Node,
|
|
) -> Result<(u64, [u8; 32]), Error>;
|
|
|
|
/// Iterate over all PathInfo objects in the store.
|
|
/// Implementations can decide to disallow listing.
|
|
///
|
|
/// This returns a pinned, boxed stream. The pinning allows for it to be polled easily,
|
|
/// and the box allows different underlying stream implementations to be returned since
|
|
/// Rust doesn't support this as a generic in traits yet. This is the same thing that
|
|
/// [async_trait] generates, but for streams instead of futures.
|
|
fn list(&self) -> Pin<Box<dyn Stream<Item = Result<PathInfo, Error>> + Send>>;
|
|
}
|