ZeroFS looks really good. I know a bit about this design space but hadn't run across ZeroFS yet. Do you do testing of the error recovery behavior (connectivity etc)?
This has been mostly manual testing for now.
ZeroFS currently lacks automatic fault injection and proper crash tests, and it’s an area I plan to focus on.
SlateDB, the lower layer, already does DST as well as fault injection though.
Re:Pricing Changes for GitHub Actions
by featherless on Tuesday December 16, 2025 @01:30PM
(#46292319)
I found that implementing a local cache on the runners has been helpful. Ingress/egress on local network is hella slow, especially when each build has ~10-20GB of artifacts to manage.
What do you use for the local cache?
Re:Pricing Changes for GitHub Actions
by featherless on Tuesday December 16, 2025 @02:25PM
(#46293133)
Just wrote about my approach yesterday: https://jeffverkoeyen.com/blog/2025/12/15/SlotWarmedCaching/
tl;dr uses a local slot-based cache that is pre-warmed after every merge to main, taking Sidecar builds from ~10-15 minutes to <60 seconds.
Re:Pricing Changes for GitHub Actions
by theLiminator on Tuesday December 16, 2025 @01:58PM
(#46292728)
Wow, that's a very cool project.
A lot of it is wasted in build time though, due to a lack of appropriate caching facilities with GitHub actions.
[0] https://github.com/Barre/ZeroFS/tree/main/.github/workflows