fix: mistyped Accept header? #14

Merged
jalil merged 1 commit from push-rnqtkllpvopp into main 2025-03-10 23:42:24 +01:00
Owner

For some reason forgejo returns HTML from a comment update request.

For some reason `forgejo` returns HTML from a comment update request.
jalil self-assigned this 2025-03-10 23:26:19 +01:00
jalil added 1 commit 2025-03-10 23:26:19 +01:00
fix: mistyped Accept header?
All checks were successful
/ check (treefmt) (push) Successful in 3s
/ check-renovaterc (push) Successful in 3s
/ report-size (push) Successful in 1s
18b0da5f8f
For some reason `forgejo` returns HTML from a comment update request.
First-time contributor

Flake output sizes

Definitions
  • Name: the name of the package/configuration.
  • Size: the closure size (size on disk/NAR size + all transitive dependencies).
  • NAR Size: the size of the build output (package without the dependencies).
  • [NAR] Size Change: the amount changed compared to the main branch.
Tips on reading this data
  • For NixOS configurations you generally care only about the Size (closure size/size on disk).
    • Reduce the Size by disabling unneeded services/default packages.
  • For Packages you care about both the Size and the NAR Size.
    • Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
    • Reduce the Size by reducing the dependencies (e.g. buildInputs).
    • Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

Packages

Name Size Size Change NAR Size NAR Size Change
hello 32MiB 0B 230KiB 0B
<!-- AUTOGENERATED by nix-flake-outputs-size action --> ## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `hello` | 32MiB | 0B | 230KiB | 0B |
jalil force-pushed push-rnqtkllpvopp from 18b0da5f8f to 60439e3b11 2025-03-10 23:30:26 +01:00 Compare
jalil force-pushed push-rnqtkllpvopp from 60439e3b11 to 62ff83fb75 2025-03-10 23:34:16 +01:00 Compare
jalil force-pushed push-rnqtkllpvopp from 62ff83fb75 to caba5a8cd6 2025-03-10 23:36:23 +01:00 Compare
jalil force-pushed push-rnqtkllpvopp from caba5a8cd6 to ac84507e43 2025-03-10 23:37:38 +01:00 Compare
jalil force-pushed push-rnqtkllpvopp from ac84507e43 to e56abf9f93 2025-03-10 23:38:46 +01:00 Compare
jalil force-pushed push-rnqtkllpvopp from e56abf9f93 to 0a637165fe 2025-03-10 23:39:57 +01:00 Compare
jalil merged commit 0a637165fe into main 2025-03-10 23:42:24 +01:00
jalil deleted branch push-rnqtkllpvopp 2025-03-10 23:42:24 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jalil/nix-flake-outputs-size#14
No description provided.