enricobuehlerandClaude Fable 5 d83eeedde4 ci(flatpak): drop the use-vc TCP-DNS hack — the runner-side cache made it the failure ...

Every flatpak Tooling failure on 2026-07-22 (4 runs, incl. two AFTER the
runner fleet got its local dnsmasq cache) died in flatpak remote-add with an
instant 'Could not resolve hostname' ×10 while dnf in the SAME container
resolved fine. The one thing only this leg does is force glibc onto TCP DNS
(use-vc) — a 2026-07-11 mitigation for the embedded resolver dropping UDP
under fleet load. With job containers now resolving against the on-box
dnsmasq cache (daemon.json dns → docker0), UDP is reliable again and the TCP
path through the same chain is the flaky one under concurrency. Remove the
hack; keep the nss-resolve drop and retry.sh as the backstop.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-23 00:27:52 +02:00

..

ISSUE_TEMPLATE

feat(security): finish Windows firewall Public opt-in wiring + vuln-disclosure + doc cleanup

2026-07-03 14:08:17 +00:00

workflows

ci(flatpak): drop the use-vc TCP-DNS hack — the runner-side cache made it the failure

2026-07-23 00:27:52 +02:00