| Age | Commit message (Collapse) | Author |
|---|
|
it was bumped in https://github.com/NixOS/nixpkgs/pull/176558
|
|
darwin-install: work around existing vim swap files
|
|
schema.sql: add comment about hash being in base16
|
|
Random fixes/improvements from the lazy-trees branch
|
|
|
|
|
|
|
|
|
|
|
|
enable LTO in optimized builds
|
|
|
|
User on Matrix reported install problems which presented as
"vifs:editing error" which we traced back to vim griping about an
existing swap file. When opened interactively, it did this:
E325: ATTENTION
Found a swap file by the name "/etc/.fstab.swp"
owned by: root dated: Sön Apr 24 16:54:10 2022
file name: /private/etc/fstab
modified: YES
user name: root host name: MBP.local
process ID: 1698
While opening file "/etc/fstab"
dated: Sön Apr 24 16:56:27 2022
NEWER than swap file!
...
|
|
|
|
Fix a segfault in the git fetcher
|
|
|
|
flake: use github: reference to nixpkgs
|
|
|
|
|
|
Fix noexcept violations
|
|
The call to perl.withPackages in nix-serve expects this.
|
|
Respect the outputSpecified attribute
|
|
'nix-serve' in nixpkgs expects the nix package to set this.
|
|
|
|
This violates the noexcept specification.
Fixes #6445.
|
|
E.g. 'nix build nixpkgs#libxml2.dev' will build the 'dev' output.
|
|
The git fetcher code used to dereference the (potentially empty) `ref`
input attribute. This was magically working, probably because the
compiler somehow outsmarted us, but is now blowing up with newer nixpkgs
versions.
Fix that by not trying to access this field while we don't know for sure
that it has been defined.
Fix #6554
|
|
|
|
|
|
src/libutil/json.cc: add missing <cstdint> include for gcc-13
|
|
Without the change llvm build fails on this week's gcc-13 snapshot as:
src/libutil/json.cc: In function 'void nix::toJSON(std::ostream&, const char*, const char*)':
src/libutil/json.cc:33:22: error: 'uint16_t' was not declared in this scope
33 | put(hex[(uint16_t(*i) >> 12) & 0xf]);
| ^~~~~~~~
src/libutil/json.cc:5:1: note: 'uint16_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
4 | #include <cstring>
+++ |+#include <cstdint>
5 |
|
|
There are still many links to the old manual on the web and
having them end up on the Introduction page is a bad user experience.
|
|
|
|
Added using the following sed scripts:
- For command-ref/opt-common.md:
s~- `(--?)([^`]+)`~- [`\1\2`]{#opt-\2}~g
- For expressions/builtin-constants.md:
s~- `(builtins\.?)([^`]+)`~- [`\1\2`]{#builtins-\2}~g
- For expressions/advanced-attributes.md
s~^ - `([^`]+)`~ - [`\1`]{#adv-attr-\1}~g
and manually adjusted outputHashAlgo & outputHashMode.
- For glossary.md
s~^ - (`([^`]+)`|(.+)) ?\\~ - [\1]{#gloss-\2\3}\\~g;
s~(gloss-\w+) ~\1-~g
and manually adjusted anchors for Nix expression, user environment, NAR, ∅ and ε.
- For command-ref/env-common.md
s~^ - `([^`]+)`~ - [`\1`]{#env-\1}~g'
|
|
Python is only pulled into the build closure by Mercurial, which might end up being removed.
Let’s port the script to jq, which is more likely to stay.
|
|
It is now possible to use the following syntax to insert anchors into the text:
[]{#anchor-name}
The anchor will allow linking to the location it is placed by appending #anchor-name to the URL.
Additionally, it is possible to create a link pointing to its own location by adding text between the square brackets:
[`--add-root`]{#opt-add-root}
|
|
Remove unused Perl dependency
|
|
|
|
Fix `Connection refused` on daemon socket
|
|
|
|
|
|
This solves the error
error: cannot connect to socket at '/nix/var/nix/daemon-socket/socket': Connection refused
on build farm systems that are loaded but operating normally.
I've seen this happen on an M1 mac running a loaded hercules-ci-agent.
Hercules CI uses multiple worker processes, which may connect to
the Nix daemon around the same time. It's not unthinkable that
the Nix daemon listening process isn't scheduled until after 6
workers try to connect, especially on a system under load with
many workers.
Is the increase safe?
The number is the number of connections that the kernel will buffer
while the listening process hasn't `accept`-ed them yet.
It did not - and will not - restrict the total number of daemon
forks that a client can create.
History
The number 5 has remained unchanged since the introduction in
nix-worker with 0130ef88ea in 2006.
|
|
Handle EOFs in string literals correctly
|
|
--debugger flag
|
|
|
|
|
|
|
|
|
|
We can't return a STR token without setting a valid StringToken,
otherwise the parser will crash.
Fixes #6562.
|
|
|
|
|
