GitHub check
256 KB of 598 KB loaded Download the full log (598 KB)
342 KB of earlier output not loaded
Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.8964170Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8964172Z
2026-10-24T02:58:54.8964323Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.8964528Z ╭─[apps/mobile/src/features/layout/workspace-inspector-pane.tsx:67:7]
2026-10-24T02:58:54.8964726Z 37 │ const { renderedInspectorWidth } = props;
2026-10-24T02:58:54.8964856Z 38 │ const renderedContentWidth = useSharedValue(inspectorWidth ?? 0);
2026-10-24T02:58:54.8964943Z · ──────────┬─────────
2026-10-24T02:58:54.8965091Z · ╰── `renderedContentWidth` originates here
2026-10-24T02:58:54.8965144Z 39 │
2026-10-24T02:58:54.8965224Z 40 │ const onClosed = props.onClosed;
2026-10-24T02:58:54.8965290Z 41 │ useEffect(() => {
2026-10-24T02:58:54.8965375Z 42 │ inspectorProgress.value = withTiming(
2026-10-24T02:58:54.8965449Z 43 │ inspectorVisible ? 1 : 0,
2026-10-24T02:58:54.8965520Z 44 │ WORKSPACE_PANE_TIMING,
2026-10-24T02:58:54.8965586Z 45 │ (finished) => {
2026-10-24T02:58:54.8965727Z 46 │ if (finished === true && !inspectorVisible && onClosed !== undefined) {
2026-10-24T02:58:54.8965801Z 47 │ runOnJS(onClosed)();
2026-10-24T02:58:54.8965856Z 48 │ }
2026-10-24T02:58:54.8965911Z 49 │ },
2026-10-24T02:58:54.8965962Z 50 │ );
2026-10-24T02:58:54.8966091Z 51 │ const targetWidth = inspectorVisible ? (inspectorWidth ?? 0) : 0;
2026-10-24T02:58:54.8966168Z 52 │ renderedInspectorWidth.set(
2026-10-24T02:58:54.8966307Z 53 │ resizing ? targetWidth : withTiming(targetWidth, WORKSPACE_PANE_TIMING),
2026-10-24T02:58:54.8966361Z 54 │ );
2026-10-24T02:58:54.8966415Z 55 │ }, [
2026-10-24T02:58:54.8966482Z 56 │ inspectorProgress,
2026-10-24T02:58:54.8966546Z 57 │ inspectorVisible,
2026-10-24T02:58:54.8966609Z 58 │ inspectorWidth,
2026-10-24T02:58:54.8966669Z 59 │ onClosed,
2026-10-24T02:58:54.8966747Z 60 │ renderedInspectorWidth,
2026-10-24T02:58:54.8966805Z 61 │ resizing,
2026-10-24T02:58:54.8966858Z 62 │ ]);
2026-10-24T02:58:54.8966909Z 63 │
2026-10-24T02:58:54.8966972Z 64 │ useEffect(() => {
2026-10-24T02:58:54.8967061Z 65 │ const targetWidth = inspectorWidth ?? 0;
2026-10-24T02:58:54.8967146Z 66 │ if (!inspectorVisible || resizing) {
2026-10-24T02:58:54.8967242Z 67 │ renderedContentWidth.value = targetWidth;
2026-10-24T02:58:54.8967327Z · ──────────┬─────────
2026-10-24T02:58:54.8967482Z · ╰── `renderedContentWidth` cannot be modified
2026-10-24T02:58:54.8967540Z 68 │ return;
2026-10-24T02:58:54.8967591Z ╰────
2026-10-24T02:58:54.8967846Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.8968155Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8968160Z
2026-10-24T02:58:54.8968413Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.8968580Z ╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:123:7]
2026-10-24T02:58:54.8968633Z 118 │
2026-10-24T02:58:54.8968695Z 119 │ useEffect(() => {
2026-10-24T02:58:54.8968766Z · ────┬────
2026-10-24T02:58:54.8968895Z · ╰── This is the containing effect
2026-10-24T02:58:54.8968977Z 120 │ if (orientationSettled) return;
2026-10-24T02:58:54.8969138Z 121 │ const orientation = getNativeShowcaseOrientation();
2026-10-24T02:58:54.8969240Z 122 │ if (orientation === null) {
2026-10-24T02:58:54.8969321Z 123 │ setOrientationSettled(true);
2026-10-24T02:58:54.8969409Z · ──────────┬──────────
2026-10-24T02:58:54.8969576Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.8969636Z 124 │ return;
2026-10-24T02:58:54.8969689Z ╰────
2026-10-24T02:58:54.8970302Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.8970618Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.8970625Z
2026-10-24T02:58:54.8970873Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.8971041Z ╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:304:7]
2026-10-24T02:58:54.8971093Z 292 │
2026-10-24T02:58:54.8971158Z 293 │ useEffect(() => {
2026-10-24T02:58:54.8971226Z · ────┬────
2026-10-24T02:58:54.8971353Z · ╰── This is the containing effect
2026-10-24T02:58:54.8971410Z 294 │ if (
2026-10-24T02:58:54.8971475Z 295 │ scene === null ||
2026-10-24T02:58:54.8971552Z 296 │ requestedScene === null ||
2026-10-24T02:58:54.8971627Z 297 │ scene !== requestedScene ||
2026-10-24T02:58:54.8971694Z 298 │ !hasFixture ||
2026-10-24T02:58:54.8971768Z 299 │ !orientationSettled ||
2026-10-24T02:58:54.8971834Z 300 │ !themeApplied ||
2026-10-24T02:58:54.8971949Z 301 │ (scene === "agent-activity" && !agentActivityStaged) ||
2026-10-24T02:58:54.8972080Z 302 │ !isShowcaseNativeContentReady({ scene, themeId, renderSignal })
2026-10-24T02:58:54.8972134Z 303 │ ) {
2026-10-24T02:58:54.8972203Z 304 │ setReadyScene(null);
2026-10-24T02:58:54.8972280Z · ──────┬──────
2026-10-24T02:58:54.8972445Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.8972505Z 305 │ return;
2026-10-24T02:58:54.8972555Z ╰────
2026-10-24T02:58:54.8973141Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.8973454Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.8973457Z
2026-10-24T02:58:54.8973719Z ⚠ eslint(no-unused-vars): Variable 'lastOutcome' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.8973883Z ╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:128:9]
2026-10-24T02:58:54.8973952Z 127 │ let cancelled = false;
2026-10-24T02:58:54.8974041Z 128 │ let lastOutcome: string | null = null;
2026-10-24T02:58:54.8974169Z · ─────┬─────
2026-10-24T02:58:54.8974328Z · ╰── 'lastOutcome' is declared here
2026-10-24T02:58:54.8974502Z 129 │ void retryShowcaseOperation(async () => applyNativeShowcaseOrientation(orientation), {
2026-10-24T02:58:54.8974552Z ╰────
2026-10-24T02:58:54.8974655Z help: Consider removing this declaration.
2026-10-24T02:58:54.8974658Z
2026-10-24T02:58:54.8974840Z ⚠ react(capitalized-calls): Capitalized function called without JSX
2026-10-24T02:58:54.8974953Z ╭─[apps/mobile/src/lib/useHoverGesture.ts:8:15]
2026-10-24T02:58:54.8975010Z 7 │ () =>
2026-10-24T02:58:54.8975075Z 8 │ Gesture.Hover()
2026-10-24T02:58:54.8975148Z · ──┬──
2026-10-24T02:58:54.8975281Z · ╰── `Hover` may be a component
2026-10-24T02:58:54.8975360Z 9 │ .manualActivation(true)
2026-10-24T02:58:54.8975412Z ╰────
2026-10-24T02:58:54.8975685Z help: Render `Hover` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
2026-10-24T02:58:54.8976125Z note: `Hover` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
2026-10-24T02:58:54.8976127Z
2026-10-24T02:58:54.8976305Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.8976489Z ╭─[apps/mobile/src/features/keyboard/HardwareKeyboardCommandProvider.tsx:116:34]
2026-10-24T02:58:54.8976556Z 115 │ return [...commands];
2026-10-24T02:58:54.8976691Z 116 │ }, [activeThreadRef, pathname, registrationVersion, navigation]);
2026-10-24T02:58:54.8976808Z · ─────────┬─────────
2026-10-24T02:58:54.8976988Z · ╰── Unnecessary dependency `registrationVersion`
2026-10-24T02:58:54.8977040Z 117 │
2026-10-24T02:58:54.8977089Z ╰────
2026-10-24T02:58:54.8977394Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.8977695Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.8977698Z
2026-10-24T02:58:54.8977909Z ⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
2026-10-24T02:58:54.8978032Z ╭─[apps/mobile/src/lib/markdownDocument.ts:259:28]
2026-10-24T02:58:54.8978128Z 258 │ visit(parser.parse(markdown), false, false);
2026-10-24T02:58:54.8978211Z 259 │ for (const edit of edits.reverse())
2026-10-24T02:58:54.8978304Z · ───────
2026-10-24T02:58:54.8978465Z 260 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
2026-10-24T02:58:54.8978514Z ╰────
2026-10-24T02:58:54.8978768Z help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
2026-10-24T02:58:54.8978771Z
2026-10-24T02:58:54.8978975Z ⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
2026-10-24T02:58:54.8979144Z ╭─[apps/mobile/src/lib/markdownDocument.ts:290:28]
2026-10-24T02:58:54.8979256Z 289 │ visit(parser.parse(markdown));
2026-10-24T02:58:54.8979338Z 290 │ for (const edit of edits.reverse())
2026-10-24T02:58:54.8979645Z · ───────
2026-10-24T02:58:54.8979804Z 291 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
2026-10-24T02:58:54.8979891Z ╰────
2026-10-24T02:58:54.8980154Z help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
2026-10-24T02:58:54.8980157Z
2026-10-24T02:58:54.8980360Z ⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
2026-10-24T02:58:54.8980480Z ╭─[apps/mobile/src/lib/markdownDocument.ts:344:38]
2026-10-24T02:58:54.8980565Z 343 │ visit(parser.parse(markdown));
2026-10-24T02:58:54.8980668Z 344 │ for (const lineStart of lineStarts.reverse()) {
2026-10-24T02:58:54.8980768Z · ───────
2026-10-24T02:58:54.8980927Z 345 │ // The header row may be a lazy line without its container markers (`>` or list indent),
2026-10-24T02:58:54.8980978Z ╰────
2026-10-24T02:58:54.8981227Z help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
2026-10-24T02:58:54.8981229Z
2026-10-24T02:58:54.8981479Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.8981627Z ╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:400:5]
2026-10-24T02:58:54.8981681Z 398 │
2026-10-24T02:58:54.8981751Z 399 │ useEffect(() => {
2026-10-24T02:58:54.8981825Z · ────┬────
2026-10-24T02:58:54.8981952Z · ╰── This is the containing effect
2026-10-24T02:58:54.8982042Z 400 │ setInspectorSelection((current) => {
2026-10-24T02:58:54.8982126Z · ──────────┬──────────
2026-10-24T02:58:54.8982291Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.8982393Z 401 │ if (props.renderInspector === undefined) {
2026-10-24T02:58:54.8982444Z ╰────
2026-10-24T02:58:54.8983087Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.8983442Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.8983444Z
2026-10-24T02:58:54.8983651Z ⚠ react(no-unstable-nested-components): Do not define components during render.
2026-10-24T02:58:54.8983801Z ╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:528:24]
2026-10-24T02:58:54.8983959Z 527 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
2026-10-24T02:58:54.8984124Z 528 │ ╭─▶ const GitInspector = () => (
2026-10-24T02:58:54.8984220Z 529 │ │ <GitOverviewSheet
2026-10-24T02:58:54.8984346Z 530 │ │ headerInset={inspectorHeaderInset}
2026-10-24T02:58:54.8984452Z 531 │ │ presentation="inspector"
2026-10-24T02:58:54.8984626Z 532 │ │ route={{ params: { environmentId: environmentId!, threadId: threadId! } }}
2026-10-24T02:58:54.8984701Z 533 │ │ />
2026-10-24T02:58:54.8984828Z 534 │ ╰─▶ );
2026-10-24T02:58:54.8984908Z 535 │ const FilesInspector = () =>
2026-10-24T02:58:54.8984958Z ╰────
2026-10-24T02:58:54.8985173Z help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
2026-10-24T02:58:54.8985176Z
2026-10-24T02:58:54.8985380Z ⚠ react(no-unstable-nested-components): Do not define components during render.
2026-10-24T02:58:54.8985533Z ╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:535:26]
2026-10-24T02:58:54.8985593Z 534 │ );
2026-10-24T02:58:54.8985754Z 535 │ ╭─▶ const FilesInspector = () =>
2026-10-24T02:58:54.8985905Z 536 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
2026-10-24T02:58:54.8986010Z 537 │ │ <ThreadFileNavigatorPane
2026-10-24T02:58:54.8986113Z 538 │ │ cwd={selectedThreadCwd}
2026-10-24T02:58:54.8986247Z 539 │ │ environmentId={selectedThread.environmentId}
2026-10-24T02:58:54.8986368Z 540 │ │ headerInset={inspectorHeaderInset}
2026-10-24T02:58:54.8986511Z 541 │ │ projectName={selectedThreadProject?.title ?? "Files"}
2026-10-24T02:58:54.8986616Z 542 │ │ selectedPath={null}
2026-10-24T02:58:54.8986744Z 543 │ │ onSelectFile={handleSelectInspectorFile}
2026-10-24T02:58:54.8986820Z 544 │ │ />
2026-10-24T02:58:54.8986953Z 545 │ ╰─▶ ) : null;
2026-10-24T02:58:54.8987102Z 546 │ const RouteInspector = () => props.renderInspector?.(inspectorHeaderInset);
2026-10-24T02:58:54.8987152Z ╰────
2026-10-24T02:58:54.8987364Z help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
2026-10-24T02:58:54.8987366Z
2026-10-24T02:58:54.8987521Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.8987682Z ╭─[apps/mobile/src/features/threads/floating-working-control.tsx:111:5]
2026-10-24T02:58:54.8987786Z 107 │ );
2026-10-24T02:58:54.8987963Z 108 │ const separationProgress = useSharedValue(props.showScrollToEnd ? 1 : 0);
2026-10-24T02:58:54.8988052Z · ─────────┬────────
2026-10-24T02:58:54.8988201Z · ╰── `separationProgress` originates here
2026-10-24T02:58:54.8988251Z 109 │
2026-10-24T02:58:54.8988316Z 110 │ useEffect(() => {
2026-10-24T02:58:54.8988486Z 111 │ separationProgress.value = withTiming(props.showScrollToEnd ? 1 : 0, CONTROL_TIMING);
2026-10-24T02:58:54.8988570Z · ─────────┬────────
2026-10-24T02:58:54.8988718Z · ╰── `separationProgress` cannot be modified
2026-10-24T02:58:54.8988824Z 112 │ }, [props.showScrollToEnd, separationProgress]);
2026-10-24T02:58:54.8988875Z ╰────
2026-10-24T02:58:54.8989140Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.8989447Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8989449Z
2026-10-24T02:58:54.8989599Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.8989756Z ╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
2026-10-24T02:58:54.8989874Z 128 │ // and repeatedly retargets the animation as it grows.
2026-10-24T02:58:54.8990016Z 129 │ const capsuleWidth = useSharedValue<number | null>(null);
2026-10-24T02:58:54.8990098Z · ──────┬─────
2026-10-24T02:58:54.8990238Z · ╰── `capsuleWidth` originates here
2026-10-24T02:58:54.8990351Z 130 │ const measuredWidthRef = useRef<number | null>(null);
2026-10-24T02:58:54.8990465Z 131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.8990566Z 132 │ const width = event.nativeEvent.layout.width;
2026-10-24T02:58:54.8990659Z 133 │ if (width === measuredWidthRef.current) {
2026-10-24T02:58:54.8990720Z 134 │ return;
2026-10-24T02:58:54.8990775Z 135 │ }
2026-10-24T02:58:54.8990879Z 136 │ const first = measuredWidthRef.current === null;
2026-10-24T02:58:54.8990963Z 137 │ measuredWidthRef.current = width;
2026-10-24T02:58:54.8991104Z 138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
2026-10-24T02:58:54.8991178Z · ──────┬─────
2026-10-24T02:58:54.8991314Z · ╰── `capsuleWidth` cannot be modified
2026-10-24T02:58:54.8991374Z 139 │ };
2026-10-24T02:58:54.8991427Z ╰────
2026-10-24T02:58:54.8991682Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.8991979Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8991982Z
2026-10-24T02:58:54.8992134Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.8992294Z ╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
2026-10-24T02:58:54.8992403Z 128 │ // and repeatedly retargets the animation as it grows.
2026-10-24T02:58:54.8992514Z 129 │ const capsuleWidth = useSharedValue<number | null>(null);
2026-10-24T02:58:54.8992643Z · ──────┬─────
2026-10-24T02:58:54.8992808Z · ╰── `capsuleWidth` originates here
2026-10-24T02:58:54.8992916Z 130 │ const measuredWidthRef = useRef<number | null>(null);
2026-10-24T02:58:54.8993025Z 131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.8993125Z 132 │ const width = event.nativeEvent.layout.width;
2026-10-24T02:58:54.8993218Z 133 │ if (width === measuredWidthRef.current) {
2026-10-24T02:58:54.8993278Z 134 │ return;
2026-10-24T02:58:54.8993330Z 135 │ }
2026-10-24T02:58:54.8993434Z 136 │ const first = measuredWidthRef.current === null;
2026-10-24T02:58:54.8993517Z 137 │ measuredWidthRef.current = width;
2026-10-24T02:58:54.8993656Z 138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
2026-10-24T02:58:54.8993707Z 139 │ };
2026-10-24T02:58:54.8993802Z 140 │ const hasStatus = props.status !== null;
2026-10-24T02:58:54.8993936Z 141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
2026-10-24T02:58:54.8994001Z 142 │ useEffect(() => {
2026-10-24T02:58:54.8994065Z 143 │ if (!hasStatus) {
2026-10-24T02:58:54.8994150Z 144 │ measuredWidthRef.current = null;
2026-10-24T02:58:54.8994228Z 145 │ capsuleWidth.value = null;
2026-10-24T02:58:54.8994304Z · ──────┬─────
2026-10-24T02:58:54.8994441Z · ╰── `capsuleWidth` cannot be modified
2026-10-24T02:58:54.8994495Z 146 │ }
2026-10-24T02:58:54.8994548Z ╰────
2026-10-24T02:58:54.8994802Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.8995103Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8995108Z
2026-10-24T02:58:54.8995306Z ⚠ react(immutability): Cannot modify local variables after render completes
2026-10-24T02:58:54.8995464Z ╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
2026-10-24T02:58:54.8995595Z 141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
2026-10-24T02:58:54.8995658Z 142 │ useEffect(() => {
2026-10-24T02:58:54.8995734Z · ───┬───
2026-10-24T02:58:54.8995953Z · ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
2026-10-24T02:58:54.8996018Z 143 │ if (!hasStatus) {
2026-10-24T02:58:54.8996107Z 144 │ measuredWidthRef.current = null;
2026-10-24T02:58:54.8996187Z 145 │ capsuleWidth.value = null;
2026-10-24T02:58:54.8996262Z · ──────┬─────
2026-10-24T02:58:54.8996395Z · ╰── This modifies `capsuleWidth`
2026-10-24T02:58:54.8996447Z 146 │ }
2026-10-24T02:58:54.8996498Z ╰────
2026-10-24T02:58:54.8996834Z help: This argument is a function which may reassign or mutate `capsuleWidth` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
2026-10-24T02:58:54.8997129Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8997131Z
2026-10-24T02:58:54.8997375Z ⚠ react(immutability): Cannot modify local variables after render completes
2026-10-24T02:58:54.8997567Z ╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
2026-10-24T02:58:54.8997675Z 130 │ const measuredWidthRef = useRef<number | null>(null);
2026-10-24T02:58:54.8997790Z 131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.8997910Z · ───────────────┬───────────────
2026-10-24T02:58:54.8998143Z · ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
2026-10-24T02:58:54.8998246Z 132 │ const width = event.nativeEvent.layout.width;
2026-10-24T02:58:54.8998341Z 133 │ if (width === measuredWidthRef.current) {
2026-10-24T02:58:54.8998400Z 134 │ return;
2026-10-24T02:58:54.8998453Z 135 │ }
2026-10-24T02:58:54.8998564Z 136 │ const first = measuredWidthRef.current === null;
2026-10-24T02:58:54.8998651Z 137 │ measuredWidthRef.current = width;
2026-10-24T02:58:54.8998791Z 138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
2026-10-24T02:58:54.8998864Z · ──────┬─────
2026-10-24T02:58:54.8998996Z · ╰── This modifies `capsuleWidth`
2026-10-24T02:58:54.8999050Z 139 │ };
2026-10-24T02:58:54.8999102Z ╰────
2026-10-24T02:58:54.8999432Z help: This argument is a function which may reassign or mutate `capsuleWidth` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
2026-10-24T02:58:54.8999729Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.8999731Z
2026-10-24T02:58:54.8999898Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9000084Z ╭─[apps/mobile/src/features/threads/thread-work-log.tsx:174:5]
2026-10-24T02:58:54.9000226Z 170 │ const expandedAngle = props.collapsedDirection === "right" ? 90 : 180;
2026-10-24T02:58:54.9000357Z 171 │ const rotation = useSharedValue(props.expanded ? expandedAngle : 0);
2026-10-24T02:58:54.9000430Z · ────┬───
2026-10-24T02:58:54.9000558Z · ╰── `rotation` originates here
2026-10-24T02:58:54.9000610Z 172 │
2026-10-24T02:58:54.9000677Z 173 │ useLayoutEffect(() => {
2026-10-24T02:58:54.9000809Z 174 │ rotation.value = withTiming(props.expanded ? expandedAngle : 0, {
2026-10-24T02:58:54.9000879Z · ────┬───
2026-10-24T02:58:54.9001014Z · ╰── `rotation` cannot be modified
2026-10-24T02:58:54.9001111Z 175 │ duration: THREAD_DISCLOSURE_TRANSITION_MS,
2026-10-24T02:58:54.9001163Z ╰────
2026-10-24T02:58:54.9001418Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9001715Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9001717Z
2026-10-24T02:58:54.9001905Z ⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
2026-10-24T02:58:54.9002053Z ╭─[apps/mobile/src/features/threads/thread-work-log.tsx:1246:23]
2026-10-24T02:58:54.9002122Z 1245 │ <Text
2026-10-24T02:58:54.9002265Z 1246 │ key={`${index}:${line}`}
2026-10-24T02:58:54.9002409Z · ────────────────────────
2026-10-24T02:58:54.9002484Z 1247 │ selectable
2026-10-24T02:58:54.9002536Z ╰────
2026-10-24T02:58:54.9002680Z help: Use a unique data-dependent key to avoid unnecessary rerenders
2026-10-24T02:58:54.9002683Z
2026-10-24T02:58:54.9002958Z ⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
2026-10-24T02:58:54.9003110Z ╭─[apps/web/src/components/settings/SettingInheritance.tsx:163:24]
2026-10-24T02:58:54.9003165Z 162 │ keys,
2026-10-24T02:58:54.9003238Z 163 │ overridingProjects = [],
2026-10-24T02:58:54.9003317Z · ──
2026-10-24T02:58:54.9003383Z 164 │ onClearOverrides,
2026-10-24T02:58:54.9003442Z ╰────
2026-10-24T02:58:54.9003753Z help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
2026-10-24T02:58:54.9003756Z
2026-10-24T02:58:54.9004005Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9004151Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:361:7]
2026-10-24T02:58:54.9004287Z 355 │ }, [cancelledIncomingShareId, navigation, props.incomingShareId]);
2026-10-24T02:58:54.9004351Z 356 │ useEffect(() => {
2026-10-24T02:58:54.9004421Z · ────┬────
2026-10-24T02:58:54.9004546Z · ╰── This is the containing effect
2026-10-24T02:58:54.9004641Z 357 │ if (!isReturningToProjectPicker) {
2026-10-24T02:58:54.9004702Z 358 │ return;
2026-10-24T02:58:54.9004755Z 359 │ }
2026-10-24T02:58:54.9004849Z 360 │ if (requestedInitialProjectAvailable) {
2026-10-24T02:58:54.9004942Z 361 │ setIsReturningToProjectPicker(false);
2026-10-24T02:58:54.9005043Z · ──────────────┬──────────────
2026-10-24T02:58:54.9005215Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9005272Z 362 │ return;
2026-10-24T02:58:54.9005323Z ╰────
2026-10-24T02:58:54.9005957Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9006301Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9006303Z
2026-10-24T02:58:54.9006549Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9006696Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:504:9]
2026-10-24T02:58:54.9006749Z 447 │
2026-10-24T02:58:54.9006813Z 448 │ useEffect(() => {
2026-10-24T02:58:54.9006881Z · ────┬────
2026-10-24T02:58:54.9007008Z · ╰── This is the containing effect
2026-10-24T02:58:54.9007108Z 449 │ if (props.pendingTaskId || props.draftId) {
2026-10-24T02:58:54.9007173Z 450 │ return;
2026-10-24T02:58:54.9007228Z 451 │ }
2026-10-24T02:58:54.9007367Z 452 │ if (lastInitialProjectRefRef.current !== props.initialProjectRef) {
2026-10-24T02:58:54.9007498Z 453 │ lastInitialProjectRefRef.current = props.initialProjectRef;
2026-10-24T02:58:54.9007602Z 454 │ appliedInitialProjectKeyRef.current = null;
2026-10-24T02:58:54.9007653Z 455 │ }
2026-10-24T02:58:54.9007792Z 456 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
2026-10-24T02:58:54.9007918Z 457 │ const initialProjectId = props.initialProjectRef?.projectId;
2026-10-24T02:58:54.9008021Z 458 │ if (initialEnvironmentId && initialProjectId) {
2026-10-24T02:58:54.9008090Z 459 │ const directProject =
2026-10-24T02:58:54.9008157Z 460 │ projects.find(
2026-10-24T02:58:54.9008222Z 461 │ (project) =>
2026-10-24T02:58:54.9008401Z 462 │ project.environmentId === initialEnvironmentId && project.id === initialProjectId,
2026-10-24T02:58:54.9008463Z 463 │ ) ?? null;
2026-10-24T02:58:54.9008514Z 464 │
2026-10-24T02:58:54.9008582Z 465 │ if (directProject) {
2026-10-24T02:58:54.9008717Z 466 │ // Apply the route's project once. Re-applying on every change would
2026-10-24T02:58:54.9008852Z 467 │ // instantly revert environment/project switches made in the picker.
2026-10-24T02:58:54.9009008Z 468 │ const directProjectKey = `${directProject.environmentId}:${directProject.id}`;
2026-10-24T02:58:54.9009140Z 469 │ if (appliedInitialProjectKeyRef.current === directProjectKey) {
2026-10-24T02:58:54.9009202Z 470 │ return;
2026-10-24T02:58:54.9009257Z 471 │ }
2026-10-24T02:58:54.9009353Z 472 │ if (props.initialProjectRef?.branch) {
2026-10-24T02:58:54.9009414Z 473 │ if (
2026-10-24T02:58:54.9009559Z 474 │ selectedProject?.environmentId !== directProject.environmentId ||
2026-10-24T02:58:54.9009662Z 475 │ selectedProject.id !== directProject.id
2026-10-24T02:58:54.9009721Z 476 │ ) {
2026-10-24T02:58:54.9009804Z 477 │ setProject(directProject);
2026-10-24T02:58:54.9009892Z 478 │ return;
2026-10-24T02:58:54.9009948Z 479 │ }
2026-10-24T02:58:54.9010028Z 480 │ if (!flow.draftKey) return;
2026-10-24T02:58:54.9010167Z 481 │ // The route completes checkout before mounting this composer. Local
2026-10-24T02:58:54.9010307Z 482 │ // mode reuses an existing worktree; worktree mode would create another.
2026-10-24T02:58:54.9010412Z 483 │ updateComposerDraftSettings(flow.draftKey, {
2026-10-24T02:58:54.9010490Z 484 │ workspaceSelection: {
2026-10-24T02:58:54.9010610Z 485 │ mode: "local",
2026-10-24T02:58:54.9010743Z 486 │ branch: props.initialProjectRef.branch,
2026-10-24T02:58:54.9010875Z 487 │ worktreePath: props.initialProjectRef.worktreePath ?? null,
2026-10-24T02:58:54.9010955Z 488 │ startFromOrigin: false,
2026-10-24T02:58:54.9011015Z 489 │ },
2026-10-24T02:58:54.9011075Z 490 │ });
2026-10-24T02:58:54.9011130Z 491 │ }
2026-10-24T02:58:54.9011256Z 492 │ appliedInitialProjectKeyRef.current = directProjectKey;
2026-10-24T02:58:54.9011314Z 493 │ if (
2026-10-24T02:58:54.9011450Z 494 │ selectedProject?.environmentId === directProject.environmentId &&
2026-10-24T02:58:54.9011547Z 495 │ selectedProject.id === directProject.id
2026-10-24T02:58:54.9011605Z 496 │ ) {
2026-10-24T02:58:54.9011665Z 497 │ return;
2026-10-24T02:58:54.9011724Z 498 │ }
2026-10-24T02:58:54.9011806Z 499 │ setProject(directProject);
2026-10-24T02:58:54.9011866Z 500 │ return;
2026-10-24T02:58:54.9011919Z 501 │ }
2026-10-24T02:58:54.9011969Z 502 │
2026-10-24T02:58:54.9012049Z 503 │ if (projects.length > 0) {
2026-10-24T02:58:54.9012143Z 504 │ setIsReturningToProjectPicker(true);
2026-10-24T02:58:54.9012249Z · ──────────────┬──────────────
2026-10-24T02:58:54.9012424Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9012480Z 505 │ }
2026-10-24T02:58:54.9012531Z ╰────
2026-10-24T02:58:54.9013117Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9013434Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9013437Z
2026-10-24T02:58:54.9013686Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9013835Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:604:5]
2026-10-24T02:58:54.9013887Z 545 │
2026-10-24T02:58:54.9013952Z 546 │ useEffect(() => {
2026-10-24T02:58:54.9014021Z · ────┬────
2026-10-24T02:58:54.9014149Z · ╰── This is the containing effect
2026-10-24T02:58:54.9014245Z 547 │ const shareId = props.incomingShareId;
2026-10-24T02:58:54.9014330Z 548 │ const draftKey = flow.draftKey;
2026-10-24T02:58:54.9014428Z 549 │ const destinationProject = selectedProject;
2026-10-24T02:58:54.9014569Z 550 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
2026-10-24T02:58:54.9014695Z 551 │ const initialProjectId = props.initialProjectRef?.projectId;
2026-10-24T02:58:54.9014783Z 552 │ const selectedProjectMatchesRoute =
2026-10-24T02:58:54.9014855Z 553 │ !initialEnvironmentId ||
2026-10-24T02:58:54.9014924Z 554 │ !initialProjectId ||
2026-10-24T02:58:54.9015051Z 555 │ (destinationProject?.environmentId === initialEnvironmentId &&
2026-10-24T02:58:54.9015153Z 556 │ destinationProject.id === initialProjectId);
2026-10-24T02:58:54.9015209Z 557 │ if (
2026-10-24T02:58:54.9015271Z 558 │ !shareId ||
2026-10-24T02:58:54.9015388Z 559 │ !draftKey ||
2026-10-24T02:58:54.9015487Z 560 │ !destinationProject ||
2026-10-24T02:58:54.9015573Z 561 │ !selectedProjectMatchesRoute ||
2026-10-24T02:58:54.9015661Z 562 │ cancelledIncomingShareId === shareId
2026-10-24T02:58:54.9015718Z 563 │ ) {
2026-10-24T02:58:54.9015775Z 564 │ return;
2026-10-24T02:58:54.9015828Z 565 │ }
2026-10-24T02:58:54.9015923Z 566 │ const importKey = `${shareId}:${draftKey}`;
2026-10-24T02:58:54.9015979Z 567 │ if (
2026-10-24T02:58:54.9016086Z 568 │ startedShareImportKeyRef.current === importKey ||
2026-10-24T02:58:54.9016194Z 569 │ cancellingShareImportKeyRef.current === importKey
2026-10-24T02:58:54.9016249Z 570 │ ) {
2026-10-24T02:58:54.9016308Z 571 │ return;
2026-10-24T02:58:54.9016359Z 572 │ }
2026-10-24T02:58:54.9016409Z 573 │
2026-10-24T02:58:54.9016480Z 574 │ if (!incomingShare) {
2026-10-24T02:58:54.9016673Z 575 │ if (isIncomingShareUnavailable && alertedUnavailableIncomingShareIdRef.current !== shareId) {
2026-10-24T02:58:54.9016798Z 576 │ alertedUnavailableIncomingShareIdRef.current = shareId;
2026-10-24T02:58:54.9016863Z 577 │ Dialog.alert(
2026-10-24T02:58:54.9016946Z 578 │ "Shared content unavailable",
2026-10-24T02:58:54.9017115Z 579 │ "The shared content is no longer in the inbox. You can continue editing this task draft.",
2026-10-24T02:58:54.9017172Z 580 │ );
2026-10-24T02:58:54.9017225Z 581 │ }
2026-10-24T02:58:54.9017283Z 582 │ return;
2026-10-24T02:58:54.9017335Z 583 │ }
2026-10-24T02:58:54.9017385Z 584 │
2026-10-24T02:58:54.9017440Z 585 │ if (
2026-10-24T02:58:54.9017602Z 586 │ incomingShare.attachments.some((attachment) => attachment.type === "file") &&
2026-10-24T02:58:54.9017700Z 587 │ selectedEnvironmentServerConfig === null
2026-10-24T02:58:54.9017754Z 588 │ ) {
2026-10-24T02:58:54.9017811Z 589 │ return;
2026-10-24T02:58:54.9017864Z 590 │ }
2026-10-24T02:58:54.9017913Z 591 │
2026-10-24T02:58:54.9018050Z 592 │ if (alertedUnavailableIncomingShareIdRef.current === shareId) {
2026-10-24T02:58:54.9018167Z 593 │ alertedUnavailableIncomingShareIdRef.current = null;
2026-10-24T02:58:54.9018219Z 594 │ }
2026-10-24T02:58:54.9018322Z 595 │ startedShareImportKeyRef.current = importKey;
2026-10-24T02:58:54.9018394Z 596 │ const draftBackup =
2026-10-24T02:58:54.9018577Z 597 │ shareImportDraftBackupRef.current.get(importKey) ?? getComposerDraftSnapshot(draftKey);
2026-10-24T02:58:54.9018711Z 598 │ shareImportDraftBackupRef.current.set(importKey, draftBackup);
2026-10-24T02:58:54.9018804Z 599 │ const importToken = Symbol(importKey);
2026-10-24T02:58:54.9018885Z 600 │ let didReserveShare = false;
2026-10-24T02:58:54.9018961Z 601 │ let didConsumeShare = false;
2026-10-24T02:58:54.9019039Z 602 │ let needsDraftRestore = false;
2026-10-24T02:58:54.9019145Z 603 │ activeShareImportTokenRef.current = importToken;
2026-10-24T02:58:54.9019229Z 604 │ setImportingShareKey(importKey);
2026-10-24T02:58:54.9019313Z · ──────────┬─────────
2026-10-24T02:58:54.9019499Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9019642Z 605 │ void (async () => {
2026-10-24T02:58:54.9019693Z ╰────
2026-10-24T02:58:54.9020374Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9020728Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9020731Z
2026-10-24T02:58:54.9020929Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9021078Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:524:5]
2026-10-24T02:58:54.9021152Z 523 │ props.initialProjectRef,
2026-10-24T02:58:54.9021224Z 524 │ props.incomingShareId,
2026-10-24T02:58:54.9021308Z · ──────────┬──────────
2026-10-24T02:58:54.9021478Z · ╰── Unnecessary dependency `props.incomingShareId`
2026-10-24T02:58:54.9021550Z 525 │ props.pendingTaskId,
2026-10-24T02:58:54.9021601Z ╰────
2026-10-24T02:58:54.9021886Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9022192Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9022195Z
2026-10-24T02:58:54.9022406Z ⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
2026-10-24T02:58:54.9022552Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:543:5]
2026-10-24T02:58:54.9022665Z 542 │ loadedBranchesProjectKeyRef.current = projectKey;
2026-10-24T02:58:54.9022735Z 543 │ flow.loadBranches();
2026-10-24T02:58:54.9022807Z · ──┬─
2026-10-24T02:58:54.9022929Z · ╰── Missing dependency `flow`
2026-10-24T02:58:54.9023020Z 544 │ }, [flow.loadBranches, selectedProject]);
2026-10-24T02:58:54.9023102Z · ────────┬────────
2026-10-24T02:58:54.9023296Z · ╰── Overly precise dependency `flow.loadBranches`, use `flow` instead
2026-10-24T02:58:54.9023348Z 545 │
2026-10-24T02:58:54.9023400Z ╰────
2026-10-24T02:58:54.9023809Z help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9024116Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9024122Z
2026-10-24T02:58:54.9024318Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9024465Z ╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:766:5]
2026-10-24T02:58:54.9024528Z 765 │ flow.draftKey,
2026-10-24T02:58:54.9024604Z 766 │ hasImportedIncomingShare,
2026-10-24T02:58:54.9024693Z · ────────────┬───────────
2026-10-24T02:58:54.9024863Z · ╰── Unnecessary dependency `hasImportedIncomingShare`
2026-10-24T02:58:54.9024926Z 767 │ incomingShare,
2026-10-24T02:58:54.9025004Z 768 │ isIncomingShareInboxLoading,
2026-10-24T02:58:54.9025098Z · ─────────────┬─────────────
2026-10-24T02:58:54.9025327Z · ╰── Unnecessary dependency `isIncomingShareInboxLoading`
2026-10-24T02:58:54.9025436Z 769 │ isIncomingShareUnavailable,
2026-10-24T02:58:54.9025506Z 770 │ props.incomingShareId,
2026-10-24T02:58:54.9025598Z 771 │ props.initialProjectRef?.environmentId,
2026-10-24T02:58:54.9025683Z 772 │ props.initialProjectRef?.projectId,
2026-10-24T02:58:54.9025755Z 773 │ releaseShareReservation,
2026-10-24T02:58:54.9025818Z 774 │ reserveShare,
2026-10-24T02:58:54.9025903Z 775 │ selectedEnvironmentServerConfig,
2026-10-24T02:58:54.9025969Z 776 │ selectedProject,
2026-10-24T02:58:54.9026035Z 777 │ shareImportAttempt,
2026-10-24T02:58:54.9026120Z · ─────────┬────────
2026-10-24T02:58:54.9026285Z · ╰── Unnecessary dependency `shareImportAttempt`
2026-10-24T02:58:54.9026342Z 778 │ ]);
2026-10-24T02:58:54.9026391Z ╰────
2026-10-24T02:58:54.9026676Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9026980Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9026983Z
2026-10-24T02:58:54.9027257Z ⚠ eslint(no-unused-vars): Variable 'useDragRegion' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.9027402Z ╭─[apps/web/src/components/preview/PreviewPanelShell.tsx:61:9]
2026-10-24T02:58:54.9027454Z 60 │ ) {
2026-10-24T02:58:54.9027626Z 61 │ const useDragRegion = isElectron && props.mode !== "sheet" && props.mode !== "embedded";
2026-10-24T02:58:54.9027709Z · ──────┬──────
2026-10-24T02:58:54.9027848Z · ╰── 'useDragRegion' is declared here
2026-10-24T02:58:54.9027935Z 62 │ const isInline = props.mode === "inline";
2026-10-24T02:58:54.9027988Z ╰────
2026-10-24T02:58:54.9028093Z help: Consider removing this declaration.
2026-10-24T02:58:54.9028095Z
2026-10-24T02:58:54.9028248Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9028399Z ╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
2026-10-24T02:58:54.9028454Z 86 │
2026-10-24T02:58:54.9028546Z 87 │ const cardCoverage = props.cardCoverage;
2026-10-24T02:58:54.9028627Z · ──────┬─────
2026-10-24T02:58:54.9028811Z · ╰── `cardCoverage` originates here
2026-10-24T02:58:54.9028920Z 88 │ const barHeightRef = useRef(0);
2026-10-24T02:58:54.9029000Z 89 │ const cardHeightRef = useRef(0);
2026-10-24T02:58:54.9029085Z 90 │ const cardHeight = useSharedValue(0);
2026-10-24T02:58:54.9029175Z 91 │ const notifyCoverage = useCallback(() => {
2026-10-24T02:58:54.9029243Z 92 │ if (!cardCoverage) {
2026-10-24T02:58:54.9029307Z 93 │ return;
2026-10-24T02:58:54.9029361Z 94 │ }
2026-10-24T02:58:54.9029506Z 95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
2026-10-24T02:58:54.9029593Z 96 │ if (coverage === cardCoverage.value) {
2026-10-24T02:58:54.9029652Z 97 │ return;
2026-10-24T02:58:54.9029708Z 98 │ }
2026-10-24T02:58:54.9029786Z 99 │ if (cardCoverage.value === 0) {
2026-10-24T02:58:54.9029883Z 100 │ cardCoverage.value = coverage;
2026-10-24T02:58:54.9029998Z · ──────┬─────
2026-10-24T02:58:54.9030145Z · ╰── `cardCoverage` cannot be modified
2026-10-24T02:58:54.9030203Z 101 │ return;
2026-10-24T02:58:54.9030256Z ╰────
2026-10-24T02:58:54.9030544Z help: Do not mutate component props or hook arguments. If the value should change, update it where it is owned and pass an update callback, or use local state
2026-10-24T02:58:54.9030843Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9030845Z
2026-10-24T02:58:54.9030996Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9031157Z ╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:118:7]
2026-10-24T02:58:54.9031240Z 89 │ const cardHeightRef = useRef(0);
2026-10-24T02:58:54.9031325Z 90 │ const cardHeight = useSharedValue(0);
2026-10-24T02:58:54.9031400Z · ─────┬────
2026-10-24T02:58:54.9031535Z · ╰── `cardHeight` originates here
2026-10-24T02:58:54.9031627Z 91 │ const notifyCoverage = useCallback(() => {
2026-10-24T02:58:54.9031695Z 92 │ if (!cardCoverage) {
2026-10-24T02:58:54.9031752Z 93 │ return;
2026-10-24T02:58:54.9031807Z 94 │ }
2026-10-24T02:58:54.9031953Z 95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
2026-10-24T02:58:54.9032039Z 96 │ if (coverage === cardCoverage.value) {
2026-10-24T02:58:54.9032095Z 97 │ return;
2026-10-24T02:58:54.9032151Z 98 │ }
2026-10-24T02:58:54.9032239Z 99 │ if (cardCoverage.value === 0) {
2026-10-24T02:58:54.9032324Z 100 │ cardCoverage.value = coverage;
2026-10-24T02:58:54.9032380Z 101 │ return;
2026-10-24T02:58:54.9032435Z 102 │ }
2026-10-24T02:58:54.9032536Z 103 │ cardCoverage.value = withTiming(coverage, {
2026-10-24T02:58:54.9032629Z 104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
2026-10-24T02:58:54.9032713Z 105 │ easing: Easing.out(Easing.cubic),
2026-10-24T02:58:54.9032770Z 106 │ });
2026-10-24T02:58:54.9032839Z 107 │ }, [cardCoverage]);
2026-10-24T02:58:54.9032920Z 108 │ const handleBarLayout = useCallback(
2026-10-24T02:58:54.9033000Z 109 │ (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.9033127Z 110 │ barHeightRef.current = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9033196Z 111 │ notifyCoverage();
2026-10-24T02:58:54.9033251Z 112 │ },
2026-10-24T02:58:54.9033376Z 113 │ [notifyCoverage],
2026-10-24T02:58:54.9033461Z 114 │ );
2026-10-24T02:58:54.9033544Z 115 │ const handleCardLayout = useCallback(
2026-10-24T02:58:54.9033623Z 116 │ (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.9033749Z 117 │ cardHeightRef.current = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9033862Z 118 │ cardHeight.value = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9033938Z · ─────┬────
2026-10-24T02:58:54.9034072Z · ╰── `cardHeight` cannot be modified
2026-10-24T02:58:54.9034141Z 119 │ notifyCoverage();
2026-10-24T02:58:54.9034193Z ╰────
2026-10-24T02:58:54.9034452Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9034755Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9034760Z
2026-10-24T02:58:54.9034958Z ⚠ react(immutability): Cannot modify local variables after render completes
2026-10-24T02:58:54.9035112Z ╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
2026-10-24T02:58:54.9035196Z 90 │ const cardHeight = useSharedValue(0);
2026-10-24T02:58:54.9035287Z 91 │ const notifyCoverage = useCallback(() => {
2026-10-24T02:58:54.9035392Z · ───┬───
2026-10-24T02:58:54.9035628Z · ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
2026-10-24T02:58:54.9035697Z 92 │ if (!cardCoverage) {
2026-10-24T02:58:54.9035763Z 93 │ return;
2026-10-24T02:58:54.9035819Z 94 │ }
2026-10-24T02:58:54.9035966Z 95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
2026-10-24T02:58:54.9036052Z 96 │ if (coverage === cardCoverage.value) {
2026-10-24T02:58:54.9036108Z 97 │ return;
2026-10-24T02:58:54.9036164Z 98 │ }
2026-10-24T02:58:54.9036246Z 99 │ if (cardCoverage.value === 0) {
2026-10-24T02:58:54.9036328Z 100 │ cardCoverage.value = coverage;
2026-10-24T02:58:54.9036405Z · ──────┬─────
2026-10-24T02:58:54.9036539Z · ╰── This modifies `cardCoverage`
2026-10-24T02:58:54.9036604Z 101 │ return;
2026-10-24T02:58:54.9036656Z ╰────
2026-10-24T02:58:54.9036994Z help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
2026-10-24T02:58:54.9037296Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9037299Z
2026-10-24T02:58:54.9037495Z ⚠ react(immutability): Cannot modify local variables after render completes
2026-10-24T02:58:54.9037648Z ╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
2026-10-24T02:58:54.9037728Z 99 │ if (cardCoverage.value === 0) {
2026-10-24T02:58:54.9037807Z 100 │ cardCoverage.value = coverage;
2026-10-24T02:58:54.9037886Z · ──────┬─────
2026-10-24T02:58:54.9038016Z · ╰── This modifies `cardCoverage`
2026-10-24T02:58:54.9038126Z 101 │ return;
2026-10-24T02:58:54.9038293Z 102 │ }
2026-10-24T02:58:54.9038396Z 103 │ cardCoverage.value = withTiming(coverage, {
2026-10-24T02:58:54.9038491Z 104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
2026-10-24T02:58:54.9038575Z 105 │ easing: Easing.out(Easing.cubic),
2026-10-24T02:58:54.9038630Z 106 │ });
2026-10-24T02:58:54.9038696Z 107 │ }, [cardCoverage]);
2026-10-24T02:58:54.9038779Z 108 │ const handleBarLayout = useCallback(
2026-10-24T02:58:54.9038857Z 109 │ (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.9038963Z · ───────────────┬───────────────
2026-10-24T02:58:54.9039182Z · ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
2026-10-24T02:58:54.9039307Z 110 │ barHeightRef.current = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9039362Z ╰────
2026-10-24T02:58:54.9039695Z help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
2026-10-24T02:58:54.9040042Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9040044Z
2026-10-24T02:58:54.9040241Z ⚠ react(immutability): Cannot modify local variables after render completes
2026-10-24T02:58:54.9040395Z ╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:118:7]
2026-10-24T02:58:54.9040478Z 115 │ const handleCardLayout = useCallback(
2026-10-24T02:58:54.9040560Z 116 │ (event: LayoutChangeEvent) => {
2026-10-24T02:58:54.9040669Z · ───────────────┬───────────────
2026-10-24T02:58:54.9040885Z · ╰── This function may (indirectly) reassign or modify `cardHeight` after render
2026-10-24T02:58:54.9041010Z 117 │ cardHeightRef.current = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9041124Z 118 │ cardHeight.value = event.nativeEvent.layout.height;
2026-10-24T02:58:54.9041200Z · ─────┬────
2026-10-24T02:58:54.9041329Z · ╰── This modifies `cardHeight`
2026-10-24T02:58:54.9041395Z 119 │ notifyCoverage();
2026-10-24T02:58:54.9041448Z ╰────
2026-10-24T02:58:54.9041776Z help: This argument is a function which may reassign or mutate `cardHeight` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
2026-10-24T02:58:54.9042077Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9042081Z
2026-10-24T02:58:54.9042335Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9042491Z ╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:40:5]
2026-10-24T02:58:54.9042604Z 37 │ const [initialized, setInitialized] = useState(false);
2026-10-24T02:58:54.9042673Z 38 │ useLayoutEffect(() => {
2026-10-24T02:58:54.9042749Z · ───────┬───────
2026-10-24T02:58:54.9042878Z · ╰── This is the containing effect
2026-10-24T02:58:54.9042941Z 39 │ reset();
2026-10-24T02:58:54.9043010Z 40 │ setInitialized(true);
2026-10-24T02:58:54.9043140Z · ───────┬──────
2026-10-24T02:58:54.9043335Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9043396Z 41 │ }, [reset]);
2026-10-24T02:58:54.9043450Z ╰────
2026-10-24T02:58:54.9044037Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9044352Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9044356Z
2026-10-24T02:58:54.9044609Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9044767Z ╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:93:5]
2026-10-24T02:58:54.9044820Z 88 │
2026-10-24T02:58:54.9044886Z 89 │ useEffect(() => {
2026-10-24T02:58:54.9044954Z · ────┬────
2026-10-24T02:58:54.9045082Z · ╰── This is the containing effect
2026-10-24T02:58:54.9045237Z 90 │ if (!needsPreparation || !initialProjectRef.branch || waitingForProject) return;
2026-10-24T02:58:54.9045338Z 91 │ const branchName = initialProjectRef.branch;
2026-10-24T02:58:54.9045403Z 92 │ let active = true;
2026-10-24T02:58:54.9045499Z 93 │ setPendingCheckouts((count) => count + 1);
2026-10-24T02:58:54.9045583Z · ─────────┬─────────
2026-10-24T02:58:54.9045765Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9045917Z 94 │ // Serialize replacements: ignoring a stale result cannot undo its Git mutation.
2026-10-24T02:58:54.9045969Z ╰────
2026-10-24T02:58:54.9046990Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9047306Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9047308Z
2026-10-24T02:58:54.9047550Z ⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
2026-10-24T02:58:54.9047703Z ╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:290:50]
2026-10-24T02:58:54.9047763Z 289 │ return (
2026-10-24T02:58:54.9047895Z 290 │ <ExistingThreadSettingsRouteContext.Provider value={value}>
2026-10-24T02:58:54.9048147Z · ─────────────
2026-10-24T02:58:54.9048215Z 291 │ {props.children}
2026-10-24T02:58:54.9048267Z ╰────
2026-10-24T02:58:54.9048488Z help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
2026-10-24T02:58:54.9048627Z Alternatively, move the value outside the render function if it doesn't depend on props or state.
2026-10-24T02:58:54.9048629Z
2026-10-24T02:58:54.9048918Z ⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
2026-10-24T02:58:54.9049106Z ╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:654:44]
2026-10-24T02:58:54.9049165Z 653 │ return (
2026-10-24T02:58:54.9049284Z 654 │ <ThreadSettingsSessionContext.Provider value={value}>
2026-10-24T02:58:54.9049396Z · ─────────────
2026-10-24T02:58:54.9049464Z 655 │ {props.children}
2026-10-24T02:58:54.9049516Z ╰────
2026-10-24T02:58:54.9049733Z help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
2026-10-24T02:58:54.9049908Z Alternatively, move the value outside the render function if it doesn't depend on props or state.
2026-10-24T02:58:54.9049913Z
2026-10-24T02:58:54.9050145Z ⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
2026-10-24T02:58:54.9050305Z ╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:1462:55]
2026-10-24T02:58:54.9050373Z 1461 │ return (
2026-10-24T02:58:54.9050533Z 1462 │ <ThreadSettingsPickerPresentationContext.Provider value={presentation}>
2026-10-24T02:58:54.9050661Z · ────────────────────
2026-10-24T02:58:54.9050759Z 1463 │ <ThreadSettingsPickerStack.Navigator
2026-10-24T02:58:54.9050812Z ╰────
2026-10-24T02:58:54.9051026Z help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
2026-10-24T02:58:54.9051157Z Alternatively, move the value outside the render function if it doesn't depend on props or state.
2026-10-24T02:58:54.9051159Z
2026-10-24T02:58:54.9051416Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9051599Z ╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:119:10]
2026-10-24T02:58:54.9051651Z 117 │
2026-10-24T02:58:54.9051714Z 118 │ useEffect(() => {
2026-10-24T02:58:54.9051787Z · ────┬────
2026-10-24T02:58:54.9051916Z · ╰── This is the containing effect
2026-10-24T02:58:54.9051998Z 119 │ void refreshNotifications();
2026-10-24T02:58:54.9052086Z · ──────────┬─────────
2026-10-24T02:58:54.9052259Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9052401Z 120 │ const subscription = AppState.addEventListener("change", (state) => {
2026-10-24T02:58:54.9052453Z ╰────
2026-10-24T02:58:54.9053084Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9053431Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9053434Z
2026-10-24T02:58:54.9053684Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9053868Z ╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:128:7]
2026-10-24T02:58:54.9053920Z 125 │
2026-10-24T02:58:54.9053988Z 126 │ useEffect(() => {
2026-10-24T02:58:54.9054062Z · ────┬────
2026-10-24T02:58:54.9054191Z · ╰── This is the containing effect
2026-10-24T02:58:54.9054257Z 127 │ if (!isLoaded) {
2026-10-24T02:58:54.9054345Z 128 │ setLiveActivityStatus("checking");
2026-10-24T02:58:54.9054434Z · ──────────┬──────────
2026-10-24T02:58:54.9054603Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9054665Z 129 │ return;
2026-10-24T02:58:54.9054715Z ╰────
2026-10-24T02:58:54.9055305Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9055619Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9055621Z
2026-10-24T02:58:54.9055869Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9056025Z ╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:444:5]
2026-10-24T02:58:54.9056085Z 434 │ : null;
2026-10-24T02:58:54.9056152Z 435 │ useEffect(() => {
2026-10-24T02:58:54.9056221Z · ────┬────
2026-10-24T02:58:54.9056347Z · ╰── This is the containing effect
2026-10-24T02:58:54.9056404Z 436 │ if (
2026-10-24T02:58:54.9056487Z 437 │ props.active === false ||
2026-10-24T02:58:54.9056566Z 438 │ activeDraftKey !== null ||
2026-10-24T02:58:54.9056648Z 439 │ editingPendingTask !== null ||
2026-10-24T02:58:54.9056722Z 440 │ selectedProject === null
2026-10-24T02:58:54.9056778Z 441 │ ) {
2026-10-24T02:58:54.9056838Z 442 │ return;
2026-10-24T02:58:54.9056891Z 443 │ }
2026-10-24T02:58:54.9056960Z 444 │ setActiveDraftKey(
2026-10-24T02:58:54.9057043Z · ────────┬────────
2026-10-24T02:58:54.9057208Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9057279Z 445 │ createNewTaskDraft({
2026-10-24T02:58:54.9057334Z ╰────
2026-10-24T02:58:54.9057968Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9058307Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9058310Z
2026-10-24T02:58:54.9058542Z ⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
2026-10-24T02:58:54.9058702Z ╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:1244:36]
2026-10-24T02:58:54.9058807Z 1243 │ <ActiveNewTaskContext value={activeNewTask}>
2026-10-24T02:58:54.9059002Z 1244 │ <NewTaskFlowContext.Provider value={value}>{props.children}</NewTaskFlowContext.Provider>
2026-10-24T02:58:54.9059118Z · ─────────────
2026-10-24T02:58:54.9059194Z 1245 │ </ActiveNewTaskContext>
2026-10-24T02:58:54.9059245Z ╰────
2026-10-24T02:58:54.9059535Z help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
2026-10-24T02:58:54.9059706Z Alternatively, move the value outside the render function if it doesn't depend on props or state.
2026-10-24T02:58:54.9059709Z
2026-10-24T02:58:54.9059909Z ⚠ react(purity): Cannot call impure function during render
2026-10-24T02:58:54.9060074Z ╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:697:76]
2026-10-24T02:58:54.9060255Z 696 │ const [snoozeGateClock, setSnoozeGateClock] = useState(() => ({ thread, now: Date.now() }));
2026-10-24T02:58:54.9060425Z 697 │ if (snoozeGateClock.thread !== thread) setSnoozeGateClock({ thread, now: Date.now() });
2026-10-24T02:58:54.9060561Z · ─────┬────
2026-10-24T02:58:54.9060738Z · ╰── Cannot call impure function
2026-10-24T02:58:54.9060874Z 698 │ const snoozeGateNow = new Date(snoozeGateClock.now).toISOString();
2026-10-24T02:58:54.9060927Z ╰────
2026-10-24T02:58:54.9061206Z help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
2026-10-24T02:58:54.9061496Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
2026-10-24T02:58:54.9061498Z
2026-10-24T02:58:54.9061666Z ⚠ react(purity): Cannot call impure function during render
2026-10-24T02:58:54.9061822Z ╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:718:71]
2026-10-24T02:58:54.9061902Z 717 │ const snoozePresets = useMemo(
2026-10-24T02:58:54.9062079Z 718 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
2026-10-24T02:58:54.9062205Z · ─────┬────
2026-10-24T02:58:54.9062381Z · ╰── Cannot call impure function
2026-10-24T02:58:54.9062497Z 719 │ [props.snoozePresetMinute, swipeActions.secondary],
2026-10-24T02:58:54.9062549Z ╰────
2026-10-24T02:58:54.9062882Z help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
2026-10-24T02:58:54.9063207Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
2026-10-24T02:58:54.9063209Z
2026-10-24T02:58:54.9063388Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.9063540Z ╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:719:6]
2026-10-24T02:58:54.9063715Z 718 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
2026-10-24T02:58:54.9063827Z 719 │ [props.snoozePresetMinute, swipeActions.secondary],
2026-10-24T02:58:54.9063920Z · ────────────┬───────────
2026-10-24T02:58:54.9064100Z · ╰── Unnecessary dependency `props.snoozePresetMinute`
2026-10-24T02:58:54.9064158Z 720 │ );
2026-10-24T02:58:54.9064208Z ╰────
2026-10-24T02:58:54.9064517Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9064823Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9064826Z
2026-10-24T02:58:54.9065002Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.9065151Z ╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:765:7]
2026-10-24T02:58:54.9065218Z 764 │ thread.pinnedAt,
2026-10-24T02:58:54.9065281Z 765 │ variant,
2026-10-24T02:58:54.9065362Z · ───┬───
2026-10-24T02:58:54.9065496Z · ╰── Unnecessary dependency `variant`
2026-10-24T02:58:54.9065554Z 766 │ ],
2026-10-24T02:58:54.9065606Z ╰────
2026-10-24T02:58:54.9065914Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9066220Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9066222Z
2026-10-24T02:58:54.9066411Z ⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
2026-10-24T02:58:54.9066573Z ╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:1215:21]
2026-10-24T02:58:54.9066703Z 1214 │ {providerDrivers.slice(0, -1).map((driver, index) => (
2026-10-24T02:58:54.9068348Z 1215 │ <View key={`${driver}:${index}`} className="-mr-1 opacity-30">
2026-10-24T02:58:54.9068469Z · ──────────────────────────
2026-10-24T02:58:54.9068578Z 1216 │ <ProviderIcon provider={driver} size={12} />
2026-10-24T02:58:54.9068629Z ╰────
2026-10-24T02:58:54.9068774Z help: Use a unique data-dependent key to avoid unnecessary rerenders
2026-10-24T02:58:54.9068777Z
2026-10-24T02:58:54.9069031Z ⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.9069159Z ╭─[packages/provider-pi/src/server/adapter.ts:3405:7]
2026-10-24T02:58:54.9069214Z 3404 │
2026-10-24T02:58:54.9069479Z 3405 │ const layer: Layer.Layer<ProviderAdapter.ProviderAdapterV2, never, PiAdapterV2DriverEnv> =
2026-10-24T02:58:54.9069578Z · ──┬──
2026-10-24T02:58:54.9069703Z · ╰── 'layer' is declared here
2026-10-24T02:58:54.9069768Z 3406 │ Layer.effect(
2026-10-24T02:58:54.9069818Z ╰────
2026-10-24T02:58:54.9069931Z help: Consider removing this declaration.
2026-10-24T02:58:54.9069934Z
2026-10-24T02:58:54.9070156Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.9070315Z ╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:100:85]
2026-10-24T02:58:54.9070418Z 99 │ const startEditor = startScheduledTaskEditor;
2026-10-24T02:58:54.9070602Z 100 │ const resetEditor = useCallback(() => startEditor(defaultEditor), [defaultEditor, startEditor]);
2026-10-24T02:58:54.9070746Z · ─────┬─────
2026-10-24T02:58:54.9070943Z · ╰── Unnecessary dependency `startEditor`
2026-10-24T02:58:54.9071021Z 101 │ const readEditor = useCallback(
2026-10-24T02:58:54.9071071Z ╰────
2026-10-24T02:58:54.9071376Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9071681Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9071683Z
2026-10-24T02:58:54.9071864Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.9072021Z ╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:121:7]
2026-10-24T02:58:54.9072082Z 120 │ setEditor,
2026-10-24T02:58:54.9072145Z 121 │ startEditor,
2026-10-24T02:58:54.9072220Z · ─────┬─────
2026-10-24T02:58:54.9072361Z · ╰── Unnecessary dependency `startEditor`
2026-10-24T02:58:54.9072423Z 122 │ hasChanges,
2026-10-24T02:58:54.9072474Z ╰────
2026-10-24T02:58:54.9072779Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9073088Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9073093Z
2026-10-24T02:58:54.9073344Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9073491Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:512:5]
2026-10-24T02:58:54.9073550Z 510 │ }, []);
2026-10-24T02:58:54.9073615Z 511 │ useEffect(() => {
2026-10-24T02:58:54.9073686Z · ────┬────
2026-10-24T02:58:54.9073811Z · ╰── This is the containing effect
2026-10-24T02:58:54.9073897Z 512 │ setKeyboardStateSuspect(false);
2026-10-24T02:58:54.9073986Z · ───────────┬───────────
2026-10-24T02:58:54.9074206Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9074334Z 513 │ }, [isKeyboardVisible, liveKeyboardHeight]);
2026-10-24T02:58:54.9074384Z ╰────
2026-10-24T02:58:54.9074968Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9075280Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9075284Z
2026-10-24T02:58:54.9075534Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9075689Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:872:7]
2026-10-24T02:58:54.9075844Z 869 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
2026-10-24T02:58:54.9075909Z 870 │ useEffect(() => {
2026-10-24T02:58:54.9075979Z · ────┬────
2026-10-24T02:58:54.9076103Z · ╰── This is the containing effect
2026-10-24T02:58:54.9076260Z 871 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
2026-10-24T02:58:54.9076370Z 872 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
2026-10-24T02:58:54.9076464Z · ─────────────┬────────────
2026-10-24T02:58:54.9076634Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9076690Z 873 │ }
2026-10-24T02:58:54.9076740Z ╰────
2026-10-24T02:58:54.9077329Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9077645Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9077647Z
2026-10-24T02:58:54.9077896Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9078048Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1119:5]
2026-10-24T02:58:54.9078100Z 1117 │
2026-10-24T02:58:54.9078171Z 1118 │ useEffect(() => {
2026-10-24T02:58:54.9078241Z · ────┬────
2026-10-24T02:58:54.9078369Z · ╰── This is the containing effect
2026-10-24T02:58:54.9078445Z 1119 │ setAnchorMessageId(null);
2026-10-24T02:58:54.9078528Z · ─────────┬────────
2026-10-24T02:58:54.9078693Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9078773Z 1120 │ setSubmittedMessageId(null);
2026-10-24T02:58:54.9078824Z ╰────
2026-10-24T02:58:54.9079406Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9079767Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9079802Z
2026-10-24T02:58:54.9080041Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9080191Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:513:7]
2026-10-24T02:58:54.9080273Z 512 │ setKeyboardStateSuspect(false);
2026-10-24T02:58:54.9080369Z 513 │ }, [isKeyboardVisible, liveKeyboardHeight]);
2026-10-24T02:58:54.9080503Z · ────────┬──────── ─────────┬────────
2026-10-24T02:58:54.9080706Z · │ ╰── Unnecessary dependency `liveKeyboardHeight`
2026-10-24T02:58:54.9080865Z · ╰── Unnecessary dependency `isKeyboardVisible`
2026-10-24T02:58:54.9080992Z 514 │ const handleOwnedInputFocusChange = (focused: boolean) => {
2026-10-24T02:58:54.9081041Z ╰────
2026-10-24T02:58:54.9081326Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9081626Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9081628Z
2026-10-24T02:58:54.9081823Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9081973Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1067:7]
2026-10-24T02:58:54.9082060Z 1066 │ userInputInsetProgress.set(1);
2026-10-24T02:58:54.9082221Z 1067 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
2026-10-24T02:58:54.9082313Z · ────────────┬───────────
2026-10-24T02:58:54.9082487Z · ╰── Unnecessary dependency `activeUserInputRequestId`
2026-10-24T02:58:54.9082591Z 1068 │ const showContent = props.showContent ?? true;
2026-10-24T02:58:54.9082643Z ╰────
2026-10-24T02:58:54.9082927Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9083231Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9083233Z
2026-10-24T02:58:54.9083476Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9083654Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1125:15]
2026-10-24T02:58:54.9083722Z 1124 │ freeze.set(false);
2026-10-24T02:58:54.9083803Z 1125 │ }, [freeze, selectedThreadKey]);
2026-10-24T02:58:54.9083895Z · ────────┬────────
2026-10-24T02:58:54.9084055Z · ╰── Unnecessary dependency `selectedThreadKey`
2026-10-24T02:58:54.9084108Z 1126 │
2026-10-24T02:58:54.9084158Z ╰────
2026-10-24T02:58:54.9084444Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9084748Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9084753Z
2026-10-24T02:58:54.9084907Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9085054Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:955:5]
2026-10-24T02:58:54.9085162Z 950 │ const composerPopoverHeight = useSharedValue(0);
2026-10-24T02:58:54.9085264Z 951 │ const floatingControlCoverage = useSharedValue(
2026-10-24T02:58:54.9085356Z · ───────────┬───────────
2026-10-24T02:58:54.9085513Z · ╰── `floatingControlCoverage` originates here
2026-10-24T02:58:54.9085636Z 952 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
2026-10-24T02:58:54.9085689Z 953 │ );
2026-10-24T02:58:54.9085761Z 954 │ useEffect(() => {
2026-10-24T02:58:54.9085864Z 955 │ floatingControlCoverage.value = withTiming(
2026-10-24T02:58:54.9085951Z · ───────────┬───────────
2026-10-24T02:58:54.9086107Z · ╰── `floatingControlCoverage` cannot be modified
2026-10-24T02:58:54.9086232Z 956 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
2026-10-24T02:58:54.9086284Z ╰────
2026-10-24T02:58:54.9086545Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9086846Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9086850Z
2026-10-24T02:58:54.9087005Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9087154Z ╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:973:7]
2026-10-24T02:58:54.9087335Z 963 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
2026-10-24T02:58:54.9087455Z 964 │ const combinedContentInsetEndAdjustment = useSharedValue(
2026-10-24T02:58:54.9087562Z · ────────────────┬────────────────
2026-10-24T02:58:54.9087743Z · ╰── `combinedContentInsetEndAdjustment` originates here
2026-10-24T02:58:54.9087867Z 965 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
2026-10-24T02:58:54.9087921Z 966 │ );
2026-10-24T02:58:54.9087988Z 967 │ useAnimatedReaction(
2026-10-24T02:58:54.9088046Z 968 │ () =>
2026-10-24T02:58:54.9088192Z 969 │ contentInsetEndAdjustment.value +
2026-10-24T02:58:54.9088306Z 970 │ floatingControlCoverage.value +
2026-10-24T02:58:54.9088495Z 971 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
2026-10-24T02:58:54.9088556Z 972 │ (value) => {
2026-10-24T02:58:54.9088666Z 973 │ combinedContentInsetEndAdjustment.value = value;
2026-10-24T02:58:54.9088771Z · ────────────────┬────────────────
2026-10-24T02:58:54.9088956Z · ╰── `combinedContentInsetEndAdjustment` cannot be modified
2026-10-24T02:58:54.9089012Z 974 │ },
2026-10-24T02:58:54.9089062Z ╰────
2026-10-24T02:58:54.9089318Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9089619Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9089624Z
2026-10-24T02:58:54.9089818Z ⚠ eslint(no-unused-vars): Identifier 'Duration' is imported but never used.
2026-10-24T02:58:54.9089980Z ╭─[packages/provider-pi/src/server/adapter.test.ts:24:13]
2026-10-24T02:58:54.9090073Z 23 │ import * as Deferred from "effect/Deferred";
2026-10-24T02:58:54.9090162Z 24 │ import * as Duration from "effect/Duration";
2026-10-24T02:58:54.9090240Z · ────┬───
2026-10-24T02:58:54.9090371Z · ╰── 'Duration' is imported here
2026-10-24T02:58:54.9090455Z 25 │ import * as Effect from "effect/Effect";
2026-10-24T02:58:54.9090505Z ╰────
2026-10-24T02:58:54.9090606Z help: Consider removing this import.
2026-10-24T02:58:54.9090611Z
2026-10-24T02:58:54.9090862Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9091010Z ╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:57:5]
2026-10-24T02:58:54.9091061Z 55 │
2026-10-24T02:58:54.9091124Z 56 │ useEffect(() => {
2026-10-24T02:58:54.9091194Z · ────┬────
2026-10-24T02:58:54.9091491Z · ╰── This is the containing effect
2026-10-24T02:58:54.9091557Z 57 │ setDecodedSize(null);
2026-10-24T02:58:54.9091632Z · ───────┬──────
2026-10-24T02:58:54.9091796Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9091870Z 58 │ }, [props.sourceKey]);
2026-10-24T02:58:54.9091922Z ╰────
2026-10-24T02:58:54.9092504Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9092821Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9092824Z
2026-10-24T02:58:54.9093073Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9093219Z ╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:61:5]
2026-10-24T02:58:54.9093323Z 59 │
2026-10-24T02:58:54.9093424Z 60 │ useEffect(() => {
2026-10-24T02:58:54.9093493Z · ────┬────
2026-10-24T02:58:54.9093617Z · ╰── This is the containing effect
2026-10-24T02:58:54.9093682Z 61 │ setFailedUri(null);
2026-10-24T02:58:54.9093755Z · ──────┬─────
2026-10-24T02:58:54.9093916Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9093981Z 62 │ }, [props.uri]);
2026-10-24T02:58:54.9094029Z ╰────
2026-10-24T02:58:54.9094615Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9094932Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9094934Z
2026-10-24T02:58:54.9095144Z ⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
2026-10-24T02:58:54.9095290Z ╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:7:10]
2026-10-24T02:58:54.9095411Z 6 │ import { parse, SvgAst, type JsxAST } from "react-native-svg";
2026-10-24T02:58:54.9095589Z 7 │ import { ActivityIndicator, Pressable, StyleSheet, View, type ViewStyle } from "react-native";
2026-10-24T02:58:54.9095677Z · ────────┬────────
2026-10-24T02:58:54.9095826Z · ╰── 'ActivityIndicator' is imported here
2026-10-24T02:58:54.9095882Z 8 │
2026-10-24T02:58:54.9095936Z ╰────
2026-10-24T02:58:54.9096032Z help: Consider removing this import.
2026-10-24T02:58:54.9096034Z
2026-10-24T02:58:54.9096230Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9096376Z ╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:58:7]
2026-10-24T02:58:54.9096443Z 57 │ setDecodedSize(null);
2026-10-24T02:58:54.9096511Z 58 │ }, [props.sourceKey]);
2026-10-24T02:58:54.9096592Z · ───────┬───────
2026-10-24T02:58:54.9096739Z · ╰── Unnecessary dependency `props.sourceKey`
2026-10-24T02:58:54.9096792Z 59 │
2026-10-24T02:58:54.9096841Z ╰────
2026-10-24T02:58:54.9097135Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9097445Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9097447Z
2026-10-24T02:58:54.9097641Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9097788Z ╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:62:7]
2026-10-24T02:58:54.9097855Z 61 │ setFailedUri(null);
2026-10-24T02:58:54.9097921Z 62 │ }, [props.uri]);
2026-10-24T02:58:54.9097991Z · ────┬────
2026-10-24T02:58:54.9098129Z · ╰── Unnecessary dependency `props.uri`
2026-10-24T02:58:54.9098181Z 63 │
2026-10-24T02:58:54.9098231Z ╰────
2026-10-24T02:58:54.9098565Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9098900Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9098903Z
2026-10-24T02:58:54.9099111Z ⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
2026-10-24T02:58:54.9099278Z ╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:249:7]
2026-10-24T02:58:54.9099355Z 248 │ mountedRef.current = false;
2026-10-24T02:58:54.9099525Z 249 │ flow.setBranchQuery("");
2026-10-24T02:58:54.9099629Z · ──┬─
2026-10-24T02:58:54.9099765Z · ╰── Missing dependency `flow`
2026-10-24T02:58:54.9099822Z 250 │ };
2026-10-24T02:58:54.9099935Z 251 │ }, [flow.setBranchQuery]);
2026-10-24T02:58:54.9100025Z · ─────────┬─────────
2026-10-24T02:58:54.9100225Z · ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
2026-10-24T02:58:54.9100276Z 252 │
2026-10-24T02:58:54.9100329Z ╰────
2026-10-24T02:58:54.9100741Z help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9101050Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9101055Z
2026-10-24T02:58:54.9101305Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9101462Z ╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:285:5]
2026-10-24T02:58:54.9101581Z 283 │ const [snoozeWakeTick, bumpSnoozeWakeTick] = useState(0);
2026-10-24T02:58:54.9101646Z 284 │ useEffect(() => {
2026-10-24T02:58:54.9101717Z · ────┬────
2026-10-24T02:58:54.9101843Z · ╰── This is the containing effect
2026-10-24T02:58:54.9101926Z 285 │ setNow(new Date().toISOString());
2026-10-24T02:58:54.9101993Z · ───┬──
2026-10-24T02:58:54.9102153Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9102361Z 286 │ const id = setInterval(() => setNow(new Date().toISOString()), 60_000);
2026-10-24T02:58:54.9102459Z ╰────
2026-10-24T02:58:54.9103043Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9103362Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9103365Z
2026-10-24T02:58:54.9103560Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9103722Z ╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:365:25]
2026-10-24T02:58:54.9103855Z 364 │ // range) the boundary string is identical and the chain would die.
2026-10-24T02:58:54.9103944Z 365 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
2026-10-24T02:58:54.9104044Z · ───────┬──────
2026-10-24T02:58:54.9104204Z · ╰── Unnecessary dependency `snoozeWakeTick`
2026-10-24T02:58:54.9104317Z 366 │ const listItems = ((): readonly SidebarListItem[] => {
2026-10-24T02:58:54.9104369Z ╰────
2026-10-24T02:58:54.9104655Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9104961Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9104968Z
2026-10-24T02:58:54.9105131Z ⚠ react(purity): Cannot call impure function during render
2026-10-24T02:58:54.9105289Z ╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:356:53]
2026-10-24T02:58:54.9105375Z 355 │ if (Number.isNaN(wakeAtMs)) return;
2026-10-24T02:58:54.9105528Z 356 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
2026-10-24T02:58:54.9105645Z · ─────┬────
2026-10-24T02:58:54.9105805Z · ╰── Cannot call impure function
2026-10-24T02:58:54.9105883Z 357 │ const id = setTimeout(() => {
2026-10-24T02:58:54.9105935Z ╰────
2026-10-24T02:58:54.9106217Z help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
2026-10-24T02:58:54.9106508Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
2026-10-24T02:58:54.9106510Z
2026-10-24T02:58:54.9106762Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9106909Z ╭─[apps/mobile/src/features/threads/use-worktree-setup.ts:30:40]
2026-10-24T02:58:54.9107067Z 28 │ const snapshot = resolveWorktreeSetupSnapshot(input.threadId, query.data, live);
2026-10-24T02:58:54.9107130Z 29 │ useEffect(() => {
2026-10-24T02:58:54.9107200Z · ────┬────
2026-10-24T02:58:54.9107374Z · ╰── This is the containing effect
2026-10-24T02:58:54.9107639Z 30 │ if (snapshot && snapshot !== live) setHeld({ key, snapshot });
2026-10-24T02:58:54.9107740Z · ───┬───
2026-10-24T02:58:54.9107929Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9108001Z 31 │ }, [key, live, snapshot]);
2026-10-24T02:58:54.9108052Z ╰────
2026-10-24T02:58:54.9108632Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9108951Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9108955Z
2026-10-24T02:58:54.9109155Z ⚠ unicorn(require-module-specifiers): Empty import specifier is not allowed
2026-10-24T02:58:54.9109319Z ╭─[apps/server/src/sourceControl/SourceControlProviderRegistry.ts:15:13]
2026-10-24T02:58:54.9109390Z 14 │ } from "@t3tools/contracts";
2026-10-24T02:58:54.9109479Z 15 │ import type {} from "@t3tools/contracts";
2026-10-24T02:58:54.9109546Z · ──
2026-10-24T02:58:54.9109725Z 16 │ import { detectSourceControlProviderFromRemoteUrl } from "@t3tools/shared/sourceControl";
2026-10-24T02:58:54.9109777Z ╰────
2026-10-24T02:58:54.9109892Z help: Remove empty braces
2026-10-24T02:58:54.9109895Z
2026-10-24T02:58:54.9110154Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9110328Z ╭─[apps/mobile/src/features/threads/thread-inspector-content-stack.tsx:60:5]
2026-10-24T02:58:54.9110383Z 58 │
2026-10-24T02:58:54.9110444Z 59 │ useEffect(() => {
2026-10-24T02:58:54.9110512Z · ────┬────
2026-10-24T02:58:54.9110640Z · ╰── This is the containing effect
2026-10-24T02:58:54.9110720Z 60 │ setMountedModes((current) => {
2026-10-24T02:58:54.9110797Z · ───────┬───────
2026-10-24T02:58:54.9110961Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9111044Z 61 │ if (current.has(props.mode)) {
2026-10-24T02:58:54.9111094Z ╰────
2026-10-24T02:58:54.9111681Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9111997Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9112000Z
2026-10-24T02:58:54.9112251Z ⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.9112391Z ╭─[packages/provider-opencode/src/server/adapter.ts:3755:7]
2026-10-24T02:58:54.9112446Z 3754 │
2026-10-24T02:58:54.9112692Z 3755 │ const layer: Layer.Layer<ProviderAdapter.ProviderAdapterV2, never, OpenCodeAdapterV2DriverEnv> =
2026-10-24T02:58:54.9112793Z · ──┬──
2026-10-24T02:58:54.9112916Z · ╰── 'layer' is declared here
2026-10-24T02:58:54.9112980Z 3756 │ Layer.effect(
2026-10-24T02:58:54.9113029Z ╰────
2026-10-24T02:58:54.9113132Z help: Consider removing this declaration.
2026-10-24T02:58:54.9113134Z
2026-10-24T02:58:54.9113295Z ⚠ eslint(no-empty-pattern): Empty array binding pattern
2026-10-24T02:58:54.9113447Z ╭─[apps/server/src/pullRequest/PullRequestService.test.ts:1526:12]
2026-10-24T02:58:54.9113498Z 1525 │
2026-10-24T02:58:54.9113567Z 1526 │ for (const [] of [
2026-10-24T02:58:54.9113637Z · ──
2026-10-24T02:58:54.9113708Z 1527 │ ["github", "github.com"],
2026-10-24T02:58:54.9113764Z ╰────
2026-10-24T02:58:54.9114037Z help: Passing non-iterable values (null, undefined, numbers, booleans, etc.) will result in a runtime error because these values are not iterable.
2026-10-24T02:58:54.9114040Z
2026-10-24T02:58:54.9114204Z ⚠ eslint(no-empty-pattern): Empty object binding pattern
2026-10-24T02:58:54.9114390Z ╭─[packages/provider-opencode/src/server/OpenCodeRuntime.environment.test.ts:53:14]
2026-10-24T02:58:54.9114442Z 52 │
2026-10-24T02:58:54.9114507Z 53 │ for (const {} of [
2026-10-24T02:58:54.9114575Z · ──
2026-10-24T02:58:54.9114640Z 54 │ { healthy: true },
2026-10-24T02:58:54.9114690Z ╰────
2026-10-24T02:58:54.9114915Z help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
2026-10-24T02:58:54.9114917Z
2026-10-24T02:58:54.9115173Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9115339Z ╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:215:7]
2026-10-24T02:58:54.9115391Z 211 │ };
2026-10-24T02:58:54.9115454Z 212 │ useEffect(() => {
2026-10-24T02:58:54.9115528Z · ────┬────
2026-10-24T02:58:54.9115657Z · ╰── This is the containing effect
2026-10-24T02:58:54.9115827Z 213 │ const inserted = ownerKey ? readComposerDraftSelection(ownerKey, draftMessage) : null;
2026-10-24T02:58:54.9115890Z 214 │ if (inserted) {
2026-10-24T02:58:54.9115966Z 215 │ setSelection((current) =>
2026-10-24T02:58:54.9116043Z · ──────┬─────
2026-10-24T02:58:54.9116213Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9116383Z 216 │ current.start === inserted.start && current.end === inserted.end ? current : inserted,
2026-10-24T02:58:54.9116433Z ╰────
2026-10-24T02:58:54.9117018Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9117329Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9117332Z
2026-10-24T02:58:54.9117712Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9117898Z ╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:296:7]
2026-10-24T02:58:54.9117975Z 284 │ }, [hasWorkspaceSnapshot]);
2026-10-24T02:58:54.9118039Z 285 │ useEffect(() => {
2026-10-24T02:58:54.9118107Z · ────┬────
2026-10-24T02:58:54.9118233Z · ╰── This is the containing effect
2026-10-24T02:58:54.9118377Z 286 │ if (!environmentId || !projectCwd || !selectedProviderInstanceId) return;
2026-10-24T02:58:54.9118523Z 287 │ const key = `${environmentId}:${selectedProviderInstanceId}:${projectCwd}`;
2026-10-24T02:58:54.9118591Z 288 │ const now = Date.now();
2026-10-24T02:58:54.9118704Z 289 │ const lastRequest = workspaceRefreshKeyRef.current;
2026-10-24T02:58:54.9118761Z 290 │ if (
2026-10-24T02:58:54.9118842Z 291 │ lastRequest?.key === key &&
2026-10-24T02:58:54.9118978Z 292 │ now - lastRequest.requestedAt < PROVIDER_WORKSPACE_SNAPSHOT_TTL_MS
2026-10-24T02:58:54.9119033Z 293 │ )
2026-10-24T02:58:54.9119095Z 294 │ return;
2026-10-24T02:58:54.9119268Z 295 │ if (hasCurrentProviderWorkspaceSnapshot(selectedProviderStatus, projectCwd, now)) {
2026-10-24T02:58:54.9119353Z 296 │ setWorkspaceRefreshRetry(null);
2026-10-24T02:58:54.9119448Z · ────────────┬───────────
2026-10-24T02:58:54.9119620Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9119680Z 297 │ return;
2026-10-24T02:58:54.9119729Z ╰────
2026-10-24T02:58:54.9120363Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9120679Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9120682Z
2026-10-24T02:58:54.9120877Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9121035Z ╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:326:5]
2026-10-24T02:58:54.9121088Z 325 │ }, [
2026-10-24T02:58:54.9121151Z 326 │ draftMessage,
2026-10-24T02:58:54.9121226Z · ──────┬─────
2026-10-24T02:58:54.9121372Z · ╰── Unnecessary dependency `draftMessage`
2026-10-24T02:58:54.9121436Z 327 │ environmentId,
2026-10-24T02:58:54.9121488Z ╰────
2026-10-24T02:58:54.9121776Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9122078Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9122080Z
2026-10-24T02:58:54.9122263Z ⚠ react(capitalized-calls): Capitalized function called without JSX
2026-10-24T02:58:54.9122413Z ╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:602:27]
2026-10-24T02:58:54.9122577Z 601 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
2026-10-24T02:58:54.9122702Z 602 │ const gesture = Gesture.Pan()
2026-10-24T02:58:54.9122821Z · ─┬─
2026-10-24T02:58:54.9122958Z · ╰── `Pan` may be a component
2026-10-24T02:58:54.9123032Z 603 │ .enabled(!props.disabled)
2026-10-24T02:58:54.9123082Z ╰────
2026-10-24T02:58:54.9123349Z help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
2026-10-24T02:58:54.9123782Z note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
2026-10-24T02:58:54.9123785Z
2026-10-24T02:58:54.9124039Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9124197Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
2026-10-24T02:58:54.9124259Z 259 │ .join("|");
2026-10-24T02:58:54.9124322Z 260 │ useEffect(() => {
2026-10-24T02:58:54.9124392Z · ────┬────
2026-10-24T02:58:54.9124519Z · ╰── This is the containing effect
2026-10-24T02:58:54.9124580Z 261 │ stop();
2026-10-24T02:58:54.9124646Z · ──┬─
2026-10-24T02:58:54.9124807Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9124872Z 262 │ }, [orderVersion]);
2026-10-24T02:58:54.9124923Z ╰────
2026-10-24T02:58:54.9125508Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9125823Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9125825Z
2026-10-24T02:58:54.9126036Z ⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
2026-10-24T02:58:54.9126190Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
2026-10-24T02:58:54.9126254Z 260 │ useEffect(() => {
2026-10-24T02:58:54.9126311Z 261 │ stop();
2026-10-24T02:58:54.9126379Z · ──┬─
2026-10-24T02:58:54.9126505Z · ╰── Missing dependency `stop`
2026-10-24T02:58:54.9126572Z 262 │ }, [orderVersion]);
2026-10-24T02:58:54.9126647Z · ──────┬─────
2026-10-24T02:58:54.9126791Z · ╰── Unnecessary dependency `orderVersion`
2026-10-24T02:58:54.9126855Z 263 │ useEffect(
2026-10-24T02:58:54.9126906Z ╰────
2026-10-24T02:58:54.9127314Z help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9127618Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9127620Z
2026-10-24T02:58:54.9127809Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9127992Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:96:9]
2026-10-24T02:58:54.9128068Z 95 │ const latest = useRef(props);
2026-10-24T02:58:54.9128134Z 96 │ latest.current = props;
2026-10-24T02:58:54.9128238Z · ───┬──────┬───
2026-10-24T02:58:54.9128412Z · │ ╰── Cannot update ref value during render
2026-10-24T02:58:54.9128524Z · ╰── This value is a ref
2026-10-24T02:58:54.9128590Z 97 │ const gesture = useMemo(
2026-10-24T02:58:54.9128641Z ╰────
2026-10-24T02:58:54.9129108Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9129393Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9129395Z
2026-10-24T02:58:54.9129533Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9129690Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:104:18]
2026-10-24T02:58:54.9129755Z 103 │ .runOnJS(true)
2026-10-24T02:58:54.9129875Z 104 │ .onStart(() => latest.current.onStart())
2026-10-24T02:58:54.9129990Z · ───────────────┬──────────────
2026-10-24T02:58:54.9130191Z · ╰── Passing a ref to a function may read its value during render
2026-10-24T02:58:54.9130325Z 105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9130376Z ╰────
2026-10-24T02:58:54.9130829Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9131111Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9131113Z
2026-10-24T02:58:54.9131253Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9131407Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:105:19]
2026-10-24T02:58:54.9131548Z 104 │ .onStart(() => latest.current.onStart())
2026-10-24T02:58:54.9131702Z 105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9131838Z · ──────────────────────────┬─────────────────────────
2026-10-24T02:58:54.9132040Z · ╰── Passing a ref to a function may read its value during render
2026-10-24T02:58:54.9132162Z 106 │ .onEnd((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9132213Z ╰────
2026-10-24T02:58:54.9132660Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9132948Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9132954Z
2026-10-24T02:58:54.9133092Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9133247Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:106:16]
2026-10-24T02:58:54.9133373Z 105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9133492Z 106 │ .onEnd((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9133629Z · ──────────────────────────┬─────────────────────────
2026-10-24T02:58:54.9133828Z · ╰── Passing a ref to a function may read its value during render
2026-10-24T02:58:54.9133956Z 107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
2026-10-24T02:58:54.9134009Z ╰────
2026-10-24T02:58:54.9134459Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9134745Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9134747Z
2026-10-24T02:58:54.9134885Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9135040Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:107:21]
2026-10-24T02:58:54.9135157Z 106 │ .onEnd((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9135281Z 107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
2026-10-24T02:58:54.9135416Z · ───────────────────────┬──────────────────────
2026-10-24T02:58:54.9135616Z · ╰── Passing a ref to a function may read its value during render
2026-10-24T02:58:54.9135682Z 108 │ [props.disabled],
2026-10-24T02:58:54.9135733Z ╰────
2026-10-24T02:58:54.9136183Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9136513Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9136545Z
2026-10-24T02:58:54.9136682Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9136835Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:249:9]
2026-10-24T02:58:54.9136946Z 248 │ const latest = useRef({ rows, planners, moveThread });
2026-10-24T02:58:54.9137049Z 249 │ latest.current = { rows, planners, moveThread };
2026-10-24T02:58:54.9137151Z · ───┬──────┬───
2026-10-24T02:58:54.9137325Z · │ ╰── Cannot update ref value during render
2026-10-24T02:58:54.9137437Z · ╰── This value is a ref
2026-10-24T02:58:54.9137490Z 250 │
2026-10-24T02:58:54.9137541Z ╰────
2026-10-24T02:58:54.9137992Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9138276Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9138278Z
2026-10-24T02:58:54.9138417Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9138573Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:247:22]
2026-10-24T02:58:54.9138690Z 246 │ const [preview, setPreview] = useState<Drag | null>(null);
2026-10-24T02:58:54.9138800Z 247 │ const translateY = useRef(new Animated.Value(0)).current;
2026-10-24T02:58:54.9138924Z · ──────────────────┬──────────────────
2026-10-24T02:58:54.9139089Z · ╰── Cannot access ref value during render
2026-10-24T02:58:54.9139198Z 248 │ const latest = useRef({ rows, planners, moveThread });
2026-10-24T02:58:54.9139247Z ╰────
2026-10-24T02:58:54.9139797Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9140117Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9140120Z
2026-10-24T02:58:54.9140283Z ⚠ react(purity): Cannot call impure function during render
2026-10-24T02:58:54.9140442Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:324:16]
2026-10-24T02:58:54.9140506Z 323 │ update(0);
2026-10-24T02:58:54.9140584Z 324 │ let last = performance.now();
2026-10-24T02:58:54.9140679Z · ────────┬────────
2026-10-24T02:58:54.9140814Z · ╰── Cannot call impure function
2026-10-24T02:58:54.9140882Z 325 │ const tick = () => {
2026-10-24T02:58:54.9140932Z ╰────
2026-10-24T02:58:54.9141224Z help: `performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
2026-10-24T02:58:54.9141512Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
2026-10-24T02:58:54.9141597Z
2026-10-24T02:58:54.9141814Z ⚠ react(capitalized-calls): Capitalized function called without JSX
2026-10-24T02:58:54.9141970Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:99:15]
2026-10-24T02:58:54.9142028Z 98 │ () =>
2026-10-24T02:58:54.9142093Z 99 │ Gesture.Pan()
2026-10-24T02:58:54.9142166Z · ─┬─
2026-10-24T02:58:54.9142294Z · ╰── `Pan` may be a component
2026-10-24T02:58:54.9142372Z 100 │ .enabled(!props.disabled)
2026-10-24T02:58:54.9142423Z ╰────
2026-10-24T02:58:54.9142687Z help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
2026-10-24T02:58:54.9143124Z note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
2026-10-24T02:58:54.9143130Z
2026-10-24T02:58:54.9143312Z ⚠ react(memo-dependencies): Found missing memoization dependencies
2026-10-24T02:58:54.9143466Z ╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:108:5]
2026-10-24T02:58:54.9143532Z 103 │ .runOnJS(true)
2026-10-24T02:58:54.9143626Z 104 │ .onStart(() => latest.current.onStart())
2026-10-24T02:58:54.9143713Z · ───┬──
2026-10-24T02:58:54.9144139Z · ╰── Missing dependency `latest`. Refs, setState functions, and other "stable" values generally do not need to be added as dependencies, but this variable may change over time to point to different values
2026-10-24T02:58:54.9144270Z 105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9144389Z 106 │ .onEnd((event) => latest.current.onMove(event.translationY))
2026-10-24T02:58:54.9144510Z 107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
2026-10-24T02:58:54.9144577Z 108 │ [props.disabled],
2026-10-24T02:58:54.9144656Z · ────────┬───────
2026-10-24T02:58:54.9144837Z · ╰── This dependency list is missing values used by the callback
2026-10-24T02:58:54.9144892Z 109 │ );
2026-10-24T02:58:54.9144942Z ╰────
2026-10-24T02:58:54.9145145Z help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI
2026-10-24T02:58:54.9145456Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9145463Z
2026-10-24T02:58:54.9145714Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9145848Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2139:5]
2026-10-24T02:58:54.9145905Z 2137 │ );
2026-10-24T02:58:54.9145971Z 2138 │ useEffect(() => {
2026-10-24T02:58:54.9146042Z · ────┬────
2026-10-24T02:58:54.9146171Z · ╰── This is the containing effect
2026-10-24T02:58:54.9146246Z 2139 │ setExpandedVideo(null);
2026-10-24T02:58:54.9146325Z · ────────┬───────
2026-10-24T02:58:54.9146545Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9146648Z 2140 │ setExpandedFile(null);
2026-10-24T02:58:54.9146699Z ╰────
2026-10-24T02:58:54.9147285Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9147601Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9147603Z
2026-10-24T02:58:54.9147826Z ⚠ eslint(no-unused-vars): Identifier 'isMarkdownFileLinkLabel' is imported but never used.
2026-10-24T02:58:54.9147963Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:66:10]
2026-10-24T02:58:54.9148102Z 65 │ import { resolveAssetUrl } from "@t3tools/client-runtime/state/assets";
2026-10-24T02:58:54.9148240Z 66 │ import { isMarkdownFileLinkLabel } from "@t3tools/shared/markdownLinks";
2026-10-24T02:58:54.9148333Z · ───────────┬───────────
2026-10-24T02:58:54.9148496Z · ╰── 'isMarkdownFileLinkLabel' is imported here
2026-10-24T02:58:54.9148650Z 67 │ import { formatAttachmentSize } from "@t3tools/client-runtime/state/attachments";
2026-10-24T02:58:54.9148702Z ╰────
2026-10-24T02:58:54.9148797Z help: Consider removing this import.
2026-10-24T02:58:54.9148800Z
2026-10-24T02:58:54.9149103Z ⚠ eslint(no-unused-vars): Identifier 'createContext' is imported but never used.
2026-10-24T02:58:54.9149236Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:92:3]
2026-10-24T02:58:54.9149295Z 91 │ import {
2026-10-24T02:58:54.9149356Z 92 │ createContext,
2026-10-24T02:58:54.9149431Z · ──────┬──────
2026-10-24T02:58:54.9149563Z · ╰── 'createContext' is imported here
2026-10-24T02:58:54.9149619Z 93 │ memo,
2026-10-24T02:58:54.9149667Z ╰────
2026-10-24T02:58:54.9149763Z help: Consider removing this import.
2026-10-24T02:58:54.9149765Z
2026-10-24T02:58:54.9150144Z ⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
2026-10-24T02:58:54.9150277Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:108:3]
2026-10-24T02:58:54.9150333Z 107 │ import {
2026-10-24T02:58:54.9150401Z 108 │ ActivityIndicator,
2026-10-24T02:58:54.9150530Z · ────────┬────────
2026-10-24T02:58:54.9150699Z · ╰── 'ActivityIndicator' is imported here
2026-10-24T02:58:54.9150754Z 109 │ Image,
2026-10-24T02:58:54.9150804Z ╰────
2026-10-24T02:58:54.9150897Z help: Consider removing this import.
2026-10-24T02:58:54.9150900Z
2026-10-24T02:58:54.9151095Z ⚠ eslint(no-unused-vars): Identifier 'ScrollView' is imported but never used.
2026-10-24T02:58:54.9151223Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:115:3]
2026-10-24T02:58:54.9151286Z 114 │ Pressable,
2026-10-24T02:58:54.9151348Z 115 │ ScrollView,
2026-10-24T02:58:54.9151421Z · ─────┬────
2026-10-24T02:58:54.9151548Z · ╰── 'ScrollView' is imported here
2026-10-24T02:58:54.9151609Z 116 │ StyleSheet,
2026-10-24T02:58:54.9151664Z ╰────
2026-10-24T02:58:54.9151760Z help: Consider removing this import.
2026-10-24T02:58:54.9151762Z
2026-10-24T02:58:54.9151953Z ⚠ eslint(no-unused-vars): Identifier 'NativeText' is imported but never used.
2026-10-24T02:58:54.9152083Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:117:11]
2026-10-24T02:58:54.9152142Z 116 │ StyleSheet,
2026-10-24T02:58:54.9152208Z 117 │ Text as NativeText,
2026-10-24T02:58:54.9152284Z · ─────┬────
2026-10-24T02:58:54.9152417Z · ╰── 'NativeText' is imported here
2026-10-24T02:58:54.9152481Z 118 │ type ColorValue,
2026-10-24T02:58:54.9152531Z ╰────
2026-10-24T02:58:54.9152622Z help: Consider removing this import.
2026-10-24T02:58:54.9152624Z
2026-10-24T02:58:54.9152837Z ⚠ eslint(no-unused-vars): Identifier 'tryOpenExternalUrl' is imported but never used.
2026-10-24T02:58:54.9152968Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:140:10]
2026-10-24T02:58:54.9153101Z 139 │ import { copyTextWithHaptic } from "../../lib/copyTextWithHaptic";
2026-10-24T02:58:54.9153223Z 140 │ import { tryOpenExternalUrl } from "../../lib/openExternalUrl";
2026-10-24T02:58:54.9153310Z · ─────────┬────────
2026-10-24T02:58:54.9153459Z · ╰── 'tryOpenExternalUrl' is imported here
2026-10-24T02:58:54.9153603Z 141 │ import { downloadAndShareAttachment } from "../../lib/attachmentDownload";
2026-10-24T02:58:54.9153652Z ╰────
2026-10-24T02:58:54.9153746Z help: Consider removing this import.
2026-10-24T02:58:54.9153748Z
2026-10-24T02:58:54.9153965Z ⚠ eslint(no-unused-vars): Identifier 'faviconUrlForOrigin' is imported but never used.
2026-10-24T02:58:54.9154100Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:143:10]
2026-10-24T02:58:54.9154231Z 142 │ import { hasWideMarkdownBlock } from "../../lib/wideMarkdownBlocks";
2026-10-24T02:58:54.9154353Z 143 │ import { faviconUrlForOrigin } from "@t3tools/shared/favicon";
2026-10-24T02:58:54.9154441Z · ─────────┬─────────
2026-10-24T02:58:54.9154591Z · ╰── 'faviconUrlForOrigin' is imported here
2026-10-24T02:58:54.9154647Z 144 │ import {
2026-10-24T02:58:54.9154700Z ╰────
2026-10-24T02:58:54.9154794Z help: Consider removing this import.
2026-10-24T02:58:54.9154796Z
2026-10-24T02:58:54.9155055Z ⚠ eslint(no-unused-vars): Identifier 'MediaVideoPlayer' is imported but never used.
2026-10-24T02:58:54.9155211Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:157:10]
2026-10-24T02:58:54.9155354Z 156 │ import { VideoAttachmentTile } from "../../components/VideoAttachmentTile";
2026-10-24T02:58:54.9155487Z 157 │ import { MediaVideoPlayer } from "../../components/MediaVideoPlayer";
2026-10-24T02:58:54.9155574Z · ────────┬───────
2026-10-24T02:58:54.9155720Z · ╰── 'MediaVideoPlayer' is imported here
2026-10-24T02:58:54.9155855Z 158 │ import { resolveMarkdownMediaPreview } from "../../lib/markdownMedia";
2026-10-24T02:58:54.9155907Z ╰────
2026-10-24T02:58:54.9156000Z help: Consider removing this import.
2026-10-24T02:58:54.9156002Z
2026-10-24T02:58:54.9156220Z ⚠ eslint(no-unused-vars): Identifier 'mediaVideoPreviewUri' is imported but never used.
2026-10-24T02:58:54.9156348Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:161:3]
2026-10-24T02:58:54.9156429Z 160 │ attachmentVideoPreviewSource,
2026-10-24T02:58:54.9156499Z 161 │ mediaVideoPreviewUri,
2026-10-24T02:58:54.9156581Z · ──────────┬─────────
2026-10-24T02:58:54.9156727Z · ╰── 'mediaVideoPreviewUri' is imported here
2026-10-24T02:58:54.9156798Z 162 │ mediaVideoThumbnailKey,
2026-10-24T02:58:54.9156849Z ╰────
2026-10-24T02:58:54.9156943Z help: Consider removing this import.
2026-10-24T02:58:54.9156945Z
2026-10-24T02:58:54.9157161Z ⚠ eslint(no-unused-vars): Identifier 'mediaVideoThumbnailKey' is imported but never used.
2026-10-24T02:58:54.9157290Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:162:3]
2026-10-24T02:58:54.9157363Z 161 │ mediaVideoPreviewUri,
2026-10-24T02:58:54.9157436Z 162 │ mediaVideoThumbnailKey,
2026-10-24T02:58:54.9157520Z · ───────────┬──────────
2026-10-24T02:58:54.9157672Z · ╰── 'mediaVideoThumbnailKey' is imported here
2026-10-24T02:58:54.9157750Z 163 │ type MediaVideoPreviewSource,
2026-10-24T02:58:54.9157801Z ╰────
2026-10-24T02:58:54.9157892Z help: Consider removing this import.
2026-10-24T02:58:54.9157894Z
2026-10-24T02:58:54.9158103Z ⚠ eslint(no-unused-vars): Type 'MediaVideoPreviewSource' is imported but never used.
2026-10-24T02:58:54.9158231Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:163:8]
2026-10-24T02:58:54.9158301Z 162 │ mediaVideoThumbnailKey,
2026-10-24T02:58:54.9158379Z 163 │ type MediaVideoPreviewSource,
2026-10-24T02:58:54.9158478Z · ───────────┬───────────
2026-10-24T02:58:54.9158639Z · ╰── 'MediaVideoPreviewSource' is imported here
2026-10-24T02:58:54.9158725Z 164 │ } from "../../lib/videoPreviewSource";
2026-10-24T02:58:54.9158773Z ╰────
2026-10-24T02:58:54.9158866Z help: Consider removing this import.
2026-10-24T02:58:54.9158868Z
2026-10-24T02:58:54.9159062Z ⚠ eslint(no-unused-vars): Type 'ReviewDiffTheme' is imported but never used.
2026-10-24T02:58:54.9159191Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:171:15]
2026-10-24T02:58:54.9159360Z 170 │ import { parseReviewCommentMessageSegments } from "../review/reviewCommentSelection";
2026-10-24T02:58:54.9159499Z 171 │ import type { ReviewDiffTheme } from "../review/shikiReviewHighlighter";
2026-10-24T02:58:54.9159639Z · ───────┬───────
2026-10-24T02:58:54.9159811Z · ╰── 'ReviewDiffTheme' is imported here
2026-10-24T02:58:54.9159902Z 172 │ import {
2026-10-24T02:58:54.9159958Z ╰────
2026-10-24T02:58:54.9160050Z help: Consider removing this import.
2026-10-24T02:58:54.9160052Z
2026-10-24T02:58:54.9160273Z ⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownFontSizes' is imported but never used.
2026-10-24T02:58:54.9160401Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:186:3]
2026-10-24T02:58:54.9160457Z 185 │ import {
2026-10-24T02:58:54.9160530Z 186 │ resolveMarkdownFontSizes,
2026-10-24T02:58:54.9160619Z · ────────────┬───────────
2026-10-24T02:58:54.9160778Z · ╰── 'resolveMarkdownFontSizes' is imported here
2026-10-24T02:58:54.9160864Z 187 │ resolveNativeMarkdownTypography,
2026-10-24T02:58:54.9160915Z ╰────
2026-10-24T02:58:54.9161007Z help: Consider removing this import.
2026-10-24T02:58:54.9161009Z
2026-10-24T02:58:54.9161222Z ⚠ eslint(no-unused-vars): Identifier 'markdownLinkIconSource' is imported but never used.
2026-10-24T02:58:54.9161350Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:191:10]
2026-10-24T02:58:54.9161480Z 190 │ import { PierreEntryIcon } from "../../components/PierreEntryIcon";
2026-10-24T02:58:54.9161615Z 191 │ import { markdownLinkIconSource } from "../../lib/markdownLinkIcons";
2026-10-24T02:58:54.9161707Z · ───────────┬──────────
2026-10-24T02:58:54.9161863Z · ╰── 'markdownLinkIconSource' is imported here
2026-10-24T02:58:54.9161926Z 192 │ import {
2026-10-24T02:58:54.9161979Z ╰────
2026-10-24T02:58:54.9162071Z help: Consider removing this import.
2026-10-24T02:58:54.9162074Z
2026-10-24T02:58:54.9162322Z ⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownInlineCodePresentation' is imported but never used.
2026-10-24T02:58:54.9162449Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:194:3]
2026-10-24T02:58:54.9162526Z 193 │ normalizeNativeMarkdownUrl,
2026-10-24T02:58:54.9162619Z 194 │ resolveMarkdownInlineCodePresentation,
2026-10-24T02:58:54.9162725Z · ──────────────────┬──────────────────
2026-10-24T02:58:54.9162916Z · ╰── 'resolveMarkdownInlineCodePresentation' is imported here
2026-10-24T02:58:54.9162988Z 195 │ resolveMarkdownLinkIcon,
2026-10-24T02:58:54.9163045Z ╰────
2026-10-24T02:58:54.9163138Z help: Consider removing this import.
2026-10-24T02:58:54.9163140Z
2026-10-24T02:58:54.9163358Z ⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownLinkIcon' is imported but never used.
2026-10-24T02:58:54.9163486Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:195:3]
2026-10-24T02:58:54.9163578Z 194 │ resolveMarkdownInlineCodePresentation,
2026-10-24T02:58:54.9163648Z 195 │ resolveMarkdownLinkIcon,
2026-10-24T02:58:54.9163735Z · ───────────┬───────────
2026-10-24T02:58:54.9163887Z · ╰── 'resolveMarkdownLinkIcon' is imported here
2026-10-24T02:58:54.9163971Z 196 │ resolveMarkdownLinkPresentation,
2026-10-24T02:58:54.9164021Z ╰────
2026-10-24T02:58:54.9164113Z help: Consider removing this import.
2026-10-24T02:58:54.9164166Z
2026-10-24T02:58:54.9164413Z ⚠ eslint(no-unused-vars): Identifier 'useMarkdownCodeHighlight' is imported but never used.
2026-10-24T02:58:54.9164541Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:234:10]
2026-10-24T02:58:54.9164640Z 233 │ import { ThreadMcpApp } from "./McpAppWebView";
2026-10-24T02:58:54.9164781Z 234 │ import { useMarkdownCodeHighlight } from "./markdownCodeHighlightState";
2026-10-24T02:58:54.9164878Z · ────────────┬───────────
2026-10-24T02:58:54.9165041Z · ╰── 'useMarkdownCodeHighlight' is imported here
2026-10-24T02:58:54.9165099Z 235 │ import {
2026-10-24T02:58:54.9165147Z ╰────
2026-10-24T02:58:54.9165240Z help: Consider removing this import.
2026-10-24T02:58:54.9165242Z
2026-10-24T02:58:54.9165451Z ⚠ eslint(no-unused-vars): Identifier 'useAssetUrlState' is imported but never used.
2026-10-24T02:58:54.9165580Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:238:3]
2026-10-24T02:58:54.9165642Z 237 │ useAssetUrl,
2026-10-24T02:58:54.9165709Z 238 │ useAssetUrlState,
2026-10-24T02:58:54.9165788Z · ────────┬───────
2026-10-24T02:58:54.9165927Z · ╰── 'useAssetUrlState' is imported here
2026-10-24T02:58:54.9165993Z 239 │ useRefreshAssetUrl,
2026-10-24T02:58:54.9166044Z ╰────
2026-10-24T02:58:54.9166136Z help: Consider removing this import.
2026-10-24T02:58:54.9166139Z
2026-10-24T02:58:54.9166335Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9166470Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2141:7]
2026-10-24T02:58:54.9166546Z 2140 │ setExpandedFile(null);
2026-10-24T02:58:54.9166701Z 2141 │ }, [props.environmentId, props.threadId, props.contentPresentation.kind]);
2026-10-24T02:58:54.9166915Z · ─────────┬───────── ───────┬────── ───────────────┬──────────────
2026-10-24T02:58:54.9167200Z · │ │ ╰── Unnecessary dependency `props.contentPresentation.kind`
2026-10-24T02:58:54.9167394Z · │ ╰── Unnecessary dependency `props.threadId`
2026-10-24T02:58:54.9167554Z · ╰── Unnecessary dependency `props.environmentId`
2026-10-24T02:58:54.9167743Z 2142 │ const horizontalPadding = props.layoutVariant === "split" ? 20 : 16;
2026-10-24T02:58:54.9167831Z ╰────
2026-10-24T02:58:54.9168120Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9168430Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9168432Z
2026-10-24T02:58:54.9168628Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9168761Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2609:7]
2026-10-24T02:58:54.9168854Z 2608 │ reportHeaderMaterialVisibility(false);
2026-10-24T02:58:54.9168971Z 2609 │ }, [feedThreadKey, reportHeaderMaterialVisibility]);
2026-10-24T02:58:54.9169053Z · ──────┬──────
2026-10-24T02:58:54.9169206Z · ╰── Unnecessary dependency `feedThreadKey`
2026-10-24T02:58:54.9169258Z 2610 │
2026-10-24T02:58:54.9169311Z ╰────
2026-10-24T02:58:54.9169603Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9169933Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9169936Z
2026-10-24T02:58:54.9170132Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9170270Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2625:7]
2026-10-24T02:58:54.9170330Z 2624 │ }
2026-10-24T02:58:54.9170459Z 2625 │ }, [listMountKey, props.contentInsetEndAdjustment, listRef]);
2026-10-24T02:58:54.9170536Z · ──────┬─────
2026-10-24T02:58:54.9170679Z · ╰── Unnecessary dependency `listMountKey`
2026-10-24T02:58:54.9170733Z 2626 │
2026-10-24T02:58:54.9170787Z ╰────
2026-10-24T02:58:54.9171069Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9171372Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9171374Z
2026-10-24T02:58:54.9171575Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9171709Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2782:7]
2026-10-24T02:58:54.9171766Z 2781 │ }
2026-10-24T02:58:54.9171944Z 2782 │ }, [expandedTurnIds, expandedWorkGroups, expandedWorkRows, settleDisclosureAfterLayout]);
2026-10-24T02:58:54.9172135Z · ───────┬─────── ─────────┬──────── ────────┬───────
2026-10-24T02:58:54.9172379Z · │ │ ╰── Unnecessary dependency `expandedWorkRows`
2026-10-24T02:58:54.9172576Z · │ ╰── Unnecessary dependency `expandedWorkGroups`
2026-10-24T02:58:54.9172776Z · ╰── Unnecessary dependency `expandedTurnIds`
2026-10-24T02:58:54.9172864Z 2783 │
2026-10-24T02:58:54.9172916Z ╰────
2026-10-24T02:58:54.9173201Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9173503Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9173505Z
2026-10-24T02:58:54.9173680Z ⚠ react(memo-dependencies): Found extra memoization dependencies
2026-10-24T02:58:54.9173812Z ╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:613:9]
2026-10-24T02:58:54.9173870Z 612 │ };
2026-10-24T02:58:54.9173983Z 613 │ }, [props.environmentId, attachment.id, httpBaseUrl]),
2026-10-24T02:58:54.9174169Z · ─────────┬───────── ──────┬────── ─────┬─────
2026-10-24T02:58:54.9174406Z · │ │ ╰── Unnecessary dependency `httpBaseUrl`
2026-10-24T02:58:54.9174598Z · │ ╰── Unnecessary dependency `attachment.id`
2026-10-24T02:58:54.9174759Z · ╰── Unnecessary dependency `props.environmentId`
2026-10-24T02:58:54.9174813Z 614 │ );
2026-10-24T02:58:54.9174862Z ╰────
2026-10-24T02:58:54.9175168Z help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9175478Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9175483Z
2026-10-24T02:58:54.9175662Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9175831Z ╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:555:70]
2026-10-24T02:58:54.9175913Z 554 │ assert.deepStrictEqual(
2026-10-24T02:58:54.9176075Z 555 │ (yield* Ref.get(fixture.syncCommands)).map(({ commandId: _, ...rest }) => rest),
2026-10-24T02:58:54.9176194Z · ┬
2026-10-24T02:58:54.9176352Z · ╰── '_' is declared here
2026-10-24T02:58:54.9176418Z 556 │ [
2026-10-24T02:58:54.9176472Z ╰────
2026-10-24T02:58:54.9176575Z help: Consider removing this parameter.
2026-10-24T02:58:54.9176577Z
2026-10-24T02:58:54.9176754Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9176924Z ╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:1155:70]
2026-10-24T02:58:54.9177006Z 1154 │ assert.deepStrictEqual(
2026-10-24T02:58:54.9177165Z 1155 │ (yield* Ref.get(fixture.linkCommands)).map(({ commandId: _, ...rest }) => rest),
2026-10-24T02:58:54.9177284Z · ┬
2026-10-24T02:58:54.9177495Z · ╰── '_' is declared here
2026-10-24T02:58:54.9177586Z 1156 │ [
2026-10-24T02:58:54.9177638Z ╰────
2026-10-24T02:58:54.9177738Z help: Consider removing this parameter.
2026-10-24T02:58:54.9177741Z
2026-10-24T02:58:54.9178191Z ⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
2026-10-24T02:58:54.9178311Z ╭─[packages/effect-acp/src/errors.test.ts:129:28]
2026-10-24T02:58:54.9178403Z 128 │ const secret = "acp-summary-secret";
2026-10-24T02:58:54.9178511Z 129 │ const cause = yield* Schema.decodeUnknownEffect(
2026-10-24T02:58:54.9178627Z · ──────────────────────────
2026-10-24T02:58:54.9178694Z 130 │ Schema.Struct({
2026-10-24T02:58:54.9178749Z ╰────
2026-10-24T02:58:54.9178754Z
2026-10-24T02:58:54.9179080Z ⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
2026-10-24T02:58:54.9179196Z ╭─[packages/effect-acp/src/schema.test.ts:18:12]
2026-10-24T02:58:54.9179351Z 17 │ const command = { name: "plan", description: "Make a plan", input: { hint: "Task" } };
2026-10-24T02:58:54.9179489Z 18 │ expect(Schema.is(V1.AvailableCommand)(command)).toBe(true);
2026-10-24T02:58:54.9179626Z · ─────────
2026-10-24T02:58:54.9179687Z 19 │ expect(
2026-10-24T02:58:54.9179737Z ╰────
2026-10-24T02:58:54.9179740Z
2026-10-24T02:58:54.9180108Z ⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
2026-10-24T02:58:54.9180227Z ╭─[packages/effect-acp/src/schema.test.ts:20:7]
2026-10-24T02:58:54.9180286Z 19 │ expect(
2026-10-24T02:58:54.9180450Z 20 │ Schema.is(V2.AvailableCommand)({ ...command, input: { type: "text", hint: "Task" } }),
2026-10-24T02:58:54.9180524Z · ─────────
2026-10-24T02:58:54.9180587Z 21 │ ).toBe(true);
2026-10-24T02:58:54.9180637Z ╰────
2026-10-24T02:58:54.9180640Z
2026-10-24T02:58:54.9180848Z ⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
2026-10-24T02:58:54.9180990Z ╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:773:7]
2026-10-24T02:58:54.9181090Z 772 │ if (settingsSheetPresentation.isActive) {
2026-10-24T02:58:54.9181221Z 773 │ settingsRoutePresentation.present(settingsRouteSession);
2026-10-24T02:58:54.9181314Z · ────────────┬────────────
2026-10-24T02:58:54.9181483Z · ╰── Missing dependency `settingsRoutePresentation`
2026-10-24T02:58:54.9181538Z 774 │ }
2026-10-24T02:58:54.9181736Z 775 │ }, [settingsRoutePresentation.present, settingsRouteSession, settingsSheetPresentation.isActive]);
2026-10-24T02:58:54.9181840Z · ────────────────┬────────────────
2026-10-24T02:58:54.9182115Z · ╰── Overly precise dependency `settingsRoutePresentation.present`, use `settingsRoutePresentation` instead
2026-10-24T02:58:54.9182179Z 776 │
2026-10-24T02:58:54.9182270Z ╰────
2026-10-24T02:58:54.9182747Z help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9183091Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9183094Z
2026-10-24T02:58:54.9183248Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9183389Z ╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:391:5]
2026-10-24T02:58:54.9183546Z 387 │ typeof props.style.borderRadius === "number" ? props.style.borderRadius : 0;
2026-10-24T02:58:54.9183678Z 388 │ const animatedBorderRadius = useSharedValue(targetBorderRadius);
2026-10-24T02:58:54.9183767Z · ──────────┬─────────
2026-10-24T02:58:54.9183923Z · ╰── `animatedBorderRadius` originates here
2026-10-24T02:58:54.9184080Z 389 │ const shouldAnimate = props.animateLayout !== false && Platform.OS !== "android";
2026-10-24T02:58:54.9184149Z 390 │ useLayoutEffect(() => {
2026-10-24T02:58:54.9184248Z 391 │ animatedBorderRadius.value = shouldAnimate
2026-10-24T02:58:54.9184334Z · ──────────┬─────────
2026-10-24T02:58:54.9184486Z · ╰── `animatedBorderRadius` cannot be modified
2026-10-24T02:58:54.9184572Z 392 │ ? withTiming(targetBorderRadius, {
2026-10-24T02:58:54.9184623Z ╰────
2026-10-24T02:58:54.9184882Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9185187Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9185193Z
2026-10-24T02:58:54.9185556Z ⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
2026-10-24T02:58:54.9185672Z ╭─[packages/effect-acp/src/client.ts:1269:11]
2026-10-24T02:58:54.9185819Z 1268 │ extNotificationHandlers.set(CLIENT_METHODS.mcp_message, (params) =>
2026-10-24T02:58:54.9185988Z 1269 │ Schema.decodeUnknownEffect(AcpSchemaV2.MessageMcpNotification)(params).pipe(
2026-10-24T02:58:54.9186091Z · ──────────────────────────
2026-10-24T02:58:54.9186232Z 1270 │ Effect.mapError(() => AcpError.AcpRequestError.invalidParams()),
2026-10-24T02:58:54.9186284Z ╰────
2026-10-24T02:58:54.9186287Z
2026-10-24T02:58:54.9186479Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9186739Z ╭─[apps/mobile/src/components/ui/AndroidAnchoredMenu.tsx:152:27]
2026-10-24T02:58:54.9186912Z 151 │ <View ref={anchorRef} collapsable={false} className={props.className} style={props.style}>
2026-10-24T02:58:54.9186989Z 152 │ {props.children(open)}
2026-10-24T02:58:54.9187076Z · ──┬─
2026-10-24T02:58:54.9187232Z · ╰── Cannot access ref value during render
2026-10-24T02:58:54.9187291Z 153 │ </View>
2026-10-24T02:58:54.9187342Z ╰────
2026-10-24T02:58:54.9187804Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9188092Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9188095Z
2026-10-24T02:58:54.9188288Z ⚠ react(memo-dependencies): Found missing/extra memoization dependencies
2026-10-24T02:58:54.9188431Z ╭─[apps/mobile/src/components/ui/AndroidAnchoredMenu.tsx:140:9]
2026-10-24T02:58:54.9188513Z 139 │ if (action.id !== undefined) {
2026-10-24T02:58:54.9188590Z 140 │ props.onPressAction?.({
2026-10-24T02:58:54.9188661Z · ──┬──
2026-10-24T02:58:54.9188787Z · ╰── Missing dependency `props`
2026-10-24T02:58:54.9188877Z 141 │ nativeEvent: { event: action.id },
2026-10-24T02:58:54.9189025Z 142 │ } as Parameters<NonNullable<MenuComponentProps["onPressAction"]>>[0]);
2026-10-24T02:58:54.9189083Z 143 │ }
2026-10-24T02:58:54.9189137Z 144 │ },
2026-10-24T02:58:54.9189217Z 145 │ [close, props.onPressAction],
2026-10-24T02:58:54.9189309Z · ─────────┬─────────
2026-10-24T02:58:54.9189518Z · ╰── Overly precise dependency `props.onPressAction`, use `props` instead
2026-10-24T02:58:54.9189571Z 146 │ );
2026-10-24T02:58:54.9189623Z ╰────
2026-10-24T02:58:54.9190131Z help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI. Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
2026-10-24T02:58:54.9190443Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9190447Z
2026-10-24T02:58:54.9190610Z ⚠ eslint(no-control-regex): Unexpected control character
2026-10-24T02:58:54.9190796Z ╭─[apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx:220:46]
2026-10-24T02:58:54.9190932Z 219 │ <Text selectable className="font-mono text-sm text-foreground">
2026-10-24T02:58:54.9191069Z 220 │ {interaction.output.replace(/\x1b\[[0-?]*[ -/]*[@-~]/g, "")}
2026-10-24T02:58:54.9191175Z · ──┬─
2026-10-24T02:58:54.9191335Z · ╰── 'U+001B' is a control character.
2026-10-24T02:58:54.9191448Z 221 │ </Text>
2026-10-24T02:58:54.9191532Z ╰────
2026-10-24T02:58:54.9191757Z help: Avoid matching control characters in regular expressions. If intentional, disable this rule for the expression.
2026-10-24T02:58:54.9191759Z
2026-10-24T02:58:54.9191979Z ⚠ eslint(no-unused-vars): Function 'assertUserMessagesExclude' is declared but never used.
2026-10-24T02:58:54.9192139Z ╭─[apps/server/src/orchestration-v2/testkit/fixtures/shared.ts:1398:10]
2026-10-24T02:58:54.9192193Z 1397 │
2026-10-24T02:58:54.9192281Z 1398 │ function assertUserMessagesExclude(
2026-10-24T02:58:54.9192381Z · ────────────┬────────────
2026-10-24T02:58:54.9192546Z · ╰── 'assertUserMessagesExclude' is declared here
2026-10-24T02:58:54.9192661Z 1399 │ projection: OrchestrationV2ThreadProjection,
2026-10-24T02:58:54.9192715Z ╰────
2026-10-24T02:58:54.9192815Z help: Consider removing this declaration.
2026-10-24T02:58:54.9192820Z
2026-10-24T02:58:54.9193276Z ⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
2026-10-24T02:58:54.9193443Z ╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:566:7]
2026-10-24T02:58:54.9193544Z 565 │ let afterSequence = created[0]!.sequence;
2026-10-24T02:58:54.9193738Z 566 │ ╭─▶ for (let index = 1; index <= 32; index += 1) {
2026-10-24T02:58:54.9193835Z 567 │ │ const nextEvent = {
2026-10-24T02:58:54.9193997Z 568 │ │ id: EventId.make(`event:foundation-stream-race:${index}`),
2026-10-24T02:58:54.9194128Z 569 │ │ type: "thread.metadata-updated" as const,
2026-10-24T02:58:54.9194217Z 570 │ │ threadId,
2026-10-24T02:58:54.9194317Z 571 │ │ providerInstanceId,
2026-10-24T02:58:54.9194415Z 572 │ │ occurredAt: now,
2026-10-24T02:58:54.9194559Z 573 │ │ payload: { ...thread, title: `Race update ${index}` },
2026-10-24T02:58:54.9194685Z 574 │ │ } satisfies OrchestrationV2DomainEvent;
2026-10-24T02:58:54.9194796Z 575 │ │ const reader = yield* eventSink
2026-10-24T02:58:54.9194916Z 576 │ │ .stream({ threadId, afterSequence })
2026-10-24T02:58:54.9195051Z 577 │ │ .pipe(Stream.runHead, Effect.forkChild);
2026-10-24T02:58:54.9195157Z 578 │ │ yield* Effect.yieldNow;
2026-10-24T02:58:54.9195317Z 579 │ │ const written = yield* eventSink.write({ events: [nextEvent] });
2026-10-24T02:58:54.9195439Z 580 │ │ const received = yield* Fiber.join(reader);
2026-10-24T02:58:54.9195553Z 581 │ │ if (Option.isNone(received)) {
2026-10-24T02:58:54.9195749Z 582 │ │ return yield* Effect.die("The event stream ended before delivering the live event.");
2026-10-24T02:58:54.9195828Z 583 │ │ }
2026-10-24T02:58:54.9195984Z 584 │ │ assert.equal(received.value.sequence, written[0]?.sequence);
2026-10-24T02:58:54.9196176Z 585 │ │ assert.equal(received.value.event.id, nextEvent.id);
2026-10-24T02:58:54.9196329Z 586 │ │ afterSequence = received.value.sequence;
2026-10-24T02:58:54.9196456Z 587 │ ╰─▶ }
2026-10-24T02:58:54.9196514Z 588 │ }),
2026-10-24T02:58:54.9196567Z ╰────
2026-10-24T02:58:54.9196569Z
2026-10-24T02:58:54.9197021Z ⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
2026-10-24T02:58:54.9197189Z ╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:2327:9]
2026-10-24T02:58:54.9197265Z 2326 │ let settled = false;
2026-10-24T02:58:54.9197427Z 2327 │ ╭─▶ while (!settled) {
2026-10-24T02:58:54.9197585Z 2328 │ │ settled = (yield* outbox.listByCommandId(commandId)).every(
2026-10-24T02:58:54.9197716Z 2329 │ │ (effect) => effect.status === "succeeded",
2026-10-24T02:58:54.9197797Z 2330 │ │ );
2026-10-24T02:58:54.9197918Z 2331 │ │ if (!settled) yield* Effect.yieldNow;
2026-10-24T02:58:54.9198054Z 2332 │ ╰─▶ }
2026-10-24T02:58:54.9198172Z 2333 │ }).pipe(Effect.provide(layerWorker), Effect.scoped);
2026-10-24T02:58:54.9198224Z ╰────
2026-10-24T02:58:54.9198226Z
2026-10-24T02:58:54.9198683Z ⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
2026-10-24T02:58:54.9198811Z ╭─[packages/effect-acp/src/protocol.test.ts:500:31]
2026-10-24T02:58:54.9198864Z 499 │
2026-10-24T02:58:54.9198976Z 500 │ const response = yield* Schema.decodeUnknownEffect(
2026-10-24T02:58:54.9199092Z · ──────────────────────────
2026-10-24T02:58:54.9199197Z 501 │ Schema.fromJsonString(JsonRpcErrorResponse),
2026-10-24T02:58:54.9199247Z ╰────
2026-10-24T02:58:54.9199249Z
2026-10-24T02:58:54.9199538Z ⚠ eslint(no-unused-vars): Variable 'revokeActiveMcpThread' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.9199658Z ╭─[apps/server/src/mcp/McpSessionRegistry.ts:218:7]
2026-10-24T02:58:54.9199715Z 217 │
2026-10-24T02:58:54.9199876Z 218 │ const revokeActiveMcpThread = (threadId: ThreadId): Effect.Effect<void> =>
2026-10-24T02:58:54.9200016Z · ──────────┬──────────
2026-10-24T02:58:54.9200167Z · ╰── 'revokeActiveMcpThread' is declared here
2026-10-24T02:58:54.9200352Z 219 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeThread(threadId) : Effect.void;
2026-10-24T02:58:54.9200403Z ╰────
2026-10-24T02:58:54.9200504Z help: Consider removing this declaration.
2026-10-24T02:58:54.9200506Z
2026-10-24T02:58:54.9200808Z ⚠ eslint(no-unused-vars): Variable 'revokeAllActiveMcpCredentials' is declared but never used. Unused variables should start with a '_'.
2026-10-24T02:58:54.9200927Z ╭─[apps/server/src/mcp/McpSessionRegistry.ts:221:7]
2026-10-24T02:58:54.9200980Z 220 │
2026-10-24T02:58:54.9201160Z 221 │ const revokeAllActiveMcpCredentials = (): Effect.Effect<void> =>
2026-10-24T02:58:54.9201289Z · ──────────────┬──────────────
2026-10-24T02:58:54.9201462Z · ╰── 'revokeAllActiveMcpCredentials' is declared here
2026-10-24T02:58:54.9201620Z 222 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeAll : Effect.void;
2026-10-24T02:58:54.9201671Z ╰────
2026-10-24T02:58:54.9201771Z help: Consider removing this declaration.
2026-10-24T02:58:54.9201773Z
2026-10-24T02:58:54.9201950Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9202084Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:121:27]
2026-10-24T02:58:54.9202250Z 120 │ const scope = makeScope(options.capabilities ?? new Set(["preview", "worktree"]));
2026-10-24T02:58:54.9202340Z 121 │ const dispatch = vi.fn((_: unknown) =>
2026-10-24T02:58:54.9202420Z · ┬
2026-10-24T02:58:54.9202547Z · ╰── '_' is declared here
2026-10-24T02:58:54.9202647Z 122 │ (options.dispatchGate ?? Effect.void).pipe(
2026-10-24T02:58:54.9202698Z ╰────
2026-10-24T02:58:54.9202796Z help: Consider removing this parameter.
2026-10-24T02:58:54.9202798Z
2026-10-24T02:58:54.9202976Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9203109Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:134:39]
2026-10-24T02:58:54.9203165Z 133 │ );
2026-10-24T02:58:54.9203267Z 134 │ const listLocalBranchNames = vi.fn((_: string) =>
2026-10-24T02:58:54.9203368Z · ┬
2026-10-24T02:58:54.9203505Z · ╰── '_' is declared here
2026-10-24T02:58:54.9203571Z 135 │ Effect.succeed(
2026-10-24T02:58:54.9203620Z ╰────
2026-10-24T02:58:54.9203720Z help: Consider removing this parameter.
2026-10-24T02:58:54.9203723Z
2026-10-24T02:58:54.9203899Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9204030Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:178:31]
2026-10-24T02:58:54.9204083Z 177 │ });
2026-10-24T02:58:54.9204181Z 178 │ const sendToThread = vi.fn((_: unknown) => {
2026-10-24T02:58:54.9204267Z · ┬
2026-10-24T02:58:54.9204402Z · ╰── '_' is declared here
2026-10-24T02:58:54.9204500Z 179 │ switch (options.continuation ?? "queued") {
2026-10-24T02:58:54.9204551Z ╰────
2026-10-24T02:58:54.9204646Z help: Consider removing this parameter.
2026-10-24T02:58:54.9204649Z
2026-10-24T02:58:54.9204824Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9204953Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:203:33]
2026-10-24T02:58:54.9205007Z 202 │ );
2026-10-24T02:58:54.9205104Z 203 │ const removeWorktree = vi.fn((_: unknown) =>
2026-10-24T02:58:54.9205192Z · ┬
2026-10-24T02:58:54.9205322Z · ╰── '_' is declared here
2026-10-24T02:58:54.9205404Z 204 │ options.removeWorktreeFails
2026-10-24T02:58:54.9205512Z ╰────
2026-10-24T02:58:54.9205639Z help: Consider removing this parameter.
2026-10-24T02:58:54.9205641Z
2026-10-24T02:58:54.9205813Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9205945Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:208:36]
2026-10-24T02:58:54.9206000Z 207 │ );
2026-10-24T02:58:54.9206100Z 208 │ const deleteLocalBranch = vi.fn((_: unknown) =>
2026-10-24T02:58:54.9206190Z · ┬
2026-10-24T02:58:54.9206324Z · ╰── '_' is declared here
2026-10-24T02:58:54.9206410Z 209 │ options.deleteLocalBranchFails
2026-10-24T02:58:54.9206463Z ╰────
2026-10-24T02:58:54.9206558Z help: Consider removing this parameter.
2026-10-24T02:58:54.9206562Z
2026-10-24T02:58:54.9206741Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9206874Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:213:42]
2026-10-24T02:58:54.9206926Z 212 │ );
2026-10-24T02:58:54.9207038Z 213 │ const fetchWorktreeBaseCommit = vi.fn((_: unknown) =>
2026-10-24T02:58:54.9207133Z · ┬
2026-10-24T02:58:54.9207271Z · ╰── '_' is declared here
2026-10-24T02:58:54.9207357Z 214 │ options.fetchWorktreeBaseFails
2026-10-24T02:58:54.9207408Z ╰────
2026-10-24T02:58:54.9207502Z help: Consider removing this parameter.
2026-10-24T02:58:54.9207505Z
2026-10-24T02:58:54.9207684Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9207818Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:254:30]
2026-10-24T02:58:54.9207873Z 253 │ );
2026-10-24T02:58:54.9207960Z 254 │ const localStatus = vi.fn((_: unknown) =>
2026-10-24T02:58:54.9208046Z · ┬
2026-10-24T02:58:54.9208175Z · ╰── '_' is declared here
2026-10-24T02:58:54.9208243Z 255 │ Effect.succeed({
2026-10-24T02:58:54.9208293Z ╰────
2026-10-24T02:58:54.9208391Z help: Consider removing this parameter.
2026-10-24T02:58:54.9208393Z
2026-10-24T02:58:54.9208567Z ⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
2026-10-24T02:58:54.9208699Z ╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:264:32]
2026-10-24T02:58:54.9208802Z 263 │ );
2026-10-24T02:58:54.9208980Z 264 │ const refreshStatus = vi.fn((_: string) => Effect.die("refreshStatus stub"));
2026-10-24T02:58:54.9209067Z · ┬
2026-10-24T02:58:54.9209199Z · ╰── '_' is declared here
2026-10-24T02:58:54.9209341Z 265 │ const runForThread = vi.fn((input: { readonly worktreePath: string }) => {
2026-10-24T02:58:54.9209390Z ╰────
2026-10-24T02:58:54.9209487Z help: Consider removing this parameter.
2026-10-24T02:58:54.9209490Z
2026-10-24T02:58:54.9209641Z ⚠ eslint(no-new): Do not use 'new' for side effects.
2026-10-24T02:58:54.9209761Z ╭─[apps/server/src/mcp/McpToolAccess.test.ts:168:3]
2026-10-24T02:58:54.9209881Z 167 │ // @ts-expect-error a declaration constructed directly
2026-10-24T02:58:54.9210003Z 168 │ new McpToolAccess.Declaration(unchecked);
2026-10-24T02:58:54.9210105Z · ─────────────────────────────
2026-10-24T02:58:54.9210229Z 169 │ // @ts-expect-error a handlers layer built outside McpToolAccess
2026-10-24T02:58:54.9210280Z ╰────
2026-10-24T02:58:54.9210437Z help: Assign the result of 'new' to a variable or compare it to a reference.
2026-10-24T02:58:54.9210440Z
2026-10-24T02:58:54.9210895Z ⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
2026-10-24T02:58:54.9211040Z ╭─[apps/server/src/background/HostPowerMonitor.test.ts:133:11]
2026-10-24T02:58:54.9211164Z 132 │ const monitor = yield* HostPowerMonitor.HostPowerMonitor;
2026-10-24T02:58:54.9211311Z 133 │ ╭─▶ for (
2026-10-24T02:58:54.9211413Z 134 │ │ let attempt = 0;
2026-10-24T02:58:54.9211580Z 135 │ │ attempt < 100 && (yield* monitor.snapshot).onBattery !== "true";
2026-10-24T02:58:54.9211674Z 136 │ │ attempt += 1
2026-10-24T02:58:54.9211756Z 137 │ │ ) {
2026-10-24T02:58:54.9211868Z 138 │ │ yield* Effect.yieldNow;
2026-10-24T02:58:54.9211999Z 139 │ ╰─▶ }
2026-10-24T02:58:54.9212119Z 140 │ expect((yield* monitor.snapshot).onBattery).toBe("true");
2026-10-24T02:58:54.9212171Z ╰────
2026-10-24T02:58:54.9212173Z
2026-10-24T02:58:54.9212335Z ⚠ react(immutability): This value cannot be modified
2026-10-24T02:58:54.9212492Z ╭─[apps/mobile/src/features/connection/ConnectionStatusDot.tsx:58:7]
2026-10-24T02:58:54.9212584Z 53 │ function usePulseAnimation(pulse: boolean) {
2026-10-24T02:58:54.9212675Z 54 │ const pulseProgress = useSharedValue(0);
2026-10-24T02:58:54.9212754Z · ──────┬──────
2026-10-24T02:58:54.9212892Z · ╰── `pulseProgress` originates here
2026-10-24T02:58:54.9212942Z 55 │
2026-10-24T02:58:54.9213008Z 56 │ useEffect(() => {
2026-10-24T02:58:54.9213070Z 57 │ if (pulse) {
2026-10-24T02:58:54.9213155Z 58 │ pulseProgress.value = withRepeat(
2026-10-24T02:58:54.9213230Z · ──────┬──────
2026-10-24T02:58:54.9213420Z · ╰── `pulseProgress` cannot be modified
2026-10-24T02:58:54.9213519Z 59 │ withTiming(1, {
2026-10-24T02:58:54.9213569Z ╰────
2026-10-24T02:58:54.9213828Z help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
2026-10-24T02:58:54.9214133Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
2026-10-24T02:58:54.9214135Z
2026-10-24T02:58:54.9214388Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9214521Z ╭─[apps/mobile/src/components/VideoPreviewModal.tsx:68:5]
2026-10-24T02:58:54.9214620Z 66 │ const { id: attachmentId, fileUri } = attachment;
2026-10-24T02:58:54.9214684Z 67 │ useEffect(() => {
2026-10-24T02:58:54.9214758Z · ────┬────
2026-10-24T02:58:54.9214885Z · ╰── This is the containing effect
2026-10-24T02:58:54.9214947Z 68 │ setUri(null);
2026-10-24T02:58:54.9215015Z · ───┬──
2026-10-24T02:58:54.9215177Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9215240Z 69 │ setError(null);
2026-10-24T02:58:54.9215290Z ╰────
2026-10-24T02:58:54.9215870Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9216194Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9216199Z
2026-10-24T02:58:54.9216395Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9216528Z ╭─[apps/mobile/src/components/VideoPreviewModal.tsx:91:7]
2026-10-24T02:58:54.9216581Z 90 │ };
2026-10-24T02:58:54.9216658Z 91 │ }, [attachmentId, fileUri]);
2026-10-24T02:58:54.9216775Z · ──────┬───── ───┬───
2026-10-24T02:58:54.9216953Z · │ ╰── Unnecessary dependency `fileUri`
2026-10-24T02:58:54.9217096Z · ╰── Unnecessary dependency `attachmentId`
2026-10-24T02:58:54.9217235Z 92 │ const mimeType = videoMimeType(attachment) ?? attachment.mimeType;
2026-10-24T02:58:54.9217289Z ╰────
2026-10-24T02:58:54.9217575Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9217879Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9217881Z
2026-10-24T02:58:54.9218090Z ⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
2026-10-24T02:58:54.9218226Z ╭─[apps/mobile/src/components/VideoPreviewModal.tsx:213:34]
2026-10-24T02:58:54.9218294Z 212 │ useEffect(() => {
2026-10-24T02:58:54.9218405Z 213 │ if (!isFocused && hasSource) props.onRequestClose();
2026-10-24T02:58:54.9218549Z · ──┬──
2026-10-24T02:58:54.9218723Z · ╰── Missing dependency `props`
2026-10-24T02:58:54.9218828Z 214 │ }, [isFocused, hasSource, props.onRequestClose]);
2026-10-24T02:58:54.9218937Z · ──────────┬─────────
2026-10-24T02:58:54.9219157Z · ╰── Overly precise dependency `props.onRequestClose`, use `props` instead
2026-10-24T02:58:54.9219232Z 215 │ const { source } = props;
2026-10-24T02:58:54.9219284Z ╰────
2026-10-24T02:58:54.9219801Z help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9220154Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9220159Z
2026-10-24T02:58:54.9220352Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9220479Z ╭─[apps/mobile/src/components/ComposerEditor.tsx:82:6]
2026-10-24T02:58:54.9220535Z 81 │ },
2026-10-24T02:58:54.9220599Z 82 │ [draftKey],
2026-10-24T02:58:54.9220668Z · ────┬───
2026-10-24T02:58:54.9220803Z · ╰── Unnecessary dependency `draftKey`
2026-10-24T02:58:54.9220857Z 83 │ );
2026-10-24T02:58:54.9220907Z ╰────
2026-10-24T02:58:54.9221195Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9221501Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9221503Z
2026-10-24T02:58:54.9221753Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9221920Z ╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:79:5]
2026-10-24T02:58:54.9221970Z 76 │
2026-10-24T02:58:54.9222035Z 77 │ useEffect(() => {
2026-10-24T02:58:54.9222104Z · ────┬────
2026-10-24T02:58:54.9222229Z · ╰── This is the containing effect
2026-10-24T02:58:54.9222357Z 78 │ const { host, code } = parsePairingUrl(connectionPairingUrl);
2026-10-24T02:58:54.9222429Z 79 │ setHostInput(host);
2026-10-24T02:58:54.9222503Z · ──────┬─────
2026-10-24T02:58:54.9222666Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9222731Z 80 │ setCodeInput(code);
2026-10-24T02:58:54.9222781Z ╰────
2026-10-24T02:58:54.9223365Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9223679Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9223743Z
2026-10-24T02:58:54.9224029Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9224192Z ╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:89:5]
2026-10-24T02:58:54.9224246Z 82 │
2026-10-24T02:58:54.9224308Z 83 │ useEffect(() => {
2026-10-24T02:58:54.9224377Z · ────┬────
2026-10-24T02:58:54.9224501Z · ╰── This is the containing effect
2026-10-24T02:58:54.9224590Z 84 │ if (routePairingUrl.length === 0) {
2026-10-24T02:58:54.9224650Z 85 │ return;
2026-10-24T02:58:54.9224702Z 86 │ }
2026-10-24T02:58:54.9224752Z 87 │
2026-10-24T02:58:54.9224867Z 88 │ const { host, code } = parsePairingUrl(routePairingUrl);
2026-10-24T02:58:54.9224941Z 89 │ setHostInput(host);
2026-10-24T02:58:54.9225019Z · ──────┬─────
2026-10-24T02:58:54.9225180Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9225246Z 90 │ setCodeInput(code);
2026-10-24T02:58:54.9225297Z ╰────
2026-10-24T02:58:54.9225875Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9226190Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9226195Z
2026-10-24T02:58:54.9226445Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9226612Z ╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:95:7]
2026-10-24T02:58:54.9226664Z 92 │
2026-10-24T02:58:54.9226727Z 93 │ useEffect(() => {
2026-10-24T02:58:54.9226794Z · ────┬────
2026-10-24T02:58:54.9226920Z · ╰── This is the containing effect
2026-10-24T02:58:54.9227002Z 94 │ if (pairingConnectionError) {
2026-10-24T02:58:54.9227073Z 95 │ setIsSubmitting(false);
2026-10-24T02:58:54.9227152Z · ───────┬───────
2026-10-24T02:58:54.9227319Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9227373Z 96 │ }
2026-10-24T02:58:54.9227428Z ╰────
2026-10-24T02:58:54.9228017Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9228333Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9228336Z
2026-10-24T02:58:54.9228585Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9228715Z ╭─[apps/mobile/src/components/MediaVideoPlayer.tsx:60:5]
2026-10-24T02:58:54.9228768Z 57 │
2026-10-24T02:58:54.9228884Z 58 │ useEffect(() => {
2026-10-24T02:58:54.9228982Z · ────┬────
2026-10-24T02:58:54.9229111Z · ╰── This is the containing effect
2026-10-24T02:58:54.9229205Z 59 │ const controller = new AbortController();
2026-10-24T02:58:54.9229278Z 60 │ setLoadState("pending");
2026-10-24T02:58:54.9229350Z · ──────┬─────
2026-10-24T02:58:54.9229510Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9229664Z 61 │ // A renewed signature is used on Retry, not as a reason to reset the native player.
2026-10-24T02:58:54.9229716Z ╰────
2026-10-24T02:58:54.9230330Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9230643Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9230646Z
2026-10-24T02:58:54.9230844Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9230974Z ╭─[apps/mobile/src/components/MediaVideoPlayer.tsx:71:7]
2026-10-24T02:58:54.9231054Z 70 │ return () => controller.abort();
2026-10-24T02:58:54.9231148Z 71 │ }, [player, props.playRequested, attempt]);
2026-10-24T02:58:54.9231314Z · ───┬── ─────────┬───────── ───┬───
2026-10-24T02:58:54.9231538Z · │ │ ╰── Unnecessary dependency `attempt`
2026-10-24T02:58:54.9231734Z · │ ╰── Unnecessary dependency `props.playRequested`
2026-10-24T02:58:54.9231870Z · ╰── Unnecessary dependency `player_0`
2026-10-24T02:58:54.9231923Z 72 │
2026-10-24T02:58:54.9231973Z ╰────
2026-10-24T02:58:54.9232256Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9232557Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9232560Z
2026-10-24T02:58:54.9232749Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9232893Z ╭─[apps/mobile/src/components/ui/Menu.tsx:54:36]
2026-10-24T02:58:54.9233065Z 53 │ const child = children as ReactElement<Pick<PressableProps, "onTouchStart" | "onPress">>;
2026-10-24T02:58:54.9233234Z 54 │ ╭─▶ children = cloneElement(child, {
2026-10-24T02:58:54.9233339Z 55 │ │ onTouchStart: (event) => {
2026-10-24T02:58:54.9233493Z 56 │ │ // Reset for a new touch, not onPressIn, which also fires when a
2026-10-24T02:58:54.9233647Z 57 │ │ // finger moves out of the row and back during the same gesture.
2026-10-24T02:58:54.9233771Z 58 │ │ menuPress.current.isPreparing = false;
2026-10-24T02:58:54.9233939Z 59 │ │ menuPress.current.suppressPress = menuPress.current.isOpen;
2026-10-24T02:58:54.9234051Z 60 │ │ pendingPress.current = null;
2026-10-24T02:58:54.9234171Z 61 │ │ child.props.onTouchStart?.(event);
2026-10-24T02:58:54.9234245Z 62 │ │ },
2026-10-24T02:58:54.9235819Z 63 │ │ onPress: (event) => {
2026-10-24T02:58:54.9235996Z 64 │ │ // Accessibility clicks have no touch identifier and must not inherit
2026-10-24T02:58:54.9236132Z 65 │ │ // cancellation from a previous physical gesture.
2026-10-24T02:58:54.9236295Z 66 │ │ const isTouch = typeof event.nativeEvent.identifier === "number";
2026-10-24T02:58:54.9236487Z 67 │ │ if (isTouch ? menuPress.current.suppressPress : menuPress.current.isOpen) {
2026-10-24T02:58:54.9236575Z 68 │ │ return;
2026-10-24T02:58:54.9236651Z 69 │ │ }
2026-10-24T02:58:54.9236786Z 70 │ │ if (isTouch && menuPress.current.isPreparing) {
2026-10-24T02:58:54.9236950Z 71 │ │ // A release can arrive between native menu preparation and display.
2026-10-24T02:58:54.9237110Z 72 │ │ // Let UIKit's display/cancel callback decide this press's outcome.
2026-10-24T02:58:54.9237209Z 73 │ │ event.persist();
2026-10-24T02:58:54.9237363Z 74 │ │ pendingPress.current = () => child.props.onPress?.(event);
2026-10-24T02:58:54.9237447Z 75 │ │ return;
2026-10-24T02:58:54.9237523Z 76 │ │ }
2026-10-24T02:58:54.9237639Z 77 │ │ child.props.onPress?.(event);
2026-10-24T02:58:54.9237715Z 78 │ │ },
2026-10-24T02:58:54.9237843Z 79 │ ├─▶ });
2026-10-24T02:58:54.9238072Z · ╰──── Passing a ref to a function may read its value during render
2026-10-24T02:58:54.9238173Z 80 │ menuProps.onMenuInteractionStart = () => {
2026-10-24T02:58:54.9238222Z ╰────
2026-10-24T02:58:54.9238681Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9239038Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9239073Z
2026-10-24T02:58:54.9239281Z ⚠ react(no-unstable-nested-components): Do not define components during render.
2026-10-24T02:58:54.9239385Z ╭─[apps/mobile/src/Stack.tsx:1074:21]
2026-10-24T02:58:54.9239448Z 1073 │ <Navigator
2026-10-24T02:58:54.9239578Z 1074 │ screenLayout={(props) => <GuardedScreenLayout {...props} />}
2026-10-24T02:58:54.9239713Z · ─────────────────────────────────────────────
2026-10-24T02:58:54.9239782Z 1075 │ screenListeners={{
2026-10-24T02:58:54.9239833Z ╰────
2026-10-24T02:58:54.9240232Z help: Move this component definition out of the parent component `AdaptiveRootStack` and pass data as props. If you want to allow component creation in props, set `allowAsProps` option to true.
2026-10-24T02:58:54.9240238Z
2026-10-24T02:58:54.9240427Z ⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
2026-10-24T02:58:54.9240571Z ╭─[apps/mobile/src/components/ComposerContextSheet.tsx:267:25]
2026-10-24T02:58:54.9240677Z 266 │ {record.elements?.map((element, index) => (
2026-10-24T02:58:54.9240837Z 267 │ <View key={`${element.selector ?? element.tagName}:${index}`} className="gap-3">
2026-10-24T02:58:54.9240987Z · ───────────────────────────────────────────────────────
2026-10-24T02:58:54.9241062Z 268 │ <ContextField
2026-10-24T02:58:54.9241112Z ╰────
2026-10-24T02:58:54.9241256Z help: Use a unique data-dependent key to avoid unnecessary rerenders
2026-10-24T02:58:54.9241258Z
2026-10-24T02:58:54.9241515Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9241661Z ╭─[apps/mobile/src/components/VideoPreviewModal.ios.tsx:63:55]
2026-10-24T02:58:54.9241719Z 61 │ }, []);
2026-10-24T02:58:54.9241782Z 62 │ useEffect(() => {
2026-10-24T02:58:54.9241852Z · ────┬────
2026-10-24T02:58:54.9241977Z · ╰── This is the containing effect
2026-10-24T02:58:54.9242125Z 63 │ if (playbackUrl === null && resolvedUrl !== null) setPlaybackUrl(resolvedUrl);
2026-10-24T02:58:54.9242242Z · ───────┬──────
2026-10-24T02:58:54.9242448Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9242529Z 64 │ }, [playbackUrl, resolvedUrl]);
2026-10-24T02:58:54.9242579Z ╰────
2026-10-24T02:58:54.9243165Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9243478Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9243481Z
2026-10-24T02:58:54.9243729Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9243907Z ╭─[apps/mobile/src/components/ProjectFavicon.tsx:159:5]
2026-10-24T02:58:54.9244129Z 154 │ const [activeFaviconRequest, setActiveFaviconRequest] = useState<typeof faviconRequest>(null);
2026-10-24T02:58:54.9244197Z 155 │ useLayoutEffect(() => {
2026-10-24T02:58:54.9244273Z · ───────┬───────
2026-10-24T02:58:54.9244402Z · ╰── This is the containing effect
2026-10-24T02:58:54.9244488Z 156 │ if (faviconRequest === null) return;
2026-10-24T02:58:54.9244538Z 157 │
2026-10-24T02:58:54.9244668Z 158 │ const endRequest = beginProjectFaviconRequest(faviconRequest);
2026-10-24T02:58:54.9244761Z 159 │ setActiveFaviconRequest(faviconRequest);
2026-10-24T02:58:54.9244850Z · ───────────┬───────────
2026-10-24T02:58:54.9245015Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9245088Z 160 │ return endRequest;
2026-10-24T02:58:54.9245141Z ╰────
2026-10-24T02:58:54.9245723Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9246038Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9246040Z
2026-10-24T02:58:54.9246229Z ⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
2026-10-24T02:58:54.9246383Z ╭─[apps/mobile/src/features/terminal/TerminalContextSheet.tsx:72:15]
2026-10-24T02:58:54.9246451Z 71 │ <Pressable
2026-10-24T02:58:54.9246516Z 72 │ key={index}
2026-10-24T02:58:54.9246597Z · ───────────
2026-10-24T02:58:54.9246680Z 73 │ accessibilityRole="button"
2026-10-24T02:58:54.9246730Z ╰────
2026-10-24T02:58:54.9246872Z help: Use a unique data-dependent key to avoid unnecessary rerenders
2026-10-24T02:58:54.9246875Z
2026-10-24T02:58:54.9247119Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9247270Z ╭─[apps/mobile/src/features/terminal/terminalLaunchContext.ts:117:5]
2026-10-24T02:58:54.9247434Z 112 │ const [entry, setEntry] = useState(() => ({ key: input.targetKey, location: candidate }));
2026-10-24T02:58:54.9247499Z 113 │ useEffect(() => {
2026-10-24T02:58:54.9247574Z · ────┬────
2026-10-24T02:58:54.9247701Z · ╰── This is the containing effect
2026-10-24T02:58:54.9247861Z 114 │ if (entry.key === input.targetKey && (entry.location !== null || candidate === null)) {
2026-10-24T02:58:54.9247923Z 115 │ return;
2026-10-24T02:58:54.9247976Z 116 │ }
2026-10-24T02:58:54.9248092Z 117 │ setEntry({ key: input.targetKey, location: candidate });
2026-10-24T02:58:54.9248161Z · ────┬───
2026-10-24T02:58:54.9248325Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9248443Z 118 │ }, [candidate, entry.key, entry.location, input.targetKey]);
2026-10-24T02:58:54.9248494Z ╰────
2026-10-24T02:58:54.9249125Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9249465Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9249468Z
2026-10-24T02:58:54.9249716Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9249904Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:643:5]
2026-10-24T02:58:54.9249956Z 638 │
2026-10-24T02:58:54.9250019Z 639 │ useEffect(() => {
2026-10-24T02:58:54.9250086Z · ────┬────
2026-10-24T02:58:54.9250215Z · ╰── This is the containing effect
2026-10-24T02:58:54.9250324Z 640 │ if (pendingLaunchEntry.key === launchTargetKey) {
2026-10-24T02:58:54.9250384Z 641 │ return;
2026-10-24T02:58:54.9250437Z 642 │ }
2026-10-24T02:58:54.9250508Z 643 │ setPendingLaunchEntry({
2026-10-24T02:58:54.9250593Z · ──────────┬──────────
2026-10-24T02:58:54.9250761Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9250830Z 644 │ key: launchTargetKey,
2026-10-24T02:58:54.9250879Z ╰────
2026-10-24T02:58:54.9251466Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9251780Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9251783Z
2026-10-24T02:58:54.9252027Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9252191Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:653:5]
2026-10-24T02:58:54.9252241Z 648 │
2026-10-24T02:58:54.9252306Z 649 │ useEffect(() => {
2026-10-24T02:58:54.9252373Z · ────┬────
2026-10-24T02:58:54.9252501Z · ╰── This is the containing effect
2026-10-24T02:58:54.9252615Z 650 │ if (initialAttachGridEntry.key === launchTargetKey) {
2026-10-24T02:58:54.9252676Z 651 │ return;
2026-10-24T02:58:54.9252730Z 652 │ }
2026-10-24T02:58:54.9252807Z 653 │ setInitialAttachGridEntry({
2026-10-24T02:58:54.9252898Z · ────────────┬────────────
2026-10-24T02:58:54.9253064Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9253134Z 654 │ key: launchTargetKey,
2026-10-24T02:58:54.9253184Z ╰────
2026-10-24T02:58:54.9253762Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9254122Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9254155Z
2026-10-24T02:58:54.9254400Z ⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
2026-10-24T02:58:54.9254563Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:746:7]
2026-10-24T02:58:54.9254616Z 743 │
2026-10-24T02:58:54.9254678Z 744 │ useEffect(() => {
2026-10-24T02:58:54.9254746Z · ────┬────
2026-10-24T02:58:54.9254870Z · ╰── This is the containing effect
2026-10-24T02:58:54.9254970Z 745 │ if (!routeEnvironmentId || !routeThreadId) {
2026-10-24T02:58:54.9255036Z 746 │ setLastGridSize({
2026-10-24T02:58:54.9255120Z · ───────┬───────
2026-10-24T02:58:54.9255286Z · ╰── Avoid calling setState() directly within an effect
2026-10-24T02:58:54.9255366Z 747 │ cols: DEFAULT_TERMINAL_COLS,
2026-10-24T02:58:54.9255415Z ╰────
2026-10-24T02:58:54.9256000Z help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
2026-10-24T02:58:54.9256313Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
2026-10-24T02:58:54.9256315Z
2026-10-24T02:58:54.9256515Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9256684Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:538:24]
2026-10-24T02:58:54.9256738Z 537 │ });
2026-10-24T02:58:54.9256862Z 538 │ }, [terminal.buffer, terminal.buffer.length, terminalKey]);
2026-10-24T02:58:54.9256968Z · ───────────┬──────────
2026-10-24T02:58:54.9257209Z · ╰── Overly precise dependency `terminal.buffer.length`, use `terminal.buffer` instead
2026-10-24T02:58:54.9257368Z 539 │ const cwd = terminal.summary?.cwd ?? selectedThreadProject?.workspaceRoot ?? null;
2026-10-24T02:58:54.9257418Z ╰────
2026-10-24T02:58:54.9257753Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9258086Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9258089Z
2026-10-24T02:58:54.9258287Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9258449Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:709:7]
2026-10-24T02:58:54.9258545Z 708 │ sentInitialInputKeyRef.current = null;
2026-10-24T02:58:54.9258610Z 709 │ }, [terminalKey]);
2026-10-24T02:58:54.9258685Z · ─────┬─────
2026-10-24T02:58:54.9258824Z · ╰── Unnecessary dependency `terminalKey`
2026-10-24T02:58:54.9258875Z 710 │
2026-10-24T02:58:54.9258925Z ╰────
2026-10-24T02:58:54.9259215Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9259659Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9259661Z
2026-10-24T02:58:54.9259888Z ⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
2026-10-24T02:58:54.9260056Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:800:52]
2026-10-24T02:58:54.9260111Z 799 │ };
2026-10-24T02:58:54.9260284Z 800 │ }, [canOperateTerminal, isRunning, pasteSession, terminal.lifecycleVersion, terminalKey]);
2026-10-24T02:58:54.9260461Z · ────────────┬──────────── ─────┬─────
2026-10-24T02:58:54.9260693Z · │ ╰── Unnecessary dependency `terminalKey`
2026-10-24T02:58:54.9260898Z · ╰── Unnecessary dependency `terminal.lifecycleVersion`
2026-10-24T02:58:54.9260949Z 801 │
2026-10-24T02:58:54.9260998Z ╰────
2026-10-24T02:58:54.9261280Z help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
2026-10-24T02:58:54.9261584Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
2026-10-24T02:58:54.9261586Z
2026-10-24T02:58:54.9261733Z ⚠ react(refs): Cannot access refs during render
2026-10-24T02:58:54.9261897Z ╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:793:24]
2026-10-24T02:58:54.9261950Z 792 │ }
2026-10-24T02:58:54.9262056Z 793 │ const pasteSession = pasteSessionRef.current;
2026-10-24T02:58:54.9262166Z · ───────────┬───────────
2026-10-24T02:58:54.9262325Z · ╰── Cannot access ref value during render
2026-10-24T02:58:54.9262375Z 794 │
2026-10-24T02:58:54.9262425Z ╰────
2026-10-24T02:58:54.9262958Z help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
2026-10-24T02:58:54.9263378Z note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
2026-10-24T02:58:54.9263381Z
2026-10-24T02:58:54.9263462Z Found 0 errors and 362 warnings in 5407 files (5.2s, 8 threads)
2026-10-24T02:58:54.9689199Z Post job cleanup.
2026-10-24T02:58:55.0291556Z Cache hit occurred on the primary key electron-Linux-X64-854e11ddd491bd4f350eebb67a74265df119376a3984c8e153cfe5fc8ced6309, not saving cache.
2026-10-24T02:58:55.0359461Z Post job cleanup.
2026-10-24T02:58:55.0370895Z ##[start-action display=Cache full pnpm store;id=__f6ac6304-82d7-4d9a-8e03-922c651584ec.__actions_cache]
2026-10-24T02:58:55.0975793Z Post job cleanup.
2026-10-24T02:58:55.1621187Z Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-3cb0b4d7cff93dc8fe33f2ea73cac71ca25a36270fcb648b9b4a9320151012ef, not saving cache.
2026-10-24T02:58:55.1653262Z ##[end-action id=__f6ac6304-82d7-4d9a-8e03-922c651584ec.__actions_cache;outcome=success;conclusion=success;duration_ms=128]
2026-10-24T02:58:55.1654812Z ##[start-action display=Cache Vite+;id=__f6ac6304-82d7-4d9a-8e03-922c651584ec.vp_cache]
2026-10-24T02:58:55.1673873Z Post job cleanup.
2026-10-24T02:58:55.2284423Z Cache hit occurred on the primary key vite-plus-home-v2-Linux-X64-1.3.0-node26.12.1-pnpm@12.14.0, not saving cache.
2026-10-24T02:58:55.2317445Z ##[end-action id=__f6ac6304-82d7-4d9a-8e03-922c651584ec.vp_cache;outcome=success;conclusion=success;duration_ms=66]
2026-10-24T02:58:55.2360933Z Post job cleanup.
2026-10-24T02:58:55.2751114Z [command]/usr/local/bin/git version
2026-10-24T02:58:55.2777659Z git version 2.55.0
2026-10-24T02:58:55.2794135Z Temporarily overriding HOME='/home/runner/_work/_temp/2f9ebf18-3e72-445f-be97-a50f417dbf4f' before making global git config changes
2026-10-24T02:58:55.2794499Z Adding repository directory to the temporary git global config as a safe directory
2026-10-24T02:58:55.2796917Z [command]/usr/local/bin/git config --global --add safe.directory /home/runner/_work/t3code/t3code
2026-10-24T02:58:55.2818223Z Removing SSH command configuration
2026-10-24T02:58:55.2821380Z [command]/usr/local/bin/git config --local --name-only --get-regexp core\.sshCommand
2026-10-24T02:58:55.2846585Z [command]/usr/local/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
2026-10-24T02:58:55.2968649Z fatal: No url found for submodule path '.repos/alchemy-effect/submodules/distilled' in .gitmodules
2026-10-24T02:58:55.2988498Z ##[warning]The process '/usr/local/bin/git' failed with exit code 128
2026-10-24T02:58:55.3028506Z A job completed hook has been configured by the self-hosted runner administrator
2026-10-24T02:58:55.3044595Z ##[group]Run '/job_completed.sh'
2026-10-24T02:58:55.3051532Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2026-10-24T02:58:55.3051697Z env:
2026-10-24T02:58:55.3051810Z BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 5307
2026-10-24T02:58:55.3051964Z BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 407
2026-10-24T02:58:55.3052104Z BLACKSMITH_CHECK_RUN_ID: 120760135878
2026-10-24T02:58:55.3052240Z BLACKSMITH_JOB_DISPLAY_NAME: Lint
2026-10-24T02:58:55.3052378Z GITHUB_ACTIONS_CACHE_MODE: write
2026-10-24T02:58:55.3052504Z ##[endgroup]
2026-10-24T02:58:55.3121466Z Docker container cache not activated, skipping hash computation.
2026-10-24T02:58:55.3364893Z No active SSH sessions detected. Proceeding with shutdown immediately.
2026-10-24T02:58:55.3404647Z Cleaning up orphan processes