NixHTTPPathInfoService acts as a bridge in between the Nix HTTP Binary cache protocol provided by Nix binary caches such as cache.nixos.org, and the Tvix Store Model. It implements the [PathInfoService] trait in an interesting way: Every [PathInfoService::get] fetches the .narinfo and referred NAR file, inserting components into a [BlobService] and [DirectoryService], then returning a [PathInfo] struct with the root. Due to this being quite a costly operation, clients are expected to layer this service with store composition, so they're only ingested once. The client is expected to be (indirectly) using the same [BlobService] and [DirectoryService], so able to fetch referred Directories and Blobs. [PathInfoService::put] and [PathInfoService::nar] are not implemented and return an error if called. This behaves very similar to the nar-bridge-pathinfo code in nar-bridge, except it's now in Rust. Change-Id: Ia03d4fed9d0657965d100299af97cd917a03f2f0 Reviewed-on: https://cl.tvl.fyi/c/depot/+/10069 Tested-by: BuildkiteCI Autosubmit: flokli <flokli@flokli.de> Reviewed-by: raitobezarius <tvl@lahfa.xyz>
47 lines
1.7 KiB
Rust
47 lines
1.7 KiB
Rust
mod from_addr;
|
|
mod grpc;
|
|
mod memory;
|
|
mod nix_http;
|
|
mod sled;
|
|
|
|
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;
|
|
|
|
/// 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>>;
|
|
}
|