Conversation
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughWalkthroughA new public setting Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
tests/functional/binary-cache.sh (1)
330-332: Consider clarifying the expected error condition in the comment.The comment states the failure is due to "nix-cache-info is gone and the cached metadata TTL is overridden to 0," but the expected error message is
"uploading.*is not supported". This suggests the store attempts to create/upload cache info when it can't be fetched, rather than simply failing to read it.Consider updating the comment to explain this behavior more explicitly for future maintainers:
# But with --refresh, it should fail because nix-cache-info is gone -# and the cached metadata TTL is overridden to 0. +# and the cached metadata TTL is overridden to 0. When nix-cache-info +# cannot be fetched, the HTTP store falls back to trying to create it, +# which fails because uploading is not supported. _NIX_FORCE_HTTP=1 expectStderr 1 nix store info --store "file://$cacheDir" --refresh | grepQuiet "uploading.*is not supported"
This makes the current hard-coded 7-day `nix-cache-info` TTL configurable, making `--offline` and `--refresh` do the right thing.
e518b25 to
4d0c767
Compare
Motivation
This makes the current hard-coded 7-day
nix-cache-infoTTL configurable, making--offlineand--refreshdo the right thing.Context
Summary by CodeRabbit
New Features
Bug Fixes
Tests