morguldir
f43c09b05d
ci: pin cache-nix-action
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-07-03 06:13:39 +02:00
morguldir
b035cd7cbe
ci: remove detsys from documentation/build workflow too
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-07-03 04:51:59 +02:00
morguldir
b7aa79884d
ci: try out cargo caching
2024-07-03 03:39:49 +02:00
morguldir
9c6cc44abb
ci: use correct config file
...
also had to try putting it at the end again
2024-07-03 01:56:14 +02:00
morguldir
9c0d7b1da0
ci: change to cache-nix-action
2024-07-03 01:08:30 +02:00
morguldir
fb758f5f4b
chore(deps): bump Cargo.lock (subtle crate was yanked)
2024-06-27 17:41:13 -04:00
morguldir
5d138a7e5e
ci: skip development.md file when running lychee
2024-06-27 17:41:13 -04:00
morguldir
563618cc9e
ci: free disk space before starting tests
2024-06-27 17:41:13 -04:00
morguldir
0a28d80cf2
ci: try another upstream cache
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-06-27 17:41:13 -04:00
morguldir
9aa372d83b
nix: Allow excluding features, allow disabling release_max_log_level
2024-05-24 15:12:23 -04:00
morguldir
5893901a75
Explicitly include snappy as well
...
Not sure what changed that we need this
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-05-24 12:46:15 -04:00
morguldir
8ba9b33a95
Make sure we use the liburing of the platform we're building for
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-05-24 12:46:15 -04:00
morguldir
70047ff26d
Make rocksdb include liburing, and tell gcc the path during the build
...
With: strings /nix/store/9skicdac6xs4yww1nd3h7m6xydv4hxlj-rocksdb-9.1.1/lib/librocksdb.so.9|rg io_uring|wc -l
112
With: strings result/bin/conduit |rg io_uring|wc -l
5
Without: strings static-x86_64-unknown-linux-musl-jemalloc |rg io_uring | wc -l
0
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-05-24 12:46:15 -04:00
morguldir
9f19a2025d
Revert "feat(membership): check if user already has the membership that is requested to be set"
...
This reverts commit 321a6ca0fe .
These checks were not working as intended, resulting in the unban button not working
The join check gets kept since it slightly reduces the amount of sent joins in some cases
This check will probably be replaced soon for a more universal solution to the "made no change" issue
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-05-10 22:52:44 -04:00
morguldir
6c0d527b90
Use jemalloc/hmalloc for cross builds
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-04-26 02:03:40 -04:00
morguldir
056c9d6920
Since we use crane.buildPackage we need to use cargoExtraArgs
...
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-04-26 02:03:40 -04:00
morguldir and AwesomeQubic
3ebf1082d6
Base oci-images on their matching alloc variant
...
Co-authored-by: AwesomeQubic <ThatQubicWah@protonmail.com >
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-04-26 02:03:40 -04:00
morguldir
32eb568909
Remove extra test flag when publishing to ghcr in the CI
...
test -n checks if a string is longer than non-zero, but we just need a compare
Signed-off-by: morguldir <morguldir@protonmail.com >
2024-04-26 02:03:40 -04:00
morguldir
b303a774d8
Set the time of the HEAD commit as the OCI created field
...
Apparently it uses `date -Iseconds` to parse, so we can use @ with a timestamp
Also it doesn't parse `created` in buildImage, only buildLayeredImage
Signed-off-by: morguldir <morguldir@protonmail.com >
Signed-off-by: strawberry <strawberry@puppygock.gay >
2024-04-17 14:51:08 -04:00