Skip to content

Keep a resolver out of the egress shape tests - #201

Merged
patchstackdave merged 1 commit into
mainfrom
fix/shape-tests-need-no-resolver
Sep 2, 2026
Merged

patchstackdave merged 1 commit into
mainfrom
fix/shape-tests-need-no-resolver

Conversation

@patchstackdave

@patchstackdave patchstackdave commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor

These rule-shape tests verify hostname and literal-address matching without DNS-derived evidence. Their helper disables DNS screening, making the cases deterministic and preventing resolver access. DNS-derived behavior remains covered separately with explicitly supplied addresses.

These cases time out under a slow resolver, which is what a CI runner sometimes has.
The guard screens a hostname by resolving it, and the destinations here are either
literal IPs — which never reach a resolver — or names that do not exist, so a live
lookup adds a network round trip to every case and decides none of them.

With DNS screening off the guard builds no resolver at all, and the hostname and
address rules these tests are about still apply. What the screen does with an address
it resolves is `egress-dns.test.ts`, which builds the guard directly and injects the
addresses it is asking about.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderbuds

coderbuds Bot commented Sep 1, 2026

Copy link
Copy Markdown

Clear test update adds context comments to disable DNS resolver.

🎯 Quality: 91% Elite · 📦 Size: Small

📈 This month: Your 155th PR — above team average · Averaging Excellent

See how your team is trending →

@patchstackdave

Copy link
Copy Markdown
Contributor Author

/review

@patchstackdave
patchstackdave merged commit edd9b1c into main Sep 2, 2026
14 checks passed
@patchstackdave
patchstackdave deleted the fix/shape-tests-need-no-resolver branch September 2, 2026 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants