Nick Cao

A staging branch would also be nice for scenarios like https://github.com/NixOS/nixpkgs/pull/158455#issuecomment-1038532832.

Due to the cryptokey routing nature of wireguard, it's bound to be a tough task to integrate any routing daemon with wireguard without efforts from their side. I checked the...

For the configuration interface part, forgive me for not clarifying, as all required is a specification for the protocol, especially the response, so that writing interoperable software involves less guesswork....

I've been syncing interfaces with a custom daemon, and it works pretty well. I believe that a simple shell script can also do the trick. Specifying interfaces with glob or...

The main reason that people do not want to generate a new config and simply do a restart is that it would disrupt traffics and cause route flapping. If some...

vendorSha256 can be computed (or built) from `go.sum` alone, just like with `Cargo.lock`, however the process is harder due the the obscure tree hashing scheme of go modules. A somehow...

To make the situation worse, `go.sum` generated by go pre 1.16 and go 1.17 differs slightly and is generally incompatible.

With the introduction of impure derivations in recent versions of nix, the approach in https://gist.github.com/NickCao/e2135fae47b31798c5d03cae1d242cb3 is now feasible (without considering pouring tens of thousands of derivations into your nix store).

My guess would be nix starting the next build too early before the outputs of the previous build is properly registered.

Maybe it requires a combination of heavy load and large derivation to trigger, what about limiting the cpu usage with cgroups and try again?