A failed read of the sites entitlement tells the member they have reached their site limit #231
Closed
opened 2026-10-16 02:59:51 +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
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#231
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
Before a site create, the create workflow asks
CheckQuotaActivity(internal/integrations/fedwiki/workflows/activities.go:581) whether the workspace may have another site. The activity reads three things: the workspace's pool, the pool'sfedwiki_sitesentitlement and the pool's usage. A failed read of the pool or of the usage returns an error, and the workflow then fails the request asquota_unavailable(internal/integrations/fedwiki/workflows/requests.go:319-322), which the member reads as "Couldn't check your site limit. Try again later."A failed read of the entitlement is handled differently. Any error from
GetNumericEntitlementByPoolAndResource(activities.go:602-614), not only "no row", is answered as a quota of 0 withCanCreatefalse, and logged at Info as "no sites entitlement found" without the error. The workflow then declines the request assite_limit_reached(requests.go:323-325), and the member reads "You have reached your site limit." (internal/integrations/fedwiki/web/requests.go:37).What should happen
Only a pool that has no
fedwiki_sitesentitlement (sql.ErrNoRows) is answered as a quota of 0. Any other error from that read returns an error, as the pool and usage reads do, so the request fails asquota_unavailableand the member is told the limit could not be checked.Where
internal/integrations/fedwiki/workflows/activities.go:602-614,CheckQuotaActivityinternal/integrations/fedwiki/workflows/requests.go:319-325, the create workflow's use of the answerSteps
Found by reading the code; not reproduced.
Why it matters
A member under their limit is told they have reached it, and the request is declined rather than failed, so nothing tells them to try again. The log line that would explain it says no entitlement was found and drops the error.
Fixed in
9027c0b1:CheckQuotaActivityanswers "no entitlement" only when the pool has no sites entitlement, and returns any other read failure, so the create ends failed withquota_unavailableand the notice " wasn't created. Couldn't check your site limit. Try again later." The slot gate and every quota read now follow the same rule throughusage.Limit.