A request that runs longer than eight seconds loses its answer, though the console lets it run for 32 #290
Closed
opened 2026-10-29 07:34:03 +00:00 by cgalo5758
·
1 comment
Labels
Clear labels
accessibility
area/billing
area/catalog
area/discourse
area/domains
area/entitlements
area/fedwiki
area/identity
area/integrations
area/licensing
area/member-ui
area/meta
area/operator-ui
area/ops
area/testing
duplicate
good-first-issue
invalid
privacy
security
upstream
wontfix
A barrier for people using assistive technology or a keyboard alone.
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
Products, prices, plan ladders, purchasability.
The Discourse integration.
The domains registry, claims, placements, the certificate ask.
Entitlement sets, rules, grants, pools, provisioning.
The Federated Wiki integration and farm sync.
Sign-in, sessions, persons, organizations, workspaces, roles.
The provider registry, outbox and webhooks in general.
Licenses, the contributor agreement, SPDX headers.
Member pages.
The repository itself, its contributing guide, CI, the tracker and the workflow.
Operator pages, forms, lists, the design system.
Deployment, configuration, migrations, workflows, instance settings.
The test stack, screens, lint, walkthroughs.
Closed because another issue already covers it.
Small, self-contained, and explained enough to be a first contribution.
Closed because it is not a ticket for this repository.
Touches what a person's data reveals.
Touches authentication, authorization, secrets or data exposure.
Waits on another repository or project before it can move.
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
Milestone
No items
No Milestone
Public launch
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#290
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What happens
The server stops writing a response eight seconds after it read the request (
WriteTimeout), while the handlers run under a 32-second request timeout (middleware.Timeout). A handler that takes longer than eight seconds still runs to the end, and its writes to the database and to Stripe land, but its answer never reaches the browser: the member sees neither the result nor an error. A plan change makes up to three Stripe calls today, and the switch of a paused plan (#278) up to eight, so a slow Stripe can push one past eight seconds.What should happen
The time the server allows for writing an answer covers the time a handler may run, so every request the console lets run gets its answer or its timeout page.
Where
internal/server/server.go: thehttp.Server'sWriteTimeout, andmiddleware.Timeoutin the handler chainWhy it matters
A member whose plan changed, or whose card was declined, can be left with no answer at all.
A request whose handler took longer than eight seconds lost its answer: the server stopped writing eight seconds after it read the request, while the handler was allowed 32 seconds. A plan change during a slow Stripe call, or a FedWiki request that waited on a site's retention purge, did its work and showed the member nothing. The server now keeps writing for 40 seconds, the 32 a handler may run and 8 more for the answer, so such a request shows its result, and one still running at 32 seconds shows the timeout error, which was lost before as well. The same holds for a request that waits on a Temporal call, such as starting a grant's expiry or signalling a domain claim, each of which can take up to 10 seconds. Neither limit is a setting. A proxy in front of the console needs to wait at least 40 seconds for an answer; the deployment guide says so.
Commit:
1d35f03860