Skip to content

Status: the third many-people round, and the join fix on its own #322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renrenmimi merged 1 commit into from
Oct 14, 2026
Merged

Status: the third many-people round, and the join fix on its own #322

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion STATUS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,24 @@
审查目录里的 `evidence/ios-native/acceptance-status.md` 是**第一阶段验收矩阵**（按
`SWIFT-CLIENT-ACCEPTANCE.md` 条目编号记证据），不是状态表；功能迁移进度只记在这里。

**更新** 2026-10-14 · **第二轮多人测试做完**：同时抢一个名字、删帖删宠物时别人正在操作、几个共同主人同时退出等 7 类，200 人同时；查出的 3 个问题修好后全部正确，修复当天第三次部署到正式环境、核对过 · 手机上的审计包 `db2d69c` 签名到 10-20 · 没有发布到 App Store
**更新** 2026-10-14 傍晚 · **第三轮多人测试做完**：聚会取消、邀请码作废时别人正在操作都没问题；200 人抢名额时偶尔有人看到「内部错误」，已修好并单独上线 · 报名被拒的提示按手机语言显示（下次装机生效） · 手机上的审计包 `db2d69c` 签名到 10-20 · 没有发布到 App Store

---

## 10-14 傍晚：第三轮多人测试，和单独上线的报名修复

时间都是太平洋时间。

| 场景（200 人同时） | 结果 |

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the 200-user concurrency claim

This heading says every listed scenario used 200 people simultaneously, but the invitation-revocation scenario in functions/scripts/scenario-many-users.mjs:718-724 selects exactly three redeemers with outsiders.slice(-4, -1), races only those requests against the revocation, and sends the fourth redemption after that race finishes. This provides four concurrent operations rather than a 200-person test, so the canonical status table materially overstates the coverage; either run the scenario with the intended crowd or report its actual concurrency.

Useful? React with 👍 / 👎.

| --- | --- |
| 有人在报名时聚会被取消 | 取消之后再报名一律被拒；名单和人数一致 |
| 有人在用邀请码时邀请码被作废 | 最多进 1 个人；作废之后谁也进不来 |
| 200 人抢 20 个名额（复查） | 修好前，没抢到的 180 人里有 2 人看到「内部错误」：人太多，数据库放弃了这两次报名，时有时无。修好后 180 人都看到「聚会已满」 |

- **修复（#321）**：报名碰到「很多人同时改同一份数据被放弃」时，等一会儿再试，和计数用的是同一套。13:49 你单独部署了这一个函数：版本号加 1，配置没变，线上代码和部署包逐字节相同，之后没有报错。这次改到的共用代码只是整理，不改变行为，所以别的函数不用重新部署。
- **App（#319）**：报名被拒时，服务器给的英文原话（比如「Meetup is full.」）现在按手机语言显示，新增了 3 条中文。单元测试 1077 条全过，下次装机生效。
- **已知小瑕疵，没改**：别人抢先用掉邀请码的同一瞬间点作废，作废的人会看到「已作废」，但对方已经加入了。结果本身是对的，家庭成员列表里能看到他。
- **测试脚本**：新加的两项在 #320。

---

Expand Down
Loading