diff options
author | Florian Klink <flokli@flokli.de> | 2024-05-10T05·59+0300 |
---|---|---|
committer | clbot <clbot@tvl.fyi> | 2024-05-11T13·33+0000 |
commit | 14766cfe1d41495f1c5aaec297c0e87756f0ff31 (patch) | |
tree | 212cb65721b79bb91442e757923ba366d46f6f2c /users/lukegb | |
parent | 944a781354a0d5151083e83669db8be7b8e69c59 (diff) |
refactor(tvix/store): drop calculate_nar from PathInfoService r/8103
This shouldn't be part of the PathInfoService trait. Pretty much none of the PathInfoServices do implement it, and requiring them to implement it means they also cannot make use of this calculation already being done by other PathInfoServices. Move it out into its own NarCalculationService trait, defined somewhere at tvix_store::nar, and have everyone who wants to trigger nar calculation use nar_calculation_service directly, which now is an additional field in TvixStoreIO for example. It being moved outside the PathInfoService trait doesn't prohibit specific implementations to implement it (like the GRPC client for the `PathInfoService` does. This is currently wired together in a bit of a hacky fashion - as of now, everything uses the naive implementation that traverses blob and directoryservice, rather than composing it properly. I want to leave that up to a later CL, dealing with other parts of store composition too. Change-Id: I18d07ea4301d4a07651b8218bc5fe95e4e307208 Reviewed-on: https://cl.tvl.fyi/c/depot/+/11619 Reviewed-by: Connor Brewster <cbrewster@hey.com> Autosubmit: flokli <flokli@flokli.de> Tested-by: BuildkiteCI
Diffstat (limited to 'users/lukegb')
0 files changed, 0 insertions, 0 deletions