-
-
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
Regression builtins.getContext
/ outputs = [ "" ]
#7655
Labels
Comments
Have fix, just writing tests. |
|
Oh nevermind, I see now. |
Ericson2314
added a commit
to obsidiansystems/nix
that referenced
this issue
Jan 22, 2023
The original `builtins.getContext` test from 1d75729 would have caught this. The problem is that b30be6b adding `builtins.appendContext` modified that test to make it test too much at once, rather than adding a separate test. We now have isolated tests for both functions, and also a property test showing everything put together (in the form of an eta rule for strings with context). This is better coverage and properly reproduces the bug.
Ericson2314
added a commit
to obsidiansystems/nix
that referenced
this issue
Jan 22, 2023
We had some local variables left over from the older (more complicated) implementation of this function. They should all be unused, but one wasn't by mistake. Delete them all, and replace the one that was still in use as intended.
roberth
added a commit
that referenced
this issue
Jan 23, 2023
github-actions bot
pushed a commit
that referenced
this issue
Jan 23, 2023
The original `builtins.getContext` test from 1d75729 would have caught this. The problem is that b30be6b adding `builtins.appendContext` modified that test to make it test too much at once, rather than adding a separate test. We now have isolated tests for both functions, and also a property test showing everything put together (in the form of an eta rule for strings with context). This is better coverage and properly reproduces the bug. (cherry picked from commit 88d8f6a)
roberth
added a commit
that referenced
this issue
Jan 23, 2023
[Backport 2.13-maintenance] Fix #7655
The fix has been released in 2.13.2. |
iFreilicht
pushed a commit
to iFreilicht/nix
that referenced
this issue
Jan 28, 2023
The original `builtins.getContext` test from 1d75729 would have caught this. The problem is that b30be6b adding `builtins.appendContext` modified that test to make it test too much at once, rather than adding a separate test. We now have isolated tests for both functions, and also a property test showing everything put together (in the form of an eta rule for strings with context). This is better coverage and properly reproduces the bug.
iFreilicht
pushed a commit
to iFreilicht/nix
that referenced
this issue
Jan 28, 2023
We had some local variables left over from the older (more complicated) implementation of this function. They should all be unused, but one wasn't by mistake. Delete them all, and replace the one that was still in use as intended.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
builtins.getContext
always returns{ outputs = [ "" ]; }
for build outputs.Steps To Reproduce
cd nixpkgs; nix repl .
Expected:
Actual:
Expected behavior
nix-env --version
outputmaster, 2.13.1
Additional context
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: