-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] V6.1.0 and V6.1.1 don't seem to work with V6.0.0 caches #82
Comments
I'm getting this error with caches created by the latest versions. The job passes if it doesn't restore. https://github.com/nix-community/nix-vscode-extensions/actions/runs/13786047382/job/38554685144 If you have a chance, please try debugging with action-tmate. |
@thenonameguy it'd be also nice if you could reproduce the problem with more verbosity. |
I can reliably reproduce the issue by running the failing job again. Everything is OK if I run |
In my case, the problem is with UPD: not always |
When building template#devShells.x86_64-linux.default, I get a derivation as an output
After GC and building, I get a normal path.
Something very wrong happens during saving/restoring a cache. |
v6.1.0 introduced changes to the SQL script that merges databases of two stores (existing and restored). If there's a problem, it should be in that script https://github.com/nix-community/cache-nix-action/blob/aee88ae5efbbeb38ac5d9862ecbebdb404a19e69/src/templates/merge.sql The script can be used with local stores created via |
@thenonameguy should be fixed in v6.1.2. |
Describe the bug
Our GHA jobs started failing today, after the new minor and patch releases.
It seems internally the Nix JSON output gets broken with the old caches used:
Disabling the caching action or downgrading it with an explicit
v6.0.0
version solved this problem.It seems there might be a log message starting with
D
, breaking the JSON parsing of devenv.To Reproduce
Sorry, I only have a private repo.
Expected behavior
Minor and patch version bumps don't break caches restored from former versions in any way.
Additional context
The text was updated successfully, but these errors were encountered: