tomberek

What endpoints are valid at that host?

Occasionally running this works as well. ``` $ security find-certificate -a -p /System/Library/Keychains/SystemRootCertificates.keychain | sudo tee /etc/ssl/certs/ca-certificates.crt $ security find-certificate -a -p /System/Library/Keychains/System.keychain | sudo tee -a /etc/ssl/certs/ca-certificates.crt $ sudo...

Needs a decision to either merge or close. How is the experience for those who have been carrying this patch?

Idea approved. This is ready for wider review and testing against Nixpkgs and larger workloads. Small changes for docs requested above and test fixups. Assigning @edolstra for review.

Idea has been approved. I'm not aware of any objections. Logs for Linux failure are no longer available, but it seems like something that can be fixed addressed.

2. Remote builds get their core numbers locally or from a machines file. 3. Make takes a "-l" with no number as removing any setting. These are unfortunate conventions. So...

There is some interaction with: https://github.com/NixOS/nix/pull/13402

### PosixAccessor calls assertNoSymlinks too often? ```python [ RUN ] PrimOpTest.unsafeGetAttrPos unknown file: Failure C++ exception with description "error: … while calling the 'unsafeGetAttrPos' builtin at «string»:1:1: 1| builtins.unsafeGetAttrPos "y"...

### Unable to find input at specified path ```python +(follow-paths.sh:80) nix flake metadata /tmp/nix-shell.yXAp0S/nix-test/flakes/follow-paths/follows/flakeA warning: Git tree '/tmp/nix-shell.yXAp0S/nix-test/flakes/follow-paths/follows/flakeA' is dirty error: … while updating the lock file of flake 'git+file:///tmp/nix-shell.yXAp0S/nix-test/flakes/follow-paths/follows/flakeA'...

Next steps: - rebase - resolve remaining test failures - flake regression suite - long-term testing, rc? Or at beginning of release cycle. - announce in Discourse to get testers...