Skip to content

Fetch server-info endpoints sequentially with per-endpoint degradation - #8

Merged
plusky merged 1 commit into
mainfrom
fix/server-info-sequential
Jul 27, 2026
Merged

Fetch server-info endpoints sequentially with per-endpoint degradation#8
plusky merged 1 commit into
mainfrom
fix/server-info-sequential

Conversation

@plusky

@plusky plusky commented Jul 27, 2026

Copy link
Copy Markdown
Owner

Found by a read-only smoke test against a real Bugzilla (apibugzilla.suse.com): the deployment drops one of four concurrent connections from a single client, which made bugzilla_server_info fail wholesale. Sequential fetch + graceful per-endpoint degradation (sanitized reasons under unavailable, hard error only if all four fail). Removes the now-dead Join2 combinator; adds a README note about bot-walled interactive hosts vs dedicated API hosts. Verified live: full server_info payload from Bugzilla 5.0.6 after the fix.

A live smoke test against apibugzilla.suse.com showed the deployment
dropping one of four connections opened concurrently by one client,
which failed the whole bugzilla_server_info tool. Fetch the four
endpoints one at a time instead, degrade a failing endpoint to null
fields with the sanitized reason under "unavailable", and error only
when every endpoint fails. Drops the now-unused hand-rolled Join2
combinator. Also add a README note about instances whose interactive
host sits behind an anti-bot challenge and expose a dedicated API
host.
@plusky
plusky merged commit c660cca into main Jul 27, 2026
10 checks passed
@plusky
plusky deleted the fix/server-info-sequential branch July 27, 2026 14:14
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.

1 participant