GitHub check
256 KB of 603 KB loaded Download the full log (603 KB)
347 KB of earlier output not loaded
yield* Effect.yieldNow;
136 │ ╰─▶ }
137 │ return yield* Effect.die(new Error(`Expected ${count} durable subscriptions.`));
╰────
⚠ 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.
╭─[packages/client-runtime/src/rpc/client.test.ts:252:7]
251 │ yield* SubscriptionRef.set(activeSession, Option.some(session(firstClient)));
252 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 1; attempt += 1) {
253 │ │ yield* Effect.yieldNow;
254 │ ╰─▶ }
255 │ yield* SubscriptionRef.set(activeSession, Option.none());
╰────
⚠ 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.
╭─[packages/client-runtime/src/rpc/client.test.ts:258:7]
257 │
258 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
259 │ │ yield* Effect.yieldNow;
260 │ ╰─▶ }
261 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ 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.
╭─[packages/client-runtime/src/rpc/client.test.ts:322:7]
321 │ );
322 │ ╭─▶ for (let attempt = 0; attempt < 100 && observedFailures.length < 1; attempt += 1) {
323 │ │ yield* Effect.yieldNow;
324 │ ╰─▶ }
325 │
╰────
⚠ 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.
╭─[packages/client-runtime/src/rpc/client.test.ts:330:7]
329 │ yield* SubscriptionRef.set(activeSession, Option.some(session(secondClient)));
330 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
331 │ │ yield* Effect.yieldNow;
332 │ ╰─▶ }
333 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:100:85]
99 │ const startEditor = startScheduledTaskEditor;
100 │ const resetEditor = useCallback(() => startEditor(defaultEditor), [defaultEditor, startEditor]);
· ─────┬─────
· ╰── Unnecessary dependency `startEditor`
101 │ const readEditor = useCallback(
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:121:7]
120 │ setEditor,
121 │ startEditor,
· ─────┬─────
· ╰── Unnecessary dependency `startEditor`
122 │ hasChanges,
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/thread-inspector-content-stack.tsx:60:5]
58 │
59 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
60 │ setMountedModes((current) => {
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
61 │ if (current.has(props.mode)) {
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ 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.
╭─[apps/mobile/src/features/agent-awareness/remoteRegistration.test.ts:223:5]
222 │ let idlePasses = 0;
223 │ ╭─▶ for (;;) {
224 │ │ yield* Effect.promise(() => Promise.resolve());
225 │ │ const pending = backgroundRuntime.pending.shift();
226 │ │ if (!pending) {
227 │ │ idlePasses++;
228 │ │ if (idlePasses >= 3) {
229 │ │ return;
230 │ │ }
231 │ │ continue;
232 │ │ }
233 │ │ idlePasses = 0;
234 │ │ const exit = yield* Effect.exit(
235 │ │ pending.operation as Effect.Effect<unknown, unknown, ManagedRelay.ManagedRelayClient>,
236 │ │ );
237 │ │ yield* Effect.sync(() => {
238 │ │ pending.resolve(exit);
239 │ │ });
240 │ ╰─▶ }
241 │ },
╰────
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
259 │ .join("|");
260 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
261 │ stop();
· ──┬─
· ╰── Avoid calling setState() directly within an effect
262 │ }, [orderVersion]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
260 │ useEffect(() => {
261 │ stop();
· ──┬─
· ╰── Missing dependency `stop`
262 │ }, [orderVersion]);
· ──────┬─────
· ╰── Unnecessary dependency `orderVersion`
263 │ useEffect(
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:96:9]
95 │ const latest = useRef(props);
96 │ latest.current = props;
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
97 │ const gesture = useMemo(
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:104:18]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───────────────┬──────────────
· ╰── Passing a ref to a function may read its value during render
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:105:19]
104 │ .onStart(() => latest.current.onStart())
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:106:16]
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:107:21]
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
· ───────────────────────┬──────────────────────
· ╰── Passing a ref to a function may read its value during render
108 │ [props.disabled],
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:249:9]
248 │ const latest = useRef({ rows, planners, moveThread });
249 │ latest.current = { rows, planners, moveThread };
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
250 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:247:22]
246 │ const [preview, setPreview] = useState<Drag | null>(null);
247 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
248 │ const latest = useRef({ rows, planners, moveThread });
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:324:16]
323 │ update(0);
324 │ let last = performance.now();
· ────────┬────────
· ╰── Cannot call impure function
325 │ const tick = () => {
╰────
help: `performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:99:15]
98 │ () =>
99 │ Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
100 │ .enabled(!props.disabled)
╰────
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
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
⚠ react(memo-dependencies): Found missing memoization dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:108:5]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───┬──
· ╰── 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
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
108 │ [props.disabled],
· ────────┬───────
· ╰── This dependency list is missing values used by the callback
109 │ );
╰────
help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ oxc(no-accumulating-spread): Do not spread accumulators in loops
╭─[packages/client-runtime/src/state/shell.ts:189:5]
186 │ let waiting = yield* Ref.get(awaitingCompletion);
187 │ let next = initial;
· ──┬─
· ╰── From this accumulator
188 │ let receivedSnapshot = false;
189 │ for (const item of items) {
· ─┬─
· ╰── For this loop
190 │ if (item.kind === "synchronized") {
191 │ waiting = false;
192 │ if (Option.isSome(next.snapshot)) {
193 │ next = { ...next, status: "live", error: Option.none() };
· ───┬───
· ╰── From this spread
194 │ }
╰────
help: Consider using `Object.assign()` to mutate the accumulator instead.
note: Using spreads within accumulators leads to `O(n^2)` time complexity.
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:602:27]
601 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
602 │ const gesture = Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
603 │ .enabled(!props.disabled)
╰────
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
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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:406:5]
404 │
405 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
406 │ setInspectorSelection((current) => {
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
407 │ if (props.renderInspector === undefined) {
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:534:24]
533 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
534 │ ╭─▶ const GitInspector = () => (
535 │ │ <GitOverviewSheet
536 │ │ headerInset={inspectorHeaderInset}
537 │ │ presentation="inspector"
538 │ │ route={{ params: { environmentId: environmentId!, threadId: threadId! } }}
539 │ │ />
540 │ ╰─▶ );
541 │ const FilesInspector = () =>
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:541:26]
540 │ );
541 │ ╭─▶ const FilesInspector = () =>
542 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
543 │ │ <ThreadFileNavigatorPane
544 │ │ cwd={selectedThreadCwd}
545 │ │ environmentId={selectedThread.environmentId}
546 │ │ headerInset={inspectorHeaderInset}
547 │ │ projectName={selectedThreadProject?.title ?? "Files"}
548 │ │ selectedPath={null}
549 │ │ onSelectFile={handleSelectInspectorFile}
550 │ │ />
551 │ ╰─▶ ) : null;
552 │ const RouteInspector = () => props.renderInspector?.(inspectorHeaderInset);
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:444:5]
434 │ : null;
435 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
436 │ if (
437 │ props.active === false ||
438 │ activeDraftKey !== null ||
439 │ editingPendingTask !== null ||
440 │ selectedProject === null
441 │ ) {
442 │ return;
443 │ }
444 │ setActiveDraftKey(
· ────────┬────────
· ╰── Avoid calling setState() directly within an effect
445 │ createNewTaskDraft({
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:1244:36]
1243 │ <ActiveNewTaskContext value={activeNewTask}>
1244 │ <NewTaskFlowContext.Provider value={value}>{props.children}</NewTaskFlowContext.Provider>
· ─────────────
1245 │ </ActiveNewTaskContext>
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ eslint(no-unused-vars): Identifier 'HostProcess' is imported but never used.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:25:13]
24 │ import * as Schema from "effect/Schema";
25 │ import * as HostProcess from "@t3tools/shared/HostProcess";
· ─────┬─────
· ╰── 'HostProcess' is imported here
26 │
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Variable 'serverConfig' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:124:11]
123 │ const path = yield* Path.Path;
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
· ──────┬─────
· ╰── 'serverConfig' is declared here
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'serverSettings' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:125:11]
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
· ───────┬──────
· ╰── 'serverSettings' is declared here
126 │ const gitWorkflow = yield* GitWorkflowService.GitWorkflowService;
╰────
help: Consider removing this declaration.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/workspace/WorkspaceToolbar.ios.tsx:114:33]
113 │ return () => cancelAnimationFrame(frame);
114 │ }, [restoreSearch, tabActive, bottomSearch]);
· ──────┬─────
· ╰── Unnecessary dependency `bottomSearch`
115 │ const composeButton = nativeToolbarCompose ? (
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Type 'AuthSessionState' is imported but never used.
╭─[apps/web/src/components/settings/ProviderSettingsPanel.logic.ts:4:8]
3 │ AuthProvidersManageScope,
4 │ type AuthSessionState,
· ────────┬───────
· ╰── 'AuthSessionState' is imported here
5 │ type EnvironmentId,
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:773:7]
772 │ if (settingsSheetPresentation.isActive) {
773 │ settingsRoutePresentation.present(settingsRouteSession);
· ────────────┬────────────
· ╰── Missing dependency `settingsRoutePresentation`
774 │ }
775 │ }, [settingsRoutePresentation.present, settingsRouteSession, settingsSheetPresentation.isActive]);
· ────────────────┬────────────────
· ╰── Overly precise dependency `settingsRoutePresentation.present`, use `settingsRoutePresentation` instead
776 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:391:5]
387 │ typeof props.style.borderRadius === "number" ? props.style.borderRadius : 0;
388 │ const animatedBorderRadius = useSharedValue(targetBorderRadius);
· ──────────┬─────────
· ╰── `animatedBorderRadius` originates here
389 │ const shouldAnimate = props.animateLayout !== false && Platform.OS !== "android";
390 │ useLayoutEffect(() => {
391 │ animatedBorderRadius.value = shouldAnimate
· ──────────┬─────────
· ╰── `animatedBorderRadius` cannot be modified
392 │ ? withTiming(targetBorderRadius, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:217:7]
213 │ };
214 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
215 │ const inserted = ownerKey ? readComposerDraftSelection(ownerKey, draftMessage) : null;
216 │ if (inserted) {
217 │ setSelection((current) =>
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
218 │ current.start === inserted.start && current.end === inserted.end ? current : inserted,
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:298:7]
286 │ }, [hasWorkspaceSnapshot]);
287 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
288 │ if (!environmentId || !projectCwd || !selectedProviderInstanceId) return;
289 │ const key = `${environmentId}:${selectedProviderInstanceId}:${projectCwd}`;
290 │ const now = Date.now();
291 │ const lastRequest = workspaceRefreshKeyRef.current;
292 │ if (
293 │ lastRequest?.key === key &&
294 │ now - lastRequest.requestedAt < PROVIDER_WORKSPACE_SNAPSHOT_TTL_MS
295 │ )
296 │ return;
297 │ if (hasCurrentProviderWorkspaceSnapshot(selectedProviderStatus, projectCwd, now)) {
298 │ setWorkspaceRefreshRetry(null);
· ────────────┬───────────
· ╰── Avoid calling setState() directly within an effect
299 │ return;
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:328:5]
327 │ }, [
328 │ draftMessage,
· ──────┬─────
· ╰── Unnecessary dependency `draftMessage`
329 │ environmentId,
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ typescript(no-extraneous-class): Unexpected class with only a constructor.
╭─[apps/desktop/src/preview/Manager.test.ts:158:18]
157 │ BrowserWindow: browserWindowConstructor,
158 │ ╭─▶ ClipboardItem: class {
159 │ │ constructor(data: Record<string, unknown>) {
160 │ │ clipboardItemConstructor(data);
161 │ │ }
162 │ ╰─▶ },
163 │ clipboard: {
╰────
help: Try replacing this class with a standalone function or deleting it entirely
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:570:5]
568 │ }, []);
569 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
570 │ setKeyboardStateSuspect(false);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
571 │ }, [isKeyboardVisible, liveKeyboardHeight]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:966:7]
963 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
964 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
965 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
966 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
· ─────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
967 │ }
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1222:5]
1220 │
1221 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1222 │ setAnchorMessageId(null);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1223 │ setSubmittedMessageId(null);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:571:7]
570 │ setKeyboardStateSuspect(false);
571 │ }, [isKeyboardVisible, liveKeyboardHeight]);
· ────────┬──────── ─────────┬────────
· │ ╰── Unnecessary dependency `liveKeyboardHeight`
· ╰── Unnecessary dependency `isKeyboardVisible`
572 │ const handleOwnedInputFocusChange = (focused: boolean) => {
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1170:7]
1169 │ userInputInsetProgress.set(1);
1170 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
· ────────────┬───────────
· ╰── Unnecessary dependency `activeUserInputRequestId`
1171 │ const showContent = props.showContent ?? true;
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1228:15]
1227 │ freeze.set(false);
1228 │ }, [freeze, selectedThreadKey]);
· ────────┬────────
· ╰── Unnecessary dependency `selectedThreadKey`
1229 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1058:5]
1053 │ const composerPopoverHeight = useSharedValue(0);
1054 │ const floatingControlCoverage = useSharedValue(
· ───────────┬───────────
· ╰── `floatingControlCoverage` originates here
1055 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
1056 │ );
1057 │ useEffect(() => {
1058 │ floatingControlCoverage.value = withTiming(
· ───────────┬───────────
· ╰── `floatingControlCoverage` cannot be modified
1059 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1076:7]
1066 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
1067 │ const combinedContentInsetEndAdjustment = useSharedValue(
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` originates here
1068 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
1069 │ );
1070 │ useAnimatedReaction(
1071 │ () =>
1072 │ contentInsetEndAdjustment.value +
1073 │ floatingControlCoverage.value +
1074 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
1075 │ (value) => {
1076 │ combinedContentInsetEndAdjustment.value = value;
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` cannot be modified
1077 │ },
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:40:5]
37 │ const [initialized, setInitialized] = useState(false);
38 │ useLayoutEffect(() => {
· ───────┬───────
· ╰── This is the containing effect
39 │ reset();
40 │ setInitialized(true);
· ───────┬──────
· ╰── Avoid calling setState() directly within an effect
41 │ }, [reset]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:93:5]
88 │
89 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
90 │ if (!needsPreparation || !initialProjectRef.branch || waitingForProject) return;
91 │ const branchName = initialProjectRef.branch;
92 │ let active = true;
93 │ setPendingCheckouts((count) => count + 1);
· ─────────┬─────────
· ╰── Avoid calling setState() directly within an effect
94 │ // Serialize replacements: ignoring a stale result cannot undo its Git mutation.
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:555:70]
554 │ assert.deepStrictEqual(
555 │ (yield* Ref.get(fixture.syncCommands)).map(({ commandId: _, ...rest }) => rest),
· ┬
· ╰── '_' is declared here
556 │ [
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:1155:70]
1154 │ assert.deepStrictEqual(
1155 │ (yield* Ref.get(fixture.linkCommands)).map(({ commandId: _, ...rest }) => rest),
· ┬
· ╰── '_' is declared here
1156 │ [
╰────
help: Consider removing this parameter.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:361:7]
355 │ }, [cancelledIncomingShareId, navigation, props.incomingShareId]);
356 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
357 │ if (!isReturningToProjectPicker) {
358 │ return;
359 │ }
360 │ if (requestedInitialProjectAvailable) {
361 │ setIsReturningToProjectPicker(false);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
362 │ return;
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:504:9]
447 │
448 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
449 │ if (props.pendingTaskId || props.draftId) {
450 │ return;
451 │ }
452 │ if (lastInitialProjectRefRef.current !== props.initialProjectRef) {
453 │ lastInitialProjectRefRef.current = props.initialProjectRef;
454 │ appliedInitialProjectKeyRef.current = null;
455 │ }
456 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
457 │ const initialProjectId = props.initialProjectRef?.projectId;
458 │ if (initialEnvironmentId && initialProjectId) {
459 │ const directProject =
460 │ projects.find(
461 │ (project) =>
462 │ project.environmentId === initialEnvironmentId && project.id === initialProjectId,
463 │ ) ?? null;
464 │
465 │ if (directProject) {
466 │ // Apply the route's project once. Re-applying on every change would
467 │ // instantly revert environment/project switches made in the picker.
468 │ const directProjectKey = `${directProject.environmentId}:${directProject.id}`;
469 │ if (appliedInitialProjectKeyRef.current === directProjectKey) {
470 │ return;
471 │ }
472 │ if (props.initialProjectRef?.branch) {
473 │ if (
474 │ selectedProject?.environmentId !== directProject.environmentId ||
475 │ selectedProject.id !== directProject.id
476 │ ) {
477 │ setProject(directProject);
478 │ return;
479 │ }
480 │ if (!flow.draftKey) return;
481 │ // The route completes checkout before mounting this composer. Local
482 │ // mode reuses an existing worktree; worktree mode would create another.
483 │ updateComposerDraftSettings(flow.draftKey, {
484 │ workspaceSelection: {
485 │ mode: "local",
486 │ branch: props.initialProjectRef.branch,
487 │ worktreePath: props.initialProjectRef.worktreePath ?? null,
488 │ startFromOrigin: false,
489 │ },
490 │ });
491 │ }
492 │ appliedInitialProjectKeyRef.current = directProjectKey;
493 │ if (
494 │ selectedProject?.environmentId === directProject.environmentId &&
495 │ selectedProject.id === directProject.id
496 │ ) {
497 │ return;
498 │ }
499 │ setProject(directProject);
500 │ return;
501 │ }
502 │
503 │ if (projects.length > 0) {
504 │ setIsReturningToProjectPicker(true);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
505 │ }
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:604:5]
545 │
546 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
547 │ const shareId = props.incomingShareId;
548 │ const draftKey = flow.draftKey;
549 │ const destinationProject = selectedProject;
550 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
551 │ const initialProjectId = props.initialProjectRef?.projectId;
552 │ const selectedProjectMatchesRoute =
553 │ !initialEnvironmentId ||
554 │ !initialProjectId ||
555 │ (destinationProject?.environmentId === initialEnvironmentId &&
556 │ destinationProject.id === initialProjectId);
557 │ if (
558 │ !shareId ||
559 │ !draftKey ||
560 │ !destinationProject ||
561 │ !selectedProjectMatchesRoute ||
562 │ cancelledIncomingShareId === shareId
563 │ ) {
564 │ return;
565 │ }
566 │ const importKey = `${shareId}:${draftKey}`;
567 │ if (
568 │ startedShareImportKeyRef.current === importKey ||
569 │ cancellingShareImportKeyRef.current === importKey
570 │ ) {
571 │ return;
572 │ }
573 │
574 │ if (!incomingShare) {
575 │ if (isIncomingShareUnavailable && alertedUnavailableIncomingShareIdRef.current !== shareId) {
576 │ alertedUnavailableIncomingShareIdRef.current = shareId;
577 │ Dialog.alert(
578 │ "Shared content unavailable",
579 │ "The shared content is no longer in the inbox. You can continue editing this task draft.",
580 │ );
581 │ }
582 │ return;
583 │ }
584 │
585 │ if (
586 │ incomingShare.attachments.some((attachment) => attachment.type === "file") &&
587 │ selectedEnvironmentServerConfig === null
588 │ ) {
589 │ return;
590 │ }
591 │
592 │ if (alertedUnavailableIncomingShareIdRef.current === shareId) {
593 │ alertedUnavailableIncomingShareIdRef.current = null;
594 │ }
595 │ startedShareImportKeyRef.current = importKey;
596 │ const draftBackup =
597 │ shareImportDraftBackupRef.current.get(importKey) ?? getComposerDraftSnapshot(draftKey);
598 │ shareImportDraftBackupRef.current.set(importKey, draftBackup);
599 │ const importToken = Symbol(importKey);
600 │ let didReserveShare = false;
601 │ let didConsumeShare = false;
602 │ let needsDraftRestore = false;
603 │ activeShareImportTokenRef.current = importToken;
604 │ setImportingShareKey(importKey);
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
605 │ void (async () => {
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:524:5]
523 │ props.initialProjectRef,
524 │ props.incomingShareId,
· ──────────┬──────────
· ╰── Unnecessary dependency `props.incomingShareId`
525 │ props.pendingTaskId,
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:543:5]
542 │ loadedBranchesProjectKeyRef.current = projectKey;
543 │ flow.loadBranches();
· ──┬─
· ╰── Missing dependency `flow`
544 │ }, [flow.loadBranches, selectedProject]);
· ────────┬────────
· ╰── Overly precise dependency `flow.loadBranches`, use `flow` instead
545 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:766:5]
765 │ flow.draftKey,
766 │ hasImportedIncomingShare,
· ────────────┬───────────
· ╰── Unnecessary dependency `hasImportedIncomingShare`
767 │ incomingShare,
768 │ isIncomingShareInboxLoading,
· ─────────────┬─────────────
· ╰── Unnecessary dependency `isIncomingShareInboxLoading`
769 │ isIncomingShareUnavailable,
770 │ props.incomingShareId,
771 │ props.initialProjectRef?.environmentId,
772 │ props.initialProjectRef?.projectId,
773 │ releaseShareReservation,
774 │ reserveShare,
775 │ selectedEnvironmentServerConfig,
776 │ selectedProject,
777 │ shareImportAttempt,
· ─────────┬────────
· ╰── Unnecessary dependency `shareImportAttempt`
778 │ ]);
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ unicorn(prefer-set-has): should be a `Set`, and use `.has()` to check existence or non-existence.
╭─[apps/web/src/components/chat/useComposerSend.ts:985:13]
984 │ const changedBeforeDecline = draftChangedSinceSend();
985 │ ╭─▶ const pendingIdsBeforeDecline = pendingApprovalsRef.current.map(
986 │ │ (approval) => approval.requestId,
987 │ ╰─▶ );
988 │ const approvalResponding = approvalsToDecline.some((approval) =>
╰────
help: Switch to `Set`
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:279:5]
277 │ const [snoozeWakeTick, bumpSnoozeWakeTick] = useState(0);
278 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
279 │ setNow(new Date().toISOString());
· ───┬──
· ╰── Avoid calling setState() directly within an effect
280 │ const id = setInterval(() => setNow(new Date().toISOString()), 60_000);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Type 'EnvironmentThreadSearchMatch' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:13:8]
12 │ threadSearchMatchKey,
13 │ type EnvironmentThreadSearchMatch,
· ──────────────┬─────────────
· ╰── 'EnvironmentThreadSearchMatch' is imported here
14 │ } from "@t3tools/client-runtime/state/thread-search";
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:359:25]
358 │ // range) the boundary string is identical and the chain would die.
359 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
· ───────┬──────
· ╰── Unnecessary dependency `snoozeWakeTick`
360 │ const listItems = ((): readonly SidebarListItem[] => {
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:350:53]
349 │ if (Number.isNaN(wakeAtMs)) return;
350 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
· ─────┬────
· ╰── Cannot call impure function
351 │ const id = setTimeout(() => {
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:249:7]
248 │ mountedRef.current = false;
249 │ flow.setBranchQuery("");
· ──┬─
· ╰── Missing dependency `flow`
250 │ };
251 │ }, [flow.setBranchQuery]);
· ─────────┬─────────
· ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
252 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Variable 'layerCodexAppServerClientFactoryCommand' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.ts:1444:7]
1443 │
1444 │ const layerCodexAppServerClientFactoryCommand = (
· ───────────────────┬───────────────────
· ╰── 'layerCodexAppServerClientFactoryCommand' is declared here
1445 │ options: CodexClient.CodexAppServerClientOptions & {
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.ts:1680:7]
1679 │
1680 │ const layer: Layer.Layer<
· ──┬──
· ╰── 'layer' is declared here
1681 │ ProviderAdapter.ProviderAdapterV2,
╰────
help: Consider removing this declaration.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2195:5]
2193 │ );
2194 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
2195 │ setExpandedVideo(null);
· ────────┬───────
· ╰── Avoid calling setState() directly within an effect
2196 │ setExpandedFile(null);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2700:9]
2691 │ const stopFollowingEnd = useEffectEvent(() => setEndFollow(false));
2692 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
2693 │ if (!jumpToMessageId || loadedListKey !== listMountKey) return;
2694 │ const index = presentedFeed.findIndex(
2695 │ (entry) => entry.type === "message" && entry.id === jumpToMessageId,
2696 │ );
2697 │ if (index === -1) {
2698 │ const runId = messageFoldRunId(props.feed, jumpToMessageId);
2699 │ if (runId && !expandedTurnIds.has(runId)) {
2700 │ setInteractionState((current) => ({
· ─────────┬─────────
· ╰── Avoid calling setState() directly within an effect
2701 │ ...current,
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Identifier 'isMarkdownFileLinkLabel' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:70:10]
69 │ import { resolveAssetUrl } from "@t3tools/client-runtime/state/assets";
70 │ import { isMarkdownFileLinkLabel } from "@t3tools/shared/markdownLinks";
· ───────────┬───────────
· ╰── 'isMarkdownFileLinkLabel' is imported here
71 │ import { formatAttachmentSize } from "@t3tools/client-runtime/state/attachments";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'createContext' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:96:3]
95 │ import {
96 │ createContext,
· ──────┬──────
· ╰── 'createContext' is imported here
97 │ memo,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:112:3]
111 │ import {
112 │ ActivityIndicator,
· ────────┬────────
· ╰── 'ActivityIndicator' is imported here
113 │ Image,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ScrollView' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:119:3]
118 │ Pressable,
119 │ ScrollView,
· ─────┬────
· ╰── 'ScrollView' is imported here
120 │ StyleSheet,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'NativeText' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:121:11]
120 │ StyleSheet,
121 │ Text as NativeText,
· ─────┬────
· ╰── 'NativeText' is imported here
122 │ type ColorValue,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'tryOpenExternalUrl' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:144:10]
143 │ import { copyTextWithHaptic } from "../../lib/copyTextWithHaptic";
144 │ import { tryOpenExternalUrl } from "../../lib/openExternalUrl";
· ─────────┬────────
· ╰── 'tryOpenExternalUrl' is imported here
145 │ import { downloadAndShareAttachment } from "../../lib/attachmentDownload";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'faviconUrlForOrigin' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:147:10]
146 │ import { hasWideMarkdownBlock } from "../../lib/wideMarkdownBlocks";
147 │ import { faviconUrlForOrigin } from "@t3tools/shared/favicon";
· ─────────┬─────────
· ╰── 'faviconUrlForOrigin' is imported here
148 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'MediaVideoPlayer' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:161:10]
160 │ import { VideoAttachmentTile } from "../../components/VideoAttachmentTile";
161 │ import { MediaVideoPlayer } from "../../components/MediaVideoPlayer";
· ────────┬───────
· ╰── 'MediaVideoPlayer' is imported here
162 │ import { resolveMarkdownMediaPreview } from "../../lib/markdownMedia";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'mediaVideoPreviewUri' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:165:3]
164 │ attachmentVideoPreviewSource,
165 │ mediaVideoPreviewUri,
· ──────────┬─────────
· ╰── 'mediaVideoPreviewUri' is imported here
166 │ mediaVideoThumbnailKey,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'mediaVideoThumbnailKey' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:166:3]
165 │ mediaVideoPreviewUri,
166 │ mediaVideoThumbnailKey,
· ───────────┬──────────
· ╰── 'mediaVideoThumbnailKey' is imported here
167 │ type MediaVideoPreviewSource,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Type 'MediaVideoPreviewSource' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:167:8]
166 │ mediaVideoThumbnailKey,
167 │ type MediaVideoPreviewSource,
· ───────────┬───────────
· ╰── 'MediaVideoPreviewSource' is imported here
168 │ } from "../../lib/videoPreviewSource";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Type 'ReviewDiffTheme' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:175:15]
174 │ import { parseReviewCommentMessageSegments } from "../review/reviewCommentSelection";
175 │ import type { ReviewDiffTheme } from "../review/shikiReviewHighlighter";
· ───────┬───────
· ╰── 'ReviewDiffTheme' is imported here
176 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownFontSizes' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:190:3]
189 │ import {
190 │ resolveMarkdownFontSizes,
· ────────────┬───────────
· ╰── 'resolveMarkdownFontSizes' is imported here
191 │ resolveNativeMarkdownTypography,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownInlineCodePresentation' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:197:3]
196 │ normalizeNativeMarkdownUrl,
197 │ resolveMarkdownInlineCodePresentation,
· ──────────────────┬──────────────────
· ╰── 'resolveMarkdownInlineCodePresentation' is imported here
198 │ resolveMarkdownLinkPresentation,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useMarkdownCodeHighlight' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:242:10]
241 │ import { ThreadMcpApp } from "./McpAppWebView";
242 │ import { useMarkdownCodeHighlight } from "./markdownCodeHighlightState";
· ────────────┬───────────
· ╰── 'useMarkdownCodeHighlight' is imported here
243 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useAssetUrlState' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:246:3]
245 │ useAssetUrl,
246 │ useAssetUrlState,
· ────────┬───────
· ╰── 'useAssetUrlState' is imported here
247 │ useRefreshAssetUrl,
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2197:7]
2196 │ setExpandedFile(null);
2197 │ }, [props.environmentId, props.threadId, props.contentPresentation.kind]);
· ─────────┬───────── ───────┬────── ───────────────┬──────────────
· │ │ ╰── Unnecessary dependency `props.contentPresentation.kind`
· │ ╰── Unnecessary dependency `props.threadId`
· ╰── Unnecessary dependency `props.environmentId`
2198 │ const horizontalPadding = props.layoutVariant === "split" ? 20 : 16;
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2669:7]
2668 │ reportHeaderMaterialVisibility(false);
2669 │ }, [feedThreadKey, reportHeaderMaterialVisibility]);
· ──────┬──────
· ╰── Unnecessary dependency `feedThreadKey`
2670 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2685:7]
2684 │ }
2685 │ }, [listMountKey, props.contentInsetEndAdjustment, listRef]);
· ──────┬─────
· ╰── Unnecessary dependency `listMountKey`
2686 │ // Opening at a message: its run unfolds, the list stops following the end
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2881:7]
2880 │ }
2881 │ }, [expandedTurnIds, expandedWorkGroups, expandedWorkRows, settleDisclosureAfterLayout]);
· ───────┬─────── ─────────┬──────── ────────┬───────
· │ │ ╰── Unnecessary dependency `expandedWorkRows`
· │ ╰── Unnecessary dependency `expandedWorkGroups`
· ╰── Unnecessary dependency `expandedTurnIds`
2882 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:627:9]
626 │ };
627 │ }, [props.environmentId, attachment.id, httpBaseUrl]),
· ─────────┬───────── ──────┬────── ─────┬─────
· │ │ ╰── Unnecessary dependency `httpBaseUrl`
· │ ╰── Unnecessary dependency `attachment.id`
· ╰── Unnecessary dependency `props.environmentId`
628 │ );
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:57:5]
55 │
56 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
57 │ setDecodedSize(null);
· ───────┬──────
· ╰── Avoid calling setState() directly within an effect
58 │ }, [props.sourceKey]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:61:5]
59 │
60 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
61 │ setFailedUri(null);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
62 │ }, [props.uri]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:7:10]
6 │ import { parse, SvgAst, type JsxAST } from "react-native-svg";
7 │ import { ActivityIndicator, Pressable, StyleSheet, View, type ViewStyle } from "react-native";
· ────────┬────────
· ╰── 'ActivityIndicator' is imported here
8 │
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:58:7]
57 │ setDecodedSize(null);
58 │ }, [props.sourceKey]);
· ───────┬───────
· ╰── Unnecessary dependency `props.sourceKey`
59 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:62:7]
61 │ setFailedUri(null);
62 │ }, [props.uri]);
· ────┬────
· ╰── Unnecessary dependency `props.uri`
63 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:698:76]
697 │ const [snoozeGateClock, setSnoozeGateClock] = useState(() => ({ thread, now: Date.now() }));
698 │ if (snoozeGateClock.thread !== thread) setSnoozeGateClock({ thread, now: Date.now() });
· ─────┬────
· ╰── Cannot call impure function
699 │ const snoozeGateNow = new Date(snoozeGateClock.now).toISOString();
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:719:71]
718 │ const snoozePresets = useMemo(
719 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
· ─────┬────
· ╰── Cannot call impure function
720 │ [props.snoozePresetMinute, swipeActions.secondary],
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:720:6]
719 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
720 │ [props.snoozePresetMinute, swipeActions.secondary],
· ────────────┬───────────
· ╰── Unnecessary dependency `props.snoozePresetMinute`
721 │ );
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:766:7]
765 │ thread.pinnedAt,
766 │ variant,
· ───┬───
· ╰── Unnecessary dependency `variant`
767 │ ],
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:1216:21]
1215 │ {providerDrivers.slice(0, -1).map((driver, index) => (
1216 │ <View key={`${driver}:${index}`} className="-mr-1 opacity-30">
· ──────────────────────────
1217 │ <ProviderIcon provider={driver} size={12} />
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:290:50]
289 │ return (
290 │ <ExistingThreadSettingsRouteContext.Provider value={value}>
· ─────────────
291 │ {props.children}
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:654:44]
653 │ return (
654 │ <ThreadSettingsSessionContext.Provider value={value}>
· ─────────────
655 │ {props.children}
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:1462:55]
1461 │ return (
1462 │ <ThreadSettingsPickerPresentationContext.Provider value={presentation}>
· ────────────────────
1463 │ <ThreadSettingsPickerStack.Navigator
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/serverRuntimeStartup.ts:728:7]
727 │
728 │ const layer = layerWithOptions();
· ──┬──
· ╰── 'layer' is declared here
╰────
help: Consider removing this declaration.
⚠ 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.
╭─[apps/server/src/project/ProjectService.test.ts:94:3]
93 │ ) {
94 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
95 │ │ const project = Option.getOrThrow(yield* service.getById(projectId));
96 │ │ if (predicate(project)) return project;
97 │ │ yield* Effect.yieldNow;
98 │ ╰─▶ }
99 │ return yield* Effect.die(`Project ${projectId} was not enriched in time.`);
╰────
⚠ 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.
╭─[apps/server/src/project/ProjectEnrichmentService.test.ts:28:3]
27 │ ) {
28 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
29 │ │ const available = yield* service.peek(workspaceRoot);
30 │ │ if (predicate(available)) return available;
31 │ │ yield* Effect.yieldNow;
32 │ ╰─▶ }
33 │ return yield* Effect.die(`Project metadata for ${workspaceRoot} was not resolved in time.`);
╰────
⚠ eslint(no-unused-vars): Function 'layerClaudeAgentSdkReplayQueryRunner' is declared but never used.
╭─[apps/server/src/orchestration-v2/Adapters/ClaudeAdapterV2.testkit.ts:960:10]
959 │
960 │ function layerClaudeAgentSdkReplayQueryRunner(
· ──────────────────┬─────────────────
· ╰── 'layerClaudeAgentSdkReplayQueryRunner' is declared here
961 │ transcript: ClaudeAgentSdkReplayTranscript,
╰────
help: Consider removing this declaration.
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) 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.
╭─[apps/server/src/provider/acp/AntigravityProtocol.ts:263:20]
262 │ ...(update._meta !== undefined
263 │ ? { _meta: Schema.is(Schema.Record(Schema.String, Schema.Json))(meta) ? meta : null }
· ─────────
264 │ : {}),
╰────
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:111:5]
107 │ );
108 │ const separationProgress = useSharedValue(props.showScrollToEnd ? 1 : 0);
· ─────────┬────────
· ╰── `separationProgress` originates here
109 │
110 │ useEffect(() => {
111 │ separationProgress.value = withTiming(props.showScrollToEnd ? 1 : 0, CONTROL_TIMING);
· ─────────┬────────
· ╰── `separationProgress` cannot be modified
112 │ }, [props.showScrollToEnd, separationProgress]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
128 │ // and repeatedly retargets the animation as it grows.
129 │ const capsuleWidth = useSharedValue<number | null>(null);
· ──────┬─────
· ╰── `capsuleWidth` originates here
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
· ──────┬─────
· ╰── `capsuleWidth` cannot be modified
139 │ };
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
128 │ // and repeatedly retargets the animation as it grows.
129 │ const capsuleWidth = useSharedValue<number | null>(null);
· ──────┬─────
· ╰── `capsuleWidth` originates here
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
139 │ };
140 │ const hasStatus = props.status !== null;
141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
142 │ useEffect(() => {
143 │ if (!hasStatus) {
144 │ measuredWidthRef.current = null;
145 │ capsuleWidth.value = null;
· ──────┬─────
· ╰── `capsuleWidth` cannot be modified
146 │ }
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
142 │ useEffect(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
143 │ if (!hasStatus) {
144 │ measuredWidthRef.current = null;
145 │ capsuleWidth.value = null;
· ──────┬─────
· ╰── This modifies `capsuleWidth`
146 │ }
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
· ──────┬─────
· ╰── This modifies `capsuleWidth`
139 │ };
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-worktree-setup.ts:30:40]
28 │ const snapshot = resolveWorktreeSetupSnapshot(input.threadId, query.data, live);
29 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
30 │ if (snapshot && snapshot !== live) setHeld({ key, snapshot });
· ───┬───
· ╰── Avoid calling setState() directly within an effect
31 │ }, [key, live, snapshot]);
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/chat/useThreadLifecycle.tsx:178:58]
177 │ if (snoozeClockState.shell !== activeThreadShell) {
178 │ setSnoozeClockState({ shell: activeThreadShell, now: new Date().toISOString() });
· ─────┬────
· ╰── Cannot call impure function
179 │ }
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/Adapters/ClaudeAdapterV2.ts:10602:7]
10601 │
10602 │ const layer: Layer.Layer<
· ──┬──
· ╰── 'layer' is declared here
10603 │ ProviderAdapter.ProviderAdapterV2,
╰────
help: Consider removing this declaration.
⚠ unicorn(prefer-array-find): Prefer `find` over filtering and accessing the first result.
╭─[apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts:1998:15]
1997 │ assert.equal(
1998 │ items.filter((item) => item.type === "assistant_message").at(-1)?.text,
· ──────
1999 │ "authoritative answer",
╰────
help: Use `find(predicate)` instead of `filter(predicate)[0]` or similar patterns.
⚠ 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.
╭─[apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts:3951:7]
3950 │ const closeFiber = yield* Scope.close(sessionScope, Exit.void).pipe(Effect.forkScoped);
3951 │ ╭─▶ while (!responseLifecycle.includes("failed")) {
3952 │ │ yield* Effect.yieldNow;
3953 │ ╰─▶ }
3954 │ const responseExit = yield* Fiber.join(responseFiber);
╰────
⚠ 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.
╭─[apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts:6062:9]
6061 │ .pipe(Effect.forkScoped);
6062 │ ╭─▶ while (promptGates.length < 1) {
6063 │ │ yield* Effect.yieldNow;
6064 │ ╰─▶ }
6065 │ assert.isDefined(sessionUpdateHandler, "session update handler must be wired");
╰────
⚠ 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.
╭─[apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts:6197:9]
6196 │ .pipe(Effect.forkScoped);
6197 │ ╭─▶ while (promptGates.length < 2) {
6198 │ │ yield* Effect.yieldNow;
6199 │ ╰─▶ }
6200 │ if (sessionUpdateHandler === undefined || capturedMutation.current === null) {
╰────
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CommandPaletteThreadItems.tsx:152:58]
151 │ if (threadSearchQuery.trim().length > 0 && !threadSearchQuery.startsWith(">") && !isOpen) {
152 │ claimThreadOpen(thread.environmentId, thread.id, Date.now());
· ─────┬────
· ╰── Cannot call impure function
153 │ }
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ 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.
╭─[packages/effect-acp/src/client.ts:1269:11]
1268 │ extNotificationHandlers.set(CLIENT_METHODS.mcp_message, (params) =>
1269 │ Schema.decodeUnknownEffect(AcpSchemaV2.MessageMcpNotification)(params).pipe(
· ──────────────────────────
1270 │ Effect.mapError(() => AcpError.AcpRequestError.invalidParams()),
╰────
⚠ 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.
╭─[packages/effect-acp/src/errors.test.ts:129:28]
128 │ const secret = "acp-summary-secret";
129 │ const cause = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
130 │ Schema.Struct({
╰────
⚠ 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.
╭─[packages/effect-acp/src/schema.test.ts:18:12]
17 │ const command = { name: "plan", description: "Make a plan", input: { hint: "Task" } };
18 │ expect(Schema.is(V1.AvailableCommand)(command)).toBe(true);
· ─────────
19 │ expect(
╰────
⚠ 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.
╭─[packages/effect-acp/src/schema.test.ts:20:7]
19 │ expect(
20 │ Schema.is(V2.AvailableCommand)({ ...command, input: { type: "text", hint: "Task" } }),
· ─────────
21 │ ).toBe(true);
╰────
⚠ 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.
╭─[packages/effect-acp/src/protocol.test.ts:500:31]
499 │
500 │ const response = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
501 │ Schema.fromJsonString(JsonRpcErrorResponse),
╰────
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[apps/mobile/src/state/use-composer-drafts.ts:1022:15]
1021 │ instanceId,
1022 │ { ...(persisted.modelOptionMemory[instanceId] ?? {}), ...models },
· ──────────────────────────────────────────────────
1023 │ ]),
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/home/thread-swipe-actions.tsx:494:27]
493 │ >
494 │ {props.children(close)}
· ──┬──
· ╰── Cannot access ref value during render
495 │ </ReanimatedSwipeable>
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/diffs/nativeReviewDiffSurface.ts:277:39]
276 │
277 │ ╭─▶ return createElement(RawNativeView, {
278 │ │ ...nativeProps,
279 │ │ refreshEnabled: props.onPullToRefresh !== undefined,
280 │ │ ref: nativeRef,
281 │ ├─▶ });
· ╰──── Passing a ref to a function may read its value during render
282 │ }
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CommandPalette.tsx:2037:20]
2036 │ title: inferProjectTitleFromPath(destinationPath),
2037 │ createdAt: new Date().toISOString(),
· ─────┬────
· ╰── Cannot call impure function
2038 │ remoteUrl: addProjectCloneFlow.remoteUrl,
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ 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.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:566:7]
565 │ let afterSequence = created[0]!.sequence;
566 │ ╭─▶ for (let index = 1; index <= 32; index += 1) {
567 │ │ const nextEvent = {
568 │ │ id: EventId.make(`event:foundation-stream-race:${index}`),
569 │ │ type: "thread.metadata-updated" as const,
570 │ │ threadId,
571 │ │ providerInstanceId,
572 │ │ occurredAt: now,
573 │ │ payload: { ...thread, title: `Race update ${index}` },
574 │ │ } satisfies OrchestrationV2DomainEvent;
575 │ │ const reader = yield* eventSink
576 │ │ .stream({ threadId, afterSequence })
577 │ │ .pipe(Stream.runHead, Effect.forkChild);
578 │ │ yield* Effect.yieldNow;
579 │ │ const written = yield* eventSink.write({ events: [nextEvent] });
580 │ │ const received = yield* Fiber.join(reader);
581 │ │ if (Option.isNone(received)) {
582 │ │ return yield* Effect.die("The event stream ended before delivering the live event.");
583 │ │ }
584 │ │ assert.equal(received.value.sequence, written[0]?.sequence);
585 │ │ assert.equal(received.value.event.id, nextEvent.id);
586 │ │ afterSequence = received.value.sequence;
587 │ ╰─▶ }
588 │ }),
╰────
⚠ 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.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:2327:9]
2326 │ let settled = false;
2327 │ ╭─▶ while (!settled) {
2328 │ │ settled = (yield* outbox.listByCommandId(commandId)).every(
2329 │ │ (effect) => effect.status === "succeeded",
2330 │ │ );
2331 │ │ if (!settled) yield* Effect.yieldNow;
2332 │ ╰─▶ }
2333 │ }).pipe(Effect.provide(layerWorker), Effect.scoped);
╰────
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/keyboard/HardwareKeyboardCommandProvider.tsx:116:34]
115 │ return [...commands];
116 │ }, [activeThreadRef, pathname, registrationVersion, navigation]);
· ─────────┬─────────
· ╰── Unnecessary dependency `registrationVersion`
117 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Type 'EnvironmentThreadSearchMatch' is imported but never used.
╭─[apps/mobile/src/features/home/HomeScreen.tsx:15:8]
14 │ threadSearchMatchKey,
15 │ type EnvironmentThreadSearchMatch,
· ──────────────┬─────────────
· ╰── 'EnvironmentThreadSearchMatch' is imported here
16 │ } from "@t3tools/client-runtime/state/thread-search";
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/home/HomeScreen.tsx:527:25]
526 │ // range) the boundary string is identical and the chain would die.
527 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
· ───────┬──────
· ╰── Unnecessary dependency `snoozeWakeTick`
528 │ const v2SearchQuery = props.searchQuery.trim().toLocaleLowerCase();
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/home/HomeScreen.tsx:518:53]
517 │ if (Number.isNaN(wakeAtMs)) return;
518 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
· ─────┬────
· ╰── Cannot call impure function
519 │ const id = setTimeout(() => {
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:123:7]
118 │
119 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
120 │ if (orientationSettled) return;
121 │ const orientation = getNativeShowcaseOrientation();
122 │ if (orientation === null) {
123 │ setOrientationSettled(true);
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
124 │ return;
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:304:7]
292 │
293 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
294 │ if (
295 │ scene === null ||
296 │ requestedScene === null ||
297 │ scene !== requestedScene ||
298 │ !hasFixture ||
299 │ !orientationSettled ||
300 │ !themeApplied ||
301 │ (scene === "agent-activity" && !agentActivityStaged) ||
302 │ !isShowcaseNativeContentReady({ scene, themeId, renderSignal })
303 │ ) {
304 │ setReadyScene(null);
· ──────┬──────
· ╰── Avoid calling setState() directly within an effect
305 │ return;
╰────
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.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Variable 'lastOutcome' is declared but never used. Unused variables should start with a '_'.
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:128:9]
127 │ let cancelled = false;
128 │ let lastOutcome: string | null = null;
· ─────┬─────
· ╰── 'lastOutcome' is declared here
129 │ void retryShowcaseOperation(async () => applyNativeShowcaseOrientation(orientation), {
╰────
help: Consider removing this declaration.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:93:5]
90 │ }) {
91 │ const rotation = useSharedValue(props.hidden ? 1 : 0);
· ────┬───
· ╰── `rotation` originates here
92 │ useLayoutEffect(() => {
93 │ rotation.value = withTiming(props.hidden ? 1 : 0, TOOLBAR_FLIP_TIMING);
· ────┬───
· ╰── `rotation` cannot be modified
94 │ }, [props.hidden, rotation]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:269:5]
266 │ const variant = props.variant ?? "plain";
267 │ const loadingVisibility = useSharedValue(props.loading ? 1 : 0);
· ────────┬────────
· ╰── `loadingVisibility` originates here
268 │ useLayoutEffect(() => {
269 │ loadingVisibility.value = withTiming(props.loading ? 1 : 0, DICTATION_TIMING);
· ────────┬────────
· ╰── `loadingVisibility` cannot be modified
270 │ }, [loadingVisibility, props.loading]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:328:5]
325 │ }) {
326 │ const recordingVisibility = useSharedValue(props.phase === "recording" ? 1 : 0);
· ─────────┬─────────
· ╰── `recordingVisibility` originates here
327 │ useLayoutEffect(() => {
328 │ recordingVisibility.value = withTiming(props.phase === "recording" ? 1 : 0, DICTATION_TIMING);
· ─────────┬─────────
· ╰── `recordingVisibility` cannot be modified
329 │ }, [props.phase, recordingVisibility]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/GlobalVoiceInputControl.tsx:68:5]
65 │ const [expanded, setExpanded] = useState(false);
66 │ const progress = useSharedValue(0);
· ────┬───
· ╰── `progress` originates here
67 │ useEffect(() => {
68 │ progress.value = withTiming(expanded ? 1 : 0, MORPH_TIMING);
· ────┬───
· ╰── `progress` cannot be modified
69 │ }, [expanded, progress]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/useVoiceInputController.ts:27:14]
26 │ const latestInput = useRef(input);
27 │ latestInput.current = input;
· ─────┬─────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
28 │ const mounted = useRef(true);
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:122:38]
121 │ const audioLevelsRef = useRef(Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0));
122 │ const audioLevels = useSharedValue(audioLevelsRef.current);
· ───────────┬──────────
· ╰── Cannot access ref value during render
123 │ const sessionRef = useRef<VoiceInputSession | null>(null);
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:8]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:7]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:31]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:30]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ──────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:127:46]
126 │ if (!sessionRef.current || !recorderRef.current) {
127 │ ╭─▶ const recorder = createLazyVoiceRecorder({
128 │ │ create: () => new AudioModule.AudioRecorder(VOICE_RECORDING_OPTIONS),
129 │ │ onStatus: (status: RecordingStatus) => {
130 │ │ sessionRef.current?.controller.handleRecorderStatus({
131 │ │ isFinished: status.isFinished,
132 │ │ hasError: status.hasError || status.mediaServicesDidReset === true,
133 │ │ error: status.error,
134 │ │ url: status.url,
135 │ │ });
136 │ │ },
137 │ │ // Read when recording starts so preference changes do not re-render every composer.
138 │ │ selectInput: (inputs) => {
139 │ │ const preferences = registry.get(mobilePreferencesAtom);
140 │ │ if (!AsyncResult.isSuccess(preferences)) return null;
141 │ │ const known = microphoneOrder(preferences.value.microphones);
142 │ │ const order = rememberMicrophones(known, inputs);
143 │ │ if (order !== known) {
144 │ │ registry.set(updateMobilePreferencesAtom, {
145 │ │ transform: (current) => ({
146 │ │ microphones: rememberMicrophones(microphoneOrder(current.microphones), inputs),
147 │ │ }),
148 │ │ });
149 │ │ }
150 │ │ return preferredMicrophoneInput(inputs, order);
151 │ │ },
152 │ ├─▶ });
· ╰──── Passing a ref to a function may read its value during render
153 │ recorderRef.current = recorder;
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:153:16]
152 │ });
153 │ recorderRef.current = recorder;
· ─────┬─────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
154 │ sessionRef.current = new VoiceInputSession({
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:154:48]
153 │ recorderRef.current = recorder;
154 │ ╭─▶ sessionRef.current = new VoiceInputSession({
155 │ │ recorder,
156 │ │ getTranscriber: getLocalVoiceTranscriber,
157 │ │ requestPermission: async () => {
158 │ │ const permission = await requestRecordingPermissionsAsync();
159 │ │ return { granted: permission.granted, canAskAgain: permission.canAskAgain };
160 │ │ },
161 │ │ configureRecording: configureVoiceRecordingAudio,
162 │ │ releaseRecording: releaseVoiceRecordingAudio,
163 │ │ deleteRecording: (uri) => new File(uri).delete(),
164 │ │ onStateChange: (nextState) =>
165 │ │ setState({
166 │ │ state: nextState,
167 │ │ ownerKey: sessionRef.current?.ownerKey ?? null,
168 │ │ label: sessionRef.current?.label ?? null,
169 │ │ }),
170 │ ├─▶ });
· ╰──── Cannot access ref value during render
171 │ }
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:154:15]
153 │ recorderRef.current = recorder;
154 │ sessionRef.current = new VoiceInputSession({
· ─────┬────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
155 │ recorder,
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:185:7]
184 │ return () => subscription.remove();
185 │ }, [controller]);
· ─────┬────
· ╰── Cannot access ref value during render
186 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:185:6]
184 │ return () => subscription.remove();
185 │ }, [controller]);
· ──────┬─────
· ╰── Cannot access ref value during render
186 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:192:6]
191 │ },
192 │ [controller, recorder],
· ─────┬────
· ╰── Cannot access ref value during render
193 │ );
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:175:20]
174 │ const controller = session.controller;
175 │ const recorder = recorderRef.current;
· ─────────┬─────────
· ╰── Cannot access ref value during render
176 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:192:5]
191 │ },
192 │ [controller, recorder],
· ───────────┬──────────
· ╰── Cannot access ref value during render
193 │ );
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:246:20]
245 │ return () => clearInterval(intervalId);
246 │ }, [audioLevels, controller, recorder, state.phase]);
· ─────┬────
· ╰── Cannot access ref value during render
247 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:246:6]
245 │ return () => clearInterval(intervalId);
246 │ }, [audioLevels, controller, recorder, state.phase]);
· ────────────────────────┬───────────────────────
· ╰── Cannot access ref value during render
247 │
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:261:5]
260 │ setOwnerFocused,
261 │ session,
· ───┬───
· ╰── Cannot access ref value during render
262 │ stop,
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:251:10]
250 │
251 │ ╭─▶ return {
252 │ │ isAvailable: getLocalVoiceTranscriber() !== null || getNativeShowcaseScene() !== null,
253 │ │ state,
254 │ │ audioLevels,
255 │ │ elapsedSeconds,
256 │ │ isBusy: voiceInputBlocksSubmission(state),
257 │ │ ownerKey,
258 │ │ label,
259 │ │ focusedOwners,
260 │ │ setOwnerFocused,
261 │ │ session,
262 │ │ stop,
263 │ │ cancel,
264 │ ├─▶ };
· ╰──── Cannot access ref value during render
265 │ }
╰────
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
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:212:7]
121 │ const audioLevelsRef = useRef(Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0));
122 │ const audioLevels = useSharedValue(audioLevelsRef.current);
· ─────┬─────
· ╰── `audioLevels` originates here
123 │ const sessionRef = useRef<VoiceInputSession | null>(null);
124 │ const recorderRef = useRef<LazyVoiceRecorder<RecorderState> | null>(null);
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
127 │ const recorder = createLazyVoiceRecorder({
128 │ create: () => new AudioModule.AudioRecorder(VOICE_RECORDING_OPTIONS),
129 │ onStatus: (status: RecordingStatus) => {
130 │ sessionRef.current?.controller.handleRecorderStatus({
131 │ isFinished: status.isFinished,
132 │ hasError: status.hasError || status.mediaServicesDidReset === true,
133 │ error: status.error,
134 │ url: status.url,
135 │ });
136 │ },
137 │ // Read when recording starts so preference changes do not re-render every composer.
138 │ selectInput: (inputs) => {
139 │ const preferences = registry.get(mobilePreferencesAtom);
140 │ if (!AsyncResult.isSuccess(preferences)) return null;
141 │ const known = microphoneOrder(preferences.value.microphones);
142 │ const order = rememberMicrophones(known, inputs);
143 │ if (order !== known) {
144 │ registry.set(updateMobilePreferencesAtom, {
145 │ transform: (current) => ({
146 │ microphones: rememberMicrophones(microphoneOrder(current.microphones), inputs),
147 │ }),
148 │ });
149 │ }
150 │ return preferredMicrophoneInput(inputs, order);
151 │ },
152 │ });
153 │ recorderRef.current = recorder;
154 │ sessionRef.current = new VoiceInputSession({
155 │ recorder,
156 │ getTranscriber: getLocalVoiceTranscriber,
157 │ requestPermission: async () => {
158 │ const permission = await requestRecordingPermissionsAsync();
159 │ return { granted: permission.granted, canAskAgain: permission.canAskAgain };
160 │ },
161 │ configureRecording: configureVoiceRecordingAudio,
162 │ releaseRecording: releaseVoiceRecordingAudio,
163 │ deleteRecording: (uri) => new File(uri).delete(),
164 │ onStateChange: (nextState) =>
165 │ setState({
166 │ state: nextState,
167 │ ownerKey: sessionRef.current?.ownerKey ?? null,
168 │ label: sessionRef.current?.label ?? null,
169 │ }),
170 │ });
171 │ }
172 │
173 │ const session = sessionRef.current;
174 │ const controller = session.controller;
175 │ const recorder = recorderRef.current;
176 │
177 │ useEffect(() => {
178 │ const subscription = AppState.addEventListener("change", (nextState) => {
179 │ // iOS reports `inactive` while its permission dialog is open. Only the
180 │ // real background state cancels preparation; recorder status handles
181 │ // calls and route interruptions during capture.
182 │ if (nextState === "background") controller.appMovedToBackground();
183 │ });
184 │ return () => subscription.remove();
185 │ }, [controller]);
186 │
187 │ useEffect(
188 │ () => () => {
189 │ controller.dispose();
190 │ recorder.release();
191 │ },
192 │ [controller, recorder],
193 │ );
194 │
195 │ useEffect(() => {
196 │ if (state.phase !== "recording") return;
197 │
198 │ const tag = `voice-input:${keepAwakeId}:${++keepAwakeSessionRef.current}`;
199 │ const activation = activateKeepAwakeAsync(tag);
200 │ void activation.catch(() => {});
201 │ return () => {
202 │ // Release after activation settles, even if the recording ends immediately.
203 │ void activation.then(() => deactivateKeepAwake(tag)).catch(() => {});
204 │ };
205 │ }, [keepAwakeId, state.phase]);
206 │
207 │ useEffect(() => {
208 │ if (state.phase !== "preparing" && state.phase !== "recording") return;
209 │
210 │ if (audioLevelsRef.current.some((level) => level !== 0)) {
211 │ audioLevelsRef.current = Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0);
212 │ audioLevels.value = audioLevelsRef.current;
· ─────┬─────
· ╰── `audioLevels` cannot be modified
213 │ }
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:212:7]
206 │
207 │ useEffect(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `audioLevels` after render
208 │ if (state.phase !== "preparing" && state.phase !== "recording") return;
209 │
210 │ if (audioLevelsRef.current.some((level) => level !== 0)) {
211 │ audioLevelsRef.current = Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0);
212 │ audioLevels.value = audioLevelsRef.current;
· ─────┬─────
· ╰── This modifies `audioLevels`
213 │ }
╰────
help: This argument is a function which may reassign or mutate `audioLevels` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
Found 0 errors and 367 warnings in 5479 files (5.5s, 8 threads)
Post job cleanup.
Cache hit occurred on the primary key electron-Linux-X64-854e11ddd491bd4f350eebb67a74265df119376a3984c8e153cfe5fc8ced6309, not saving cache.
Post job cleanup.
##[start-action display=Cache full pnpm store;id=__2b1212e6-0049-4482-8ef5-f0f54f446c17.__actions_cache]
Post job cleanup.
Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-bab31c3827e90e1352d302da4c761fd1b91963ae565f5f0ea70972d0942af1f6, not saving cache.
##[end-action id=__2b1212e6-0049-4482-8ef5-f0f54f446c17.__actions_cache;outcome=success;conclusion=success;duration_ms=137]
##[start-action display=Cache Vite+;id=__2b1212e6-0049-4482-8ef5-f0f54f446c17.vp_cache]
Post job cleanup.
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.
##[end-action id=__2b1212e6-0049-4482-8ef5-f0f54f446c17.vp_cache;outcome=success;conclusion=success;duration_ms=72]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/4e863490-39d0-40fe-bab8-8ead509c21e2' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/local/bin/git config --global --add safe.directory /home/runner/_work/t3code/t3code
Removing SSH command configuration
[command]/usr/local/bin/git config --local --name-only --get-regexp core\.sshCommand
[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' || :"
fatal: No url found for submodule path '.repos/alchemy-effect/submodules/distilled' in .gitmodules
Warning: The process '/usr/local/bin/git' failed with exit code 128
A job completed hook has been configured by the self-hosted runner administrator
▸ Run '/job_completed.sh'
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 160
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 347
BLACKSMITH_CHECK_RUN_ID: 120984969685
BLACKSMITH_JOB_DISPLAY_NAME: Lint
GITHUB_ACTIONS_CACHE_MODE: write
Docker container cache not activated, skipping hash computation.
No active SSH sessions detected. Proceeding with shutdown immediately.
Cleaning up orphan processes