Nemo157
Nemo157
Sorry about the delay, I finally got around to rebasing and implemented both suggestions from above.
I think it would be worth merging a zstd update and pushing that before going to 0.4, so that there's less pressure on downstream updating.
This appears to have been fixed by cc7b192f935bd27c30f1bc4ee6dd2a5aed53b900
This is actually fixed in master, by df2e3d43aafc3966f0789d678975ebf2011bb10b
It is my understanding boats cannot work on open source projects currently, so I have published a fork of `fehler` with the changes from master and integrating fixes for I...
Would it be useful to have a list of known undetected breakages to test against too? isn't detected currently and doesn't appear to match any of the checks in the...
Rather than being a list of checks, just a list of version pairs that have seen known ecosystem breakage, but pass all current checks. Maybe even something that can run...
I was just looking at using syncthing to synchronize the existing directories, and the major issue I notice is that both the persistent data and caches are put in the...
I don't think it's possible to import a generated config file, because that contains a randomized private key. The provider needs to support uploading the existing public key from the...
> Either you configure it completely manually, exporting private keys from tailnet nodes and importing them into the WG node which is annoying Just to clarify, you need to export...