Raise the ats body cap to 96 MB, retry Greenhouse without content=true

openings.go's 8 MB cap was written against arbitrary URLs; every URL here is
on a fixed allow-list of seven ATS hosts, and the real pull of 2026-09-23
refused Anduril, Anthropic, OpenAI, Databricks, Carvana, Axon and Airwallex
for it. A board that still exceeds 96 MB now retries once without
content=true (Greenhouse only), trading the description for the listing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Sonnet 5 committed 2026-09-23 11:39:39 +02:00
1 parent 078fb8ff8f
commit 867ebe6405
3 files changed
+85 -8

No files matched your search

+9
View File
@@ -38,6 +38,15 @@ What was decided for roledesk and the one reason for each. The longer reasoning
**The 8 MB cap and `?content=true` fight each other on the largest boards, and the cap won.** Both are named in the plan — the cap from openings.go, `content=true` so Greenhouse ships the description inline — but jobhunt-hq's own feeds never asked for content, so it never hit the size this combination produces. The real run (2026-09-23) refused seven boards outright for it: Anduril at 41 MB, and Anthropic, OpenAI, Databricks, Carvana, Axon and Airwallex between 9 and 19 MB, each because the biggest employers publish the most roles with the longest descriptions. Left as is, because raising the cap only moves the line and a company that big is exactly the case `openings.go`'s cap was written against; a real fix — retry without `content=true` when the capped response is refused, trading the description for at least the listing — is a follow-up, not a guess made here.
**The cap is raised to 96 MB, with one retry for Greenhouse.** The follow-up
the entry above deferred. Every URL `ats` fetches is on a fixed allow-list of
seven ATS API hosts, not an arbitrary one, so the cap openings.go wrote
against arbitrary URLs was the wrong number to port unchanged. 96 MB fits
every board seen so far, including Anduril's 41 MB; a board that still
exceeds it retries once without `?content=true` (Greenhouse only, since that
is the one host whose feed URL carries the flag), trading the description for
at least the listing.
**Workable's shape is confirmed, not a populated example.** Every slug tried against `apply.workable.com/api/v3/accounts/{slug}/jobs` during this build returned the documented `{"total": 0, "results": []}` before Cloudflare rate-limited further requests from this session, so the parser is written from Workable's long-published job object rather than from a fetched row. Worth a fixture-level recheck against a live board with open roles the next time this plugin is touched.
## Ranking