cafkafk/lix
cafkafk/lix
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

rl-next: add extra context to a few release notes

Browse source 
This was found while writing the release blog post.

Change-Id: Ifd55f308d4d4c831273cbe6ea35d29a38e134783
This commit is contained in:
Jade Lovelace 2024-08-09 20:09:08 -07:00
parent 35c9069c66
commit 7ca47a0e69
3 changed files with 17 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/manual/rl-next/better-invalid-path-errors.md Normal file
View file

@ -0,0 +1,10 @@
---
synopsis: "Confusing 'invalid path' errors are now 'path does not exist'"
cls: [1161, 1160, 1159]
credits: midnightveil
category: Improvements
---
Previously, if a path did not exist in a Nix store, it was referred to as the internal name "path is invalid".
This is, however, very confusing, and there were numerous such errors that were exactly the same, making it hard to debug.
These errors are now more specific and refer to the path not existing in the store.

1
doc/manual/rl-next/build-dir.md
View file

@ -1,6 +1,7 @@
--- ---
synopsis: "Add a `build-dir` setting to set the backing directory for builds" synopsis: "Add a `build-dir` setting to set the backing directory for builds"
cls: 1514 cls: 1514
prs: [gh#10303, gh#10312, gh#10883]
credits: [roberth, tomberek] credits: [roberth, tomberek]
category: Improvements category: Improvements
--- ---

9
doc/manual/rl-next/sanitizers.md
View file

@ -1,10 +1,13 @@
--- ---
synopsis: "Lix now supports building with UndefinedBehaviorSanitizer" synopsis: "Lix now supports building with UndefinedBehaviorSanitizer"
cls: [1483] cls: [1483, 1481, 1669]
credits: [jade] credits: [jade]
category: Development category: Development
--- ---
You can now build Lix with the configuration option `-Db_sanitize=undefined` and it will both work and pass tests. AddressSanitizer support is also coming soon. You can now build Lix with the configuration option `-Db_sanitize=undefined,address` and it will both work and pass tests with both AddressSanitizer and UndefinedBehaviorSanitizer enabled.
To use ASan specifically, you have to set `-Dgc=disabled`, which an error message will tell you to do if necessary anyhow.
For a list of undefined behaviour fixed by sanitizer usage, see [the gerrit topic "undefined-behaviour"](https://gerrit.lix.systems/q/topic:%22undefined-behaviour%22). Furthermore, tests passing with Clang ASan+UBSan is checked on every change in CI.
For a list of undefined behaviour found by tooling usage, see [the gerrit topic "undefined-behaviour"](https://gerrit.lix.systems/q/topic:%22undefined-behaviour%22).