| Age | Commit message (Collapse) | Author |
|---|
|
extract_archive: fix "Hard-link target '...'" error
|
|
EvalCommand::getEvalState: use gc tracable allocator for EvalState (fix segfault)
|
|
|
|
doc: Fix command for distributed builds
|
|
Fixes #5741
|
|
Libarchive documentation mentions that archive_entry_set_pathname
expects us to keep the passed string alive, which we don't.
|
|
Closes #1584.
|
|
|
|
We also need to build impurely or the <nixpkgs> lookup will not work.
|
|
Properly take the last assignment in the REPL
|
|
Fix link to nixos channel
|
|
The old link returned 404 errror.
|
|
When a variable is assigned in the REPL, make sure to remove any possible reference to the old one so that we correctly pick the new one afterwards
Fix #5706
|
|
Tidy up the logging
|
|
installer: clarify starting assumption task
|
|
darwin-install: fix break from bad vim plugins
|
|
|
|
document some darwin mount settings
|
|
|
|
|
|
|
|
|
|
Update manual links
|
|
Fixes: https://github.com/NixOS/nixos-homepage/issues/762
|
|
Add a :log command that shows logs for a derivation.
Closes https://github.com/NixOS/nix/issues/3504
Co-authored-by: Taeer Bar-Yam <taeer@bar-yam.me>
|
|
Before this change, stdout was closed after the pager exits. This is
fine for non-interactive commands where we want to exit right after
the pager exits anyways, but for interactive things (e.g. nix repl)
this breaks the output after we quit the pager.
Keep the initial stdout fd as part of RunPager, and restore it in
RunPager::~RunPager using dup2.
|
|
Fixes #5732.
|
|
Fix #5712
|
|
launchd: Set NumberOfFiles to 4096
|
|
|
|
The default maxfiles on macOS 11 and macOS 12 is 256, which is too low
for nix to work:
```
$ launchctl limit maxfiles
maxfiles 256 unlimited
```
Set NumberOfFiles of nix-daemon to 4096 to avoid `Too many open files`
error.
|
|
Introduce `builtins.groupBy` primop
|
|
Fix docker command
|
|
`docker -ti run nixos` does not run on docker version 20.10.7 (my machine). This fixes it to read `docker run -ti nixos`.
|
|
This function is very useful in nixpkgs, but its implementation in Nix
itself is rather slow due to it requiring a lot of attribute set and
list appends.
|
|
Flakes: computeLocks: pass correct LockParent when reusing oldLock
|
|
src/libutil/util.hh: fix build on gcc-11
|
|
Fix parent path check boundary
|
|
darwin-install: nail down diskutil invocations
|
|
Previously, when we were attempting to reuse the old lockfile
information in the computeLocks function, we have passed the parent of
the current input to the next computeLocks call. This was incorrect,
since the follows are resolved relative to the parent. This caused
issues when we tried to reuse oldLock but couldn't for some
reason (read: mustRefetch is true), in that case the follows were
resolved incorrectly.
Fix this by passing the correct parent, and adding some tests to
prevent this particular regression from happening again.
Closes https://github.com/NixOS/nix/issues/5697
|
|
Same purpose as de9efa3b79af7886fcf2a67b6ce97d4f96a57421
For some unclear reason, we get occasional reports from people who do
not have /usr/sbin on their PATH that the installer fails. It's a
standard part of the PATH, so I have no clue what they're doing to
remove it--but it's also fairly cheap to avoid.
|
|
- Previous to this commit the boundary was exclusive of the
top level flake.
- This is wrong since the top level flake is still a valid
relative reference.
- Now, the check boundary is inclusive of the top level flake.
Signed-off-by: Timothy DeHerrera <tim.deh@pm.me>
|
|
Due to missing <atomic> declaration the build fails as:
src/libutil/util.hh:350:24: error: no match for 'operator||' (operand types are 'std::atomic<bool>' and 'bool')
350 | if (_isInterrupted || (interruptCheck && interruptCheck()))
| ~~~~~~~~~~~~~~ ^~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| | |
| std::atomic<bool> bool
|
|
|
|
Fix #5299 and remove uncesssary unbounded buffer
|
|
Fix heap use after free in progress-bar.cc
|
|
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>
|
|
This doesn't fix the bug, but makes the code less difficult to read.
Also improve the comments, now that it is clear what part is needed in
each code path.
|
|
No more buffering in string.
|
|
Use the macros more, so we properly skip work when the log level
excludes. Also log the daemon operation number on the daemon side.
|
