Hugo Herter
Hugo Herter
That's great, looking forward to it ! Not allowing hard resets on the main branches solves the unauthorized rollbacks, good to read that this is handled already.
What about reusing the template from https://github.com/aleph-im/aleph-client/pull/244/files instead of the generic one ?
I restarted the test that failed.
Apparently a `postrouting` chain would already have bee configured by Libvirt: ``` table ip6 nat { chain LIBVIRT_PRT { } chain POSTROUTING { type nat hook postrouting priority srcnat; policy...
This is apparently due to Libvirt being installed on the machine, conflicting on the NFTables rules.
Thanks for the positive feedback. Another motivation is to package pytezos (or at least the cryptography part) in Nixpkgs, which has [libnacl already packaged](https://search.nixos.org/packages?channel=24.05&from=0&size=50&sort=relevance&type=packages&query=libnacl) but not `pysodium`
@olethanh I moved the resource limits into this branch.
There were exciting discussions about this topic during the Matrix sprint before FOSDEM this year, has anything progressed on this side?
Thanks, but my goal is to install Unsloth from the source repository instead of installing pre-built wheels from PyPI. The context is that I am packaging Unsloth on NixOS in...
See also GitHub's documentation on publishing releases: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository This would help users follow new releases through GitHub and relies on Git tags for versions.