!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

388 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.121 Servers

Load older messages


SenderMessageTime
4 Aug 2025
@vcunat:matrix.orgVladimír ČunátThe links on that page are "generic". Lots of the stuff doesn't exist.13:37:12
@vcunat:matrix.orgVladimír Čunát* The links on that page are "generic". Lots of the stuff intentionally doesn't exist.13:37:27
@hexa:lossy.networkhexagraphical never, only minimal 13:38:32
@vcunat:matrix.orgVladimír ČunátRedacted or Malformed Event13:38:45
@hexa:lossy.networkhexafrankly, I don't know why we have the trailing slash prefixes13:38:57
@vcunat:matrix.orgVladimír ČunátOops. I thought I was wrong. Let me repost. Maybe it's better to use links like https://releases.nixos.org/?prefix=nixos/25.05-small/ ?13:40:06
@sandro:supersandro.deSandrotrue, especially since the combined ISO13:40:27
@djacu:matrix.orgdjacuSorry. By source of truth we meant that we don't want people to treat where the logo files are in the website as stable paths for linking. E.g. the Infra and Nixpkgs README files were previously linking to paths in the website to display the logo in the readme. The goal would be serving up the branding artifacts (currently just logos and branding guide PDF) to a location where we can use it for the website and repos can use it for their README15:33:51
@jfly:matrix.orgJeremy Fleischman (jfly) djacu, that makes sense! Pick the tech you want to use, and let us know how we can help. I imagine at the very least you'll need a DNS entry. Feel free to send us a PR (relevant code here), or just ask for help here. 16:43:15
@sandro:supersandro.deSandroIs it just me or is hydra currently insanely slow? every request takes like 10s17:55:58
@hexa:lossy.networkhexahttps://grafana.nixos.org/d/fejx5cl0i0s1sb/anubis?orgId=1&from=now-24h&to=now&timezone=utc&var-site=hydra.nixos.org:9001&viewPanel=panel-318:08:36
@hexa:lossy.networkhexaCan take a look in 30m18:08:53
@sandro:supersandro.deSandrohmmm, so someone or something is doing lots of load currently...18:20:40
@paperdigits:matrix.org@paperdigits:matrix.org left the room.18:25:20
@hexa:lossy.networkhexa700+ source addresses hammering out over 2.7million requests18:48:01
@hexa:lossy.networkhexaover 600k 429 responses18:48:06
@hexa:lossy.networkhexasource seems to be tor, but there is an email address in the user-agent18:48:16
@emma:rory.gay@emma:rory.gaypersonally i'd just throw up a few temporary iptables rules18:52:28
@hexa:lossy.networkhexayeah, I'm temporarily blocking tor exits18:53:12
@hexa:lossy.networkhexathe requests stopped a minute after I sent the mail18:57:02
@hexa:lossy.networkhexaalso boo, we're still using iptables18:57:17
5 Aug 2025
@emma:rory.gay@emma:rory.gayor youre using the nftables wrapper lol02:59:30
@hexa:lossy.networkhexathe nixos default 🤷03:00:29
@hexa:lossy.networkhexaquite a bit of technical debt in there03:00:51
@emma:rory.gay@emma:rory.gayyeah, thats the nftables wraper03:02:10
@emma:rory.gay@emma:rory.gay iptables v1.8.11 (nf_tables) 03:02:18
@emma:rory.gay@emma:rory.gayglad that still exists because i have no clue how to manage nftables03:02:46
@hexa:lossy.networkhexa
  systemd.services.nft-update-tor-exits = {
    wantedBy = [ "nftables.service" ];
    after = [ "nftables.service" ];
    startAt = "hourly";
    script = ''
      curl -sSL "https://check.torproject.org/cgi-bin/TorBulkExitList.py?exit" | sed '/^#/d' | while read IP; do
        nft add element inet filter torexits { $IP } 
      done
    '';
    path = with pkgs; [
      curl
      nftables
    ];
  };
03:10:29
@hexa:lossy.networkhexa
        set torexits {
          type ipv4_addr;
          flags dynamic, timeout;
          timeout 6h;
        }
03:11:00
@hexa:lossy.networkhexabasically you can create a datatype, e.g. a set03:11:06

Show newer messages


Back to Room ListRoom Version: 6