Repository navigation
fix(mobile): join an open channel from the chat footer - #9253
Conversation
|
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a503618e7f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fae660296e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
🔐 Codex Security Review
Review SummaryOverall Risk: NONE
FindingsNo concrete security, correctness, or reliability findings were identified. Notes
Generated by Codex Security Review | |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5b6064229d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
5b60642 to
1b61947
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b619472cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
jedwards27
left a comment
There was a problem hiding this comment.
🤖 :bot: Jude’s code review agent — REQUEST CHANGES
Reviewed base 8cce12f591988f29cc2beab5ff0c89d51862f31b to head 1b619472cda1182296c897a33e07c6facd4b9b15. This joins a channel from the mobile footer and changes the read-after-write membership contract. The following source-traced cases need attention:
-
[P2] A confirmed join can settle without updating the UI.
channel_management_actions.dart:238–240,392–400calls the best-effortrefresh;channels_provider.dart:1033–1057returns normally when disconnected, retired, or a fetch fails. After a confirmed roster, the footer can therefore re-enable Join without feedback while its cached channel remains a nonmember; the details-page caller can also close as if successful. Propagate or reconcile the result and verify that membership was installed before treating the operation as complete. Add a production-seam regression for failed/retired refresh and visible recovery, plus a successful strong-membership refresh assertion. The current footer success test supplies fake actions, and the action test only exercises exhausted confirmation. -
[P2] A later replica read can undo the confirmed join. The join refresh requests strong membership reads, but a later notice, foreground resume, or reconnect may trigger an ordinary list read:
channels_provider.dart:980–989,channels_provider_lifecycle.dart:285–301. If the replica still lacks the new roster, that newer request installs a nonmember snapshot and the composer disappears again; the read can also be marked as covering the notice. Preserve read-your-writes through subsequent refreshes without hiding a genuine later removal, and test a writer-visible/replica-stale join followed by a later ordinary refresh and eventual reconciliation. -
[P2] Distinguish acceptance from failure.
_confirmJoinedruns only after submit returns, but a failed query or exhausted confirmation is caught by the new footer and shown asCouldn’t join … Try again. The membership may already exist. In particular, the relay commits membership before best-effort roster emission, and an already-member retry returns before re-emission (side_effects.rs:2966–2985,3014–3016); resending is not a universal recovery. Represent accepted-but-unconfirmed separately from an actual rejection, give accurate next-step guidance, and test both outcomes. A durable repair for a missing relay roster is a pre-existing relay follow-up, not a demand to redesign the relay in this mobile PR. -
[P2] The new posting promise is false for guest-join channels.
banners.dart:11–12,31–35promises sending for every open channel, but self-join can grantguest(side_effects.rs:2975–2984), and guests cannot post (ingest.rs:996–1026). The pre-existing composer checks membership rather than posting role, so this new one-tap path can invite users to compose only to have the relay reject the send. Make the new copy and resulting affordance accurate for guest joins; cover guest and ordinary-member journeys.
Scope: Leave’s ordinary refresh and the relay’s missing-roster repair gap predate this PR; consider them separate follow-ups, not independent blockers here.
Evidence and verification: source review at the clean pinned head; git diff --check 8cce12f591988f29cc2beab5ff0c89d51862f31b 1b619472cda1182296c897a33e07c6facd4b9b15 passed. GitHub CI run 42532167759 passed at the exact head, including mobile checks and three mobile test shards. The PR body separately reports a local full-suite failure that passed when rerun alone. The failure scenarios above are source-traced, not independently reproduced; this review did not run a local suite, simulator, accessibility, or mutation checks. Author owns fixes and causal regressions; reviewer/CI owns independent full-suite and exact-artifact native/accessibility verification. Host capacity and simulator availability are verification gaps, not additional defects.
|
🤖 Meli, Tyler’s AI agent, posting on his explicit behalf. The new footer conflates an accepted-but-unconfirmed join with a rejected join by showing “Couldn’t join. Try again.” Please distinguish those outcomes, as the current desktop flow does, and cover the unconfirmed state. A separate, pre-existing relay recovery gap can make retries ineffective when membership has committed but discovery/roster emission failed and no later repair occurs: the already-member path returns without re-emitting it. That deserves a follow-up; an unconfirmed result alone does not establish a permanent dead end. Leave confirmation parity is recommended as a separate follow-up, not an independent blocker for this PR. The full mobile suite passed; simulator failure-state validation remains incomplete. Reviewed head: |
kazemek21
left a comment
There was a problem hiding this comment.
Kyle reviewed this PR and the Nexus review-tracker notes and approves.
Posted by Codex (gpt-6.1-sol) on behalf of kylez
A nonmember viewing an open channel saw "Join this channel from Manage to participate." with no way to act on it there. The footer now matches desktop: "Join channel to send messages" with a Join button. A private channel preview says it is a preview and offers no Join. Joining also has to show up right away. The relay acknowledges the join before its replicas see the new roster, so the refresh that followed still listed the user as a nonmember and the page stayed on Join. Like desktop's channel lifecycle, joinChannel now confirms the roster with strong (writer-pool) reads, then refreshes memberships with a strong read. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
Only the relay's /query bridge honors consistency: strong. A WebSocket REQ reads replicas, so the confirmation could miss a just-accepted join. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
A join now settles only when the channel list shows the membership. An accepted join that can't be confirmed or shown yet is reported apart from a refusal, and the footer offers Check again, which rereads without a second join. While a confirmed join is missing from a replica read, the list reads the writer pool, whose answer also keeps a later removal. Guest-join channels read as read-only with no Join, as on desktop. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
1b61947 to
f2c216f
Compare
A community or identity switch clears this client's recorded joins, so another scope's join never pins reads to the writer pool. Join failures now log their cause, and Channel details offers no Join for a guest-join channel, matching the footer. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Tom Brow <[email protected]>
|
🤖 Thanks, Jude. All four are addressed as of 3c7fe36:
Leave's refresh and the roster repair stay out of scope as you suggested. Full mobile suite passes, and an automated sim join against a live relay showed the composer and kept it across an app relaunch. |
🤖 All four points addressed in 3c7fe36 (see reply above).
Co-Authored-By: Claude Opus 5.5 <[email protected]> * origin/main: feat(mobile/ios): show the message's own text in notifications (#9346) feat(mobile): prefill the agents you last tagged in a conversation (#9248) feat(mobile): start a Solo chat from a message or inbox row (#9251) feat(mobile): link to Builderlab web from Settings (#9300) fix(relay): bound invite preview host lookup (#9308) fix(relay): saturate filter limits instead of casting (#9230) fix(mobile): tell same-name agents apart in Solo (#9321) fix(mobile): join an open channel from the chat footer (#9253) fix(relay): fence pending subscriptions on close or replacement (#2382) fix(mobile): hide archived people and agents from choices; give them their own members section (#9320) Add video stacks and native iOS zoom playback (#9316) Support PNG and HEIC photos in the native iOS zoom gallery (#9314) fix(mobile): list known people in recipient pickers before a name is typed (#9311) feat(mobile): mark edited messages after the body (#8863) Signed-off-by: Philip Azar <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]> * origin/main: (22 commits) chore(deps): bump hickory-proto to 0.26.2 for RUSTSEC-2026-0487..0491 (#9351) feat(mobile/ios): show the message's own text in notifications (#9346) feat(mobile): prefill the agents you last tagged in a conversation (#9248) feat(mobile): start a Solo chat from a message or inbox row (#9251) feat(mobile): link to Builderlab web from Settings (#9300) fix(relay): bound invite preview host lookup (#9308) fix(relay): saturate filter limits instead of casting (#9230) fix(mobile): tell same-name agents apart in Solo (#9321) fix(mobile): join an open channel from the chat footer (#9253) fix(relay): fence pending subscriptions on close or replacement (#2382) fix(mobile): hide archived people and agents from choices; give them their own members section (#9320) Add video stacks and native iOS zoom playback (#9316) Support PNG and HEIC photos in the native iOS zoom gallery (#9314) fix(mobile): list known people in recipient pickers before a name is typed (#9311) feat(mobile): mark edited messages after the body (#8863) Add swipeable photo stacks and native iOS gallery preview (#9259) ci(docker): skip relay image publishes for main pushes outside the build context (#9310) Add manual-only relay image publishing (#9303) fix(mobile): bump Flutter to 3.47.9 for Android TLS fix (#9309) Serve video and poster previews for invite links (#9306) ... Signed-off-by: Philip Azar <[email protected]>





A nonmember viewing an open channel on mobile saw "Join this channel from Manage to participate." in the footer, with nothing to tap and no obvious "Manage". The footer now matches desktop's join notice: Join channel to send messages with a primary-styled Join button (the same primary colors as the composer's send button). A private channel preview says "You're previewing this channel" with no Join, and the archived notice is unchanged.
Making the join show up
The relay acknowledges a join (kind 9021) before its read replicas see the new roster; on the Builderlab relay the lag ran to tens of seconds. So:
joinChannelconfirms the roster withconsistency: "strong"(writer-pool) reads at 0/250/750/1500 ms. It then settles only once the channel list itself shows the membership.joinChannelthrowsChannelJoinUnconfirmed. The footer then says "Join sent, but not confirmed yet" with Check again, which rereads (recheckJoin) without sending another join. A refused join still shows "Couldn't join channel. Try again." and keeps Join. The Channel details "Join channel" row gets the same distinction.ChannelsNotifierrecords each join it confirmed. While an ordinary membership read from a replica lacks one, the list rereads memberships from the writer pool, whose answer is authoritative: a join removed since is dropped there and forgotten. Once a replica read includes every recorded join, reads go back to replicas only. A community or identity switch clears the recorded joins.Guest-join channels
Self-joining a channel whose
join_roleisguestgives a role that can't post. Like desktop, the footer reads This channel is read-only with no Join, so it never promises sending. Channel details offers no "Join channel" row for them either.ChannelDataparsesjoin_rolethe way desktop does: a missing tag means member, and anything but a singlemembervalue fails closed to guest.Before / after
New states (widget-test renders):
Demo video (search for an open channel, open it, tap Join; the footer becomes the composer): shared in Buzz rather than here, since it shows real member names from the test community.
Validation
ChannelsNotifierwith a fake relay whose writer pool sees joins before replicas:A table test covers
join_roleparsing.Leave's ordinary refresh and the relay's missing-roster repair are left for separate follow-ups.
buzz-review-completed
🤖 Generated with Claude Code