| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
|
|
|
|
Ignore the enforceDeterminism value
|
|
We used to set enforceDeterminism to true in the settings (by default)
and thus did send a non-zero value over the wire. The value should
probably be ignored as it should only matter if nrRounds is non-zero
as well.
Having the old code here where the value is expected to be zero only
works with the same version of Nix where we are sending zero. We
should always test this against older Nix versions being client or
server as otherwise upgrade in larger networks might be a pain.
Fixes 8e0946e8df968391d1430af8377bdb51204e4666
|
|
Remove tests for --repeat
|
|
https://hydra.nixos.org/build/201125739
|
|
Update uninstall guide involving systemd
|
|
systemd,launchd match nixos open files limit
|
|
check the store for input before failing (hopefully fix #6383)
|
|
refactor rendering documentation of options
|
|
tests: don't refer to TMPDIR
|
|
.version: Add newline
|
|
Remove repeat option
|
|
this is a follow-up on e7dcacb.
most links are relative and this should not be too much of a detriment.
|
|
this avoids incorrect rendering on the man pages, since `lowdown`
neither parses the anchor syntax nor HTML.
this should rather be fixed in lowdown, as adding more anchors
would otherwise produce ever more noise and error-prone repetition.
|
|
|
|
|
|
* docs: Use secret-key-files when demonstrating post-build-hooks
The docs used to recommend calling `nix store sign` in a post-build
hook, but on more recent versions of nix, this results in unsigned
store paths being copied into binary caches. See
https://github.com/NixOS/nix/issues/6960 for details.
Instead, use the `secret-key-files` config option, which signs all
locally-built derivations with the private key.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
let installer blurb to to community page
|
|
These only functioned if a very narrow combination of conditions held:
- The result path does not yet exist (--check did not result in
repeated builds), AND
- The result path is not available from any configured substituters, AND
- No remote builders that can build the path are available.
If any of these do not hold, a derivation would be built 0 or 1 times
regardless of the repeat option. Thus, remove it to avoid confusion.
|
|
add template for installer issues
|
|
being too specific about it requires more maintenance (or otherwise
produced more confusion and churn), since these points of contact change
over time.
|
|
since the installer prompts users to file issues, labelling them
automatically should reduce triaging effort significantly.
|
|
Bump version to 2.13
|
|
|
|
|
|
|
|
Branch 2.12 release notes
|
|
|
|
move documentation on `auto-allocate-uids` to options docs
|
|
|
|
|
|
check the store for input before failing (hopefully fix #6700)
|
|
getMaxCPU: fix cgroup path
|
|
Revert "docs: drop shell prompt character for consistency"
|
|
|
|
add maintainers' handbook
|
|
|
|
|
|
add CODEOWNERS
|
|
Given this typo I am not sure if it has been tested.
|
|
encourage adding 👍 to express interest
|
|
Lower verbosity of exceptions in getMaxCPU()
|
|
Change "while evaluating <fun>" to "while *calling*" in trace
|
|
The old way was not correct.
Here is an example:
```
$ nix-instantiate --eval --expr 'let x = a: throw "asdf"; in x 1' --show-trace
error: asdf
… while evaluating 'x'
at «string»:1:9:
1| let x = a: throw "asdf"; in x 1
| ^
… from call site
at «string»:1:29:
1| let x = a: throw "asdf"; in x 1
| ^
```
and yet also:
```
$ nix-instantiate --eval --expr 'let x = a: throw "asdf"; in x' --show-trace
<LAMBDA>
```
Here is the thing: in both cases we are evaluating `x`!
Nix is a higher-order languages, and functions are a sort of value. When
we write `x = a: ...`, `a: ...` is the expression that `x` is being
defined to be, and that is already a value. Therefore, we should *never*
get an trace that says "while evaluating `x`", because evaluating `a:
...` is *trival* and nothing happens during it!
What is actually happening here is we are applying `x` and evaluating
its *body* with arguments substituted for parameters. I think the
simplest way to say is just "while *calling* `x`", and so that is what I
changed it to.
|
|
Fixes #7268.
|
|
doc: listToAttrs: document repeated keys
|
