simpletest/who_need_help
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh release and rate-limit evidence

Browse Source
This commit is contained in:
SimpleTest 2026-08-26 03:58:12 +03:00
parent acccb140b8
commit 0d5130fcd9
3 changed files with 15 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
android/play-store/closed-test.md
View File

@ -5,7 +5,7 @@ least 12 testers to remain opted in to the closed test for 14 continuous days
before production access can be requested.
This requirement was rechecked against the official Play Console Help article
on 2026-08-25. The Console remains the source of truth for the account's actual
on 2026-08-26. The Console remains the source of truth for the account's actual
eligibility and the date on which production access can be requested.
## Before inviting testers

6
android/play-store/release-checklist.md
View File

@ -213,9 +213,9 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
On 2026-08-25 the existing **Closed testing - Alpha** track was inactive with
zero of four setup tasks complete. Countries and testers were not selected, and
the track had no release. The current official requirement for this personal
developer account was rechecked as at least 12 testers continuously opted in
for at least 14 days before applying for Production access. No Closed or
Production release was created during this inspection.
developer account was rechecked again on 2026-08-26 as at least 12 testers
continuously opted in for at least 14 days before applying for Production
access. No Closed or Production release was created during this inspection.
## Publishing

11
docs/performance.md
View File

@ -461,6 +461,17 @@ host. It is not a production capacity claim and does not justify a hard startup
guard. The much slower hot-scope result is expected contention on one database
row; ordinary email/IP policy traffic distributes attempts across many scopes.
The same checked-in benchmark was repeated on 2026-08-13 with the same explicit
one-CPU, PostgreSQL 18.4, 5,000-call and concurrency-20 boundaries. The hot
scope completed in 12,625.396 ms (396.03 operations/s); 5,000 distributed
scopes completed in 852.909 ms (5,862.29 operations/s). Both profiles reported
5,000 successful calls, zero failures, zero unexpected limited calls, exactly
5,000 persisted increments, and zero run-owned buckets after cleanup. The
generated JSON is retained under the ignored local directory
`output/rate-limit/20260813073442-3329179/`. This repetition strengthens the
implementation and cleanup evidence; it still does not select or approve the
product-facing thresholds.
## Observed local comparison
Observed on 2026-07-18 with Docker Engine 29.6.2 on the recorded 32-CPU,