[libc++][NFC] Mark LWG3884 as complete in C++26 issues status (#195819)
[LWG3884](https://wg21.link/LWG3884) requires allocator-extended
copy/move constructors on the flat container adaptors. All four
container adaptors (flat_map, flat_multimap, flat_set, flat_multiset)
landed with these constructors and their tests already in place:
- flat_map (#98643) -- LLVM 20
- flat_multimap (#113835) -- LLVM 20
- flat_set (#125241) -- LLVM 21
- flat_multiset (#128363) -- LLVM 21
This LWG issue was fully addressed once flat_set/flat_multiset landed in
LLVM 21, so the status is updated to `|Complete|` with first released
version 21.
Closes #105269
Co-authored-by: Hristo Hristov <zingam at outlook.com>
hammer2 - Disallow duplicate label names in newfs_hammer2
* Disallow duplicate label names in newfs_hammer2, which leads
to a radix tree insertion panic later on.
Reported-by: afranke (Andreas Franke) using AI operational analysis
DragonFly-PR: 3406
hammer2 - Handle error path in certain freemap sequences
* Portions of the freemap handling code issue hammer2_chain_modify()
but do not process a non-zero error return.
* Generally speaking, because freemap blocks are algorithmically
allocated and non dynamically allocated, the "allocation" can not
fail. But it is possible to contrive situations where the freemap
is corrupted to the point where it does.
Process the error path(s) anyway
Reported-by: afranke (Andreas Franke) using AI operational analysis
DragonFly-PR: 3407
[Instrumentor][test] Ensure dir is writeable (#196466)
When running the test in a runner where the source directory is read
only, this test fails w/ `error: failed to open instrumentor stub
runtime file for writing: Permission denied`. Run the test in a
writeable test dir `%t` to ensure we can actually write to the current
directory.