-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
nix-store 2.3 incompatible with nix-daemon 2.4pre #5299
Comments
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nix-2-4-and-what-s-next/16257/1 |
I can indeed reproduce it. It’s a bit hard to understand what’s going on because the messages exchanged when using the 2.3 and 2.4 clients are very different. I bisected it however to be introduced by bc10964, which should narrow the scope of the possible culprits quite a bit. /cc @Ericson2314 |
Thanks @regnat! There was some confusions about whether the protocol was using raw dump vs nar dump vs raw dump with references, that might be related too. |
I am taking a look. |
No matter what, we need to resize the buffer to not have any scratch space after we do the `read`. In the end of file case, `got` will be 0 from it's initial value. Before, we forgot to resize in the EOF case with the break. Yes, we know we didn't recieve any data in that case, but we still have the scatch space to undo. Co-Authored-By: Will Fancher <Will.Fancher@Obsidian.Systems>
Fix #5299 and remove uncesssary unbounded buffer
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/22-05-call-for-release-managers-and-editor/17663/16 |
Using nix-store 2.3 on a system where nix-daemon 2.4pre is running results in unexpected behavior.
Steps To Reproduce
Following script
produces following output:
The host system runs nix version
2.4pre20210908_3c56f62
.Expected behavior
nix-store shall not add 65536 zeros at the end of the file.
The text was updated successfully, but these errors were encountered: