fix(mobile): prevent Android chat rows overlapping during sync - #10983
Merged
juliusmarminge merged 1 commit intoSep 9, 2026
Merged
Conversation
github-actions
Bot
added
vouch:trusted
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
Contributor
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a focused one-file mobile bug fix that disables the problematic Android row-layout transition path while preserving iOS behavior. Its runtime impact is limited to chat row positioning and animation, with no schema, security, billing, deployment, or static-analysis changes. You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe thread feed now disables ChangesThread feed layout behavior
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Android thread rows now use non-animated positioning to prevent sync-time overlap, while iOS behavior remains unchanged. No current merge-blocking risk is identified. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
2 tasks
This was referenced Sep 9, 2026
github-actions Bot
added a commit
to omarcresp/t3code-flake
that referenced
this pull request
Sep 10, 2026
## What's Changed * fix(web): allow expanding duplicate tool call commands by @Yash-Singh1 in pingdotgg/t3code#10981 * fix(mobile): prevent Android chat rows overlapping during sync by @SunkenInTime in pingdotgg/t3code#10983 * fix(mobile): prevent text leaking through Android glass by @juliusmarminge in pingdotgg/t3code#10998 * feat(pull-requests): link multiple pull requests to threads by @juliusmarminge in pingdotgg/t3code#10839 * feat(search): find threads by linked pull request by @juliusmarminge in pingdotgg/t3code#10870 * feat(prs): navigate, merge and rebase GitHub stacks by @juliusmarminge in pingdotgg/t3code#10875 * fix(server): preserve recent PR reads across server restarts by @juliusmarminge in pingdotgg/t3code#11007 * feat(web): zoom and pan expanded images by @maria-rcks in pingdotgg/t3code#10869 * fix(ui): use available space for composer model names by @juliusmarminge in pingdotgg/t3code#11002 **Full Changelog**: pingdotgg/t3code@v0.0.41-nightly.20260909.1461...v0.0.41-nightly.20260910.1473 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.41-nightly.20260910.1473
aorwall
added a commit
to aorwall/t3code
that referenced
this pull request
Sep 10, 2026
Merges `pingdotgg/t3code` `2a3035353..0f602b3` (16 commits) into the fork. - **Landed:** 283 files (`HEAD^1..HEAD`) against 277 in the upstream range — `merge-stats.mjs` reports an exact 277/277 file match, so nothing in the range was dropped and nothing extra came in. The six over are three typecheck fixes and three fork docs, both listed below. Fork delta 733 files (`HEAD^2..HEAD`). - **Conflicts:** 6 files, all on one upstream feature (pingdotgg#10839, linking several pull requests to a thread). Resolutions in `docs/fork/upstream-merge-log.md`. - **Sweep:** 13 owned-concern hits, all `infra/relay/**` FCM/Android-push files under the decided-out `cloud-relay-connect` concern. Inherited in tree, adopted by nothing. - **Unsupported methods:** 0 ADD, 0 DROP — no `packages/contracts/src/rpc.ts` edit needed. ## What upstream shipped ### Usable as-is against Moatless Pure client work, no backend involvement — these are live the moment this merges. - **pingdotgg#11020** message copy buttons show on touch devices. - **pingdotgg#11018** middle-click pastes in the terminal on Linux. - **pingdotgg#10869** expanded images zoom and pan. - **pingdotgg#11002** the composer uses the available space for model names. - **pingdotgg#10981** duplicate tool-call commands can be expanded independently. - **pingdotgg#10947** provider settings grow a bulk model toggle. - **pingdotgg#10609** the PR list's diff counts return to the top right. - **pingdotgg#11022** remote projects open in Zed (`packages/contracts/src/editor.ts` plus the desktop shell — the fork ships both). - **pingdotgg#10998 / pingdotgg#10983 / pingdotgg#10964** three Android glass/overlap fixes in `apps/mobile`. ### Unsupported in Moatless — needs backend implementation - **pingdotgg#10839 — several pull requests per thread.** This is the substantive decision in the merge. Upstream now carries `thread.pullRequests: ThreadPullRequestLink[]`, `packages/shared/src/threadPullRequests.ts`, and a `ThreadPullRequestBadgeControl` pill with its own `pull-requests` stack tab. That is exactly the equivalent the fork's `task-bound-pull-request` convergence entry said to re-home its `+N` menu onto — but it cannot be re-homed yet: Moatless serves no `pullRequests` array on a thread and does not advertise the new `threadPullRequests` capability, so upstream's badge would resolve to nothing and paint an empty pill over a working one. Taking `theirs` would have silently deleted live fork behaviour. **Resolution:** upstream's implementation landed whole, and the two presentations are switched on `useSupportsMultiplePullRequests` — upstream's badge and stack where the server advertises the capability, the fork's binding-derived pill and `+N` menu where it does not. Additive, no prop threading, and it re-homes itself the day the backend advertises. `docs/fork/inventory.json` and `docs/fork/gaps.md` are updated with the switch and with the exact deletion list for when that happens. **To close it:** serve `thread.pullRequests` on `OrchestrationThread`/`OrchestrationThreadShell` from `task_bindings`, and report `capabilities.threadPullRequests: true`. - **pingdotgg#10870 — find threads by linked pull request.** Search terms come off the same `thread.pullRequests` array, so sidebar and command-palette search by PR number/URL match nothing here until the array is served. Closes with pingdotgg#10839. - **pingdotgg#10875 — navigate, merge and rebase GitHub stacks.** Adds two RPC methods, `pullRequests.stack` and `pullRequests.linkedThreads`, which the Moatless backend does not dispatch. Both are already covered by the shared `PullRequestRpcError` union, so the client decodes the refusal correctly and the stack UI stays inert — no contract change needed. Implementing the two methods is what turns it on. - **pingdotgg#10416 — Android agent notifications and ongoing activity.** Rides FCM through `infra/relay`, which is part of the decided-out `cloud-relay-connect` concern (being removed with Clerk). Inherited in tree, not adopted. ### Backend behaviour worth reproducing in Moatless - **pingdotgg#11007 — recent PR reads survive a server restart.** Upstream added `apps/server/src/pullRequest/PullRequestReadCache.ts`, persisting which pull requests a user has already read so a restart does not re-mark the whole list unread. Moatless owns this surface itself, so nothing in this repository holds it open — recorded so whoever touches the backend's PR read state knows the answer exists upstream. ## Verification `verify.mjs`, seven of eight green: `duplicate-adds`, `tripwires`, `resolution-check`, `unsupported-methods`, `fmt:check`, `lint`, `typecheck`. `test` is red on `@t3tools/desktop` alone — `scripts/browser-secret-native.test.mjs > bundled libsecret helper` fails to compile because `libsecret-1` is not installed in this sandbox. **Pre-existing environment gap, not merge-introduced:** it is already an entry in `docs/fork/gaps.md`, and `git diff --name-only HEAD^1 HEAD | grep browser-secret` is empty. 100 of 102 desktop files pass. Four packages did not finish under `vp run -r test` (`@t3tools/mobile`, `t3`, `@t3tools/web`, `t3code-relay`) and all four pass when run alone, which is parallel load rather than the merge. Three typecheck failures were fixed in the merge commit, all fork-only web code that upstream's widened shared types reached: `sandboxControl.placement.test.tsx` needed the two new `RightPanelTabs` props, and `useSandboxAvailability.ts` / `useSandboxDetail.ts` needed `isSuccess` threaded through now that `EnvironmentQueryView` carries it. Nothing is unresolved. --- Moatless task: https://moatless.soaplabstest.com/tasks/db1b3cbe-4401-441b-bbec-6b0c725c93ce
Contributor
|
It's discouraging to see my PR superceeded by an identical PR. |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Loading an Android chat during sync can leave assistant text drawn over the preceding attachment and timestamp until refresh. Reproduced the intermittent overlap with an attachment-only user message followed by a long assistant response.
Use LegendList's non-animated row positioning on Android instead of Reanimated layout transitions, including zero-duration transitions. Keep that choice stable during command expansion/collapse so the list does not swap container types and remount rows. iOS retains its existing transition path.
Validation: Android API 36 before/after with fresh conversations, plus a successful hardware-accelerated run with a command disclosure. iPhone 17 Pro / iOS 26.5 rendered the same fixture correctly, including delayed attachment loading. Mobile typecheck, 31 focused feed tests, formatting, and targeted lint passed (lint reports existing warnings). The failure was intermittent; subsequent upstream loads also sometimes passed, so these checks establish an Android reproduction, not proof that every iOS timing scenario is unaffected.
Recording limitation: native Android screen recording repeatedly stalled the emulator, including a System UI non-response. Before/after simulator screenshots are attached; a usable motion recording could not be captured.
iOS verification screenshot
Model: GPT-6. Harness: Codex.