| 12 May 2025 |
 nim65s | I have a bunch of eg.
inputs.patch-arsenik = {
url = "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch";
flake = false;
};
in the flake for my systems, applied with patchedNixpkgs = inputs.nixpkgs.legacyPackages.x86_64-linux.applyPatches { src = inputs.nixpkgs; patches = [ inputs.patch-arsenik ]; };, for some of my PRs I want in my pkgs but are not merged. This allow to have up-to-date patches with low effort.
But recently, github rate limits have been hitting me on like 100% of my nix flake update. Anybody has a workaround ?
| 16:35:42 |
| nim65s | If I could set an access token on githubusercontent, it would work (eg. as in curl "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch?access_token=$GITHUB_TOKEN"), but I have no idea how to configure that without exposing the token directly in my flake.nix, which is a public file | 16:39:36 |
| nim65s | * I have a bunch of eg.
inputs.patch-arsenik = {
url = "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch";
flake = false;
};
in the flake for my systems, applied with patchedNixpkgs = inputs.nixpkgs.legacyPackages.x86_64-linux.applyPatches { src = inputs.nixpkgs; patches = [ inputs.patch-arsenik ]; };, for some PRs I want in my pkgs but are not merged. This allow to have up-to-date patches with low effort.
But recently, github rate limits have been hitting me on like 100% of my nix flake update. Anybody has a workaround ?
| 16:41:03 |
 dramforever | In reply to @gsaurel:laas.fr
If I could set an access token on githubusercontent, it would work (eg. as in curl "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch?access_token=$GITHUB_TOKEN"), but I have no idea how to configure that without exposing the token directly in my flake.nix, which is a public file for flake inputs you're in luck, you can set the access-tokens nix option | 17:04:03 |
| dramforever | oh wait hmmm | 17:04:25 |
| dramforever | yeah i posted too quick and didn't notice you're using https on a github url... | 17:06:19 |
| nim65s | I tried access-tokens = github.com=ghp_… patch-diff.githubusercontent.com=ghp_…, but it didn't work, and I found in the doc that it is like only for specific to github/gitlab things, so this probably won't work with a random thing | 17:08:16 |
| dramforever | tbh, i'm mostly surprised this even works. having non-pinnable https inputs is a surefire way to make your old flake revisions non-reproducible | 17:10:52 |
| dramforever | it'll fail the flake.lock check forcing you to update | 17:11:36 |
| 13 May 2025 |
|  codgician joined the room. | 08:51:52 |
|  GladiatorEntred joined the room. | 09:21:46 |
| GladiatorEntred set a profile picture. | 09:25:18 |
