GitHub check
256 KB of 599 KB loaded Download the full log (599 KB)
343 KB of earlier output not loaded
· ────┬────
· ╰── This is the containing effect
63 │ if (playbackUrl === null && resolvedUrl !== null) setPlaybackUrl(resolvedUrl);
· ───────┬──────
· ╰── Avoid calling setState() directly within an effect
64 │ }, [playbackUrl, resolvedUrl]);
╰────
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(refs): Cannot access refs during render
╭─[apps/mobile/src/components/ui/Menu.tsx:54:36]
53 │ const child = children as ReactElement<Pick<PressableProps, "onTouchStart" | "onPress">>;
54 │ ╭─▶ children = cloneElement(child, {
55 │ │ onTouchStart: (event) => {
56 │ │ // Reset for a new touch, not onPressIn, which also fires when a
57 │ │ // finger moves out of the row and back during the same gesture.
58 │ │ menuPress.current.isPreparing = false;
59 │ │ menuPress.current.suppressPress = menuPress.current.isOpen;
60 │ │ pendingPress.current = null;
61 │ │ child.props.onTouchStart?.(event);
62 │ │ },
63 │ │ onPress: (event) => {
64 │ │ // Accessibility clicks have no touch identifier and must not inherit
65 │ │ // cancellation from a previous physical gesture.
66 │ │ const isTouch = typeof event.nativeEvent.identifier === "number";
67 │ │ if (isTouch ? menuPress.current.suppressPress : menuPress.current.isOpen) {
68 │ │ return;
69 │ │ }
70 │ │ if (isTouch && menuPress.current.isPreparing) {
71 │ │ // A release can arrive between native menu preparation and display.
72 │ │ // Let UIKit's display/cancel callback decide this press's outcome.
73 │ │ event.persist();
74 │ │ pendingPress.current = () => child.props.onPress?.(event);
75 │ │ return;
76 │ │ }
77 │ │ child.props.onPress?.(event);
78 │ │ },
79 │ ├─▶ });
· ╰──── Passing a ref to a function may read its value during render
80 │ menuProps.onMenuInteractionStart = () => {
╰────
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(memo-dependencies): Found missing memoization dependencies
╭─[apps/mobile/src/native/T3ComposerEditor.ios.tsx:197:6]
161 │ const tokens = collectComposerInlineTokens(props.value, {
162 │ preserveTrailingFrom: confirmedTokensRef.current,
· ─────────┬────────
· ╰── Missing dependency `confirmedTokensRef`. 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
163 │ });
164 │ confirmedTokensRef.current = tokens;
165 │ return JSON.stringify(
166 │ composerContextEditorTokens(props.value, tokens, skillLabels).map((token) => {
167 │ const record =
168 │ token.type === "context"
169 │ ? props.context?.records.find((record) => record.contextId === token.contextId)
170 │ : undefined;
171 │ const presentation = contextChipPresentation(
172 │ token.type === "context" ? token.kind : token.type,
173 │ record,
174 │ );
175 │ const icon = contextChipIcon(
176 │ presentation,
177 │ token.type === "mention" ? token.value : contextRecordFileName(record),
178 │ );
179 │ return {
180 │ type: token.type,
181 │ source: token.source,
182 │ start: token.start,
183 │ end: token.end,
184 │ accent: presentation.accent,
185 │ label:
186 │ token.type === "skill"
187 │ ? (skillLabels.get(token.value) ?? token.value)
188 │ : token.type === "context"
189 │ ? `${token.label}${props.context?.records.some((record) => record.contextId === token.contextId) ? "" : " · unavailable"}`
190 │ : basename(token.value),
191 │ detail: token.type === "context" ? composerChipSizeSuffix(record) : "",
192 │ iconUri: contextChipIconUri(icon),
193 │ tintsIcon: icon.kind === "chip",
194 │ };
195 │ }),
196 │ );
197 │ }, [props.value, props.context, skillLabels]);
· ────────────────────┬────────────────────
· ╰── This dependency list is missing values used by the callback
198 │ // Every render resolves against the snapshot history, so a render whose
╰────
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
⚠ react(memo-dependencies): Found missing memoization dependencies
╭─[apps/mobile/src/native/T3ComposerEditor.ios.tsx:259:5]
251 │ mostRecentEventCountRef.current = acknowledgedEventCount;
252 │ nativeEventSnapshotsRef.current.push({
· ───────────┬───────────
· ╰── Missing dependency `nativeEventSnapshotsRef`. 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
253 │ eventCount: acknowledgedEventCount,
254 │ value,
255 │ selection: nextSelection,
256 │ });
257 │ return acknowledgedEventCount;
258 │ },
259 │ [],
· ─┬
· ╰── This dependency list is missing values used by the callback
260 │ );
╰────
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
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/native/T3ComposerEditor.ios.tsx:162:29]
161 │ const tokens = collectComposerInlineTokens(props.value, {
162 │ preserveTrailingFrom: confirmedTokensRef.current,
· ─────────────┬────────────
· ╰── Cannot access ref value during render
163 │ });
╰────
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/native/T3ComposerEditor.ios.tsx:162:29]
161 │ const tokens = collectComposerInlineTokens(props.value, {
162 │ preserveTrailingFrom: confirmedTokensRef.current,
· ─────────────┬────────────
· ╰── Passing a ref to a function may read its value during render
163 │ });
╰────
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/native/T3ComposerEditor.ios.tsx:164:23]
163 │ });
164 │ confirmedTokensRef.current = tokens;
· ─────────┬────────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
165 │ return JSON.stringify(
╰────
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/native/T3ComposerEditor.ios.tsx:206:5]
205 │ mostRecentEventCount,
206 │ nativeEventSnapshotsRef.current,
· ───────────────┬───────────────
· ╰── Passing a ref to a function may read its value during render
207 │ );
╰────
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/native/T3ComposerEditor.ios.tsx:212:5]
211 │ mostRecentEventCount,
212 │ nativeEventSnapshotsRef.current,
· ───────────────┬───────────────
· ╰── Passing a ref to a function may read its value during render
213 │ );
╰────
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(exhaustive-effect-dependencies): Found missing effect dependencies
╭─[apps/mobile/src/native/T3ComposerEditor.ios.tsx:229:6]
225 │ nativeEventSnapshotsRef.current = pruneAcknowledgedComposerNativeEvents(
226 │ nativeEventSnapshotsRef.current,
· ───────────┬───────────
· ╰── Missing dependency `nativeEventSnapshotsRef`. 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
227 │ mostRecentEventCount,
228 │ );
229 │ }, [acknowledgesLatestNativeEvent, mostRecentEventCount]);
· ──────────────────────────┬──────────────────────────
· ╰── This dependency list is missing values used by the callback
230 │ const assumedValue = props.value;
╰────
help: Missing dependencies can cause an effect to fire less often than it should
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/native/T3ComposerEditor.ios.tsx:237:7]
236 │ nativeEventSnapshotsRef.current = assumeComposerControlledState(
237 │ nativeEventSnapshotsRef.current,
· ───────────┬───────────
· ╰── Missing dependency `nativeEventSnapshotsRef`. 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
238 │ controlledEventCount,
239 │ assumedValue,
240 │ );
241 │ }, [assumedValue, controlledEventCount, isNativeEcho, controlledDocumentJson]);
· ───────────┬──────────
· ╰── Unnecessary dependency `controlledDocumentJson`
242 │ const acceptNativeEvent = useCallback(
╰────
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-control-regex): Unexpected control character
╭─[apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx:220:46]
219 │ <Text selectable className="font-mono text-sm text-foreground">
220 │ {interaction.output.replace(/\x1b\[[0-?]*[ -/]*[@-~]/g, "")}
· ──┬─
· ╰── 'U+001B' is a control character.
221 │ </Text>
╰────
help: Avoid matching control characters in regular expressions. If intentional, disable this rule for the expression.
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/components/ComposerContextSheet.tsx:267:25]
266 │ {record.elements?.map((element, index) => (
267 │ <View key={`${element.selector ?? element.tagName}:${index}`} className="gap-3">
· ───────────────────────────────────────────────────────
268 │ <ContextField
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ 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/components/VideoPreviewModal.tsx:68:5]
66 │ const { id: attachmentId, fileUri } = attachment;
67 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
68 │ setUri(null);
· ───┬──
· ╰── Avoid calling setState() directly within an effect
69 │ setError(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/components/VideoPreviewModal.tsx:91:7]
90 │ };
91 │ }, [attachmentId, fileUri]);
· ──────┬───── ───┬───
· │ ╰── Unnecessary dependency `fileUri`
· ╰── Unnecessary dependency `attachmentId`
92 │ const mimeType = videoMimeType(attachment) ?? attachment.mimeType;
╰────
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/components/VideoPreviewModal.tsx:213:34]
212 │ useEffect(() => {
213 │ if (!isFocused && hasSource) props.onRequestClose();
· ──┬──
· ╰── Missing dependency `props`
214 │ }, [isFocused, hasSource, props.onRequestClose]);
· ──────────┬─────────
· ╰── Overly precise dependency `props.onRequestClose`, use `props` instead
215 │ const { source } = props;
╰────
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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:215:7]
211 │ };
212 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
213 │ const inserted = ownerKey ? readComposerDraftSelection(ownerKey, draftMessage) : null;
214 │ if (inserted) {
215 │ setSelection((current) =>
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
216 │ 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:296:7]
284 │ }, [hasWorkspaceSnapshot]);
285 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
286 │ if (!environmentId || !projectCwd || !selectedProviderInstanceId) return;
287 │ const key = `${environmentId}:${selectedProviderInstanceId}:${projectCwd}`;
288 │ const now = Date.now();
289 │ const lastRequest = workspaceRefreshKeyRef.current;
290 │ if (
291 │ lastRequest?.key === key &&
292 │ now - lastRequest.requestedAt < PROVIDER_WORKSPACE_SNAPSHOT_TTL_MS
293 │ )
294 │ return;
295 │ if (hasCurrentProviderWorkspaceSnapshot(selectedProviderStatus, projectCwd, now)) {
296 │ setWorkspaceRefreshRetry(null);
· ────────────┬───────────
· ╰── Avoid calling setState() directly within an effect
297 │ 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:326:5]
325 │ }, [
326 │ draftMessage,
· ──────┬─────
· ╰── Unnecessary dependency `draftMessage`
327 │ 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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:119:10]
117 │
118 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
119 │ void refreshNotifications();
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
120 │ const subscription = AppState.addEventListener("change", (state) => {
╰────
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/settings/SettingsNotificationsRouteScreen.tsx:128:7]
125 │
126 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
127 │ if (!isLoaded) {
128 │ setLiveActivityStatus("checking");
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
129 │ 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(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/Stack.tsx:1058:21]
1057 │ <Navigator
1058 │ screenLayout={(props) => <GuardedScreenLayout {...props} />}
· ─────────────────────────────────────────────
1059 │ screenOptions={({ route }) => {
╰────
help: Move this component definition out of the parent component `AdaptiveRootStack` and pass data as props. If you want to allow component creation in props, set `allowAsProps` option to true.
⚠ eslint(no-unused-vars): Type 'ThreadRunSummary' is imported but never used.
╭─[apps/web/src/types.ts:22:3]
21 │ EnvironmentThreadShell,
22 │ ThreadRunSummary,
· ────────┬───────
· ╰── 'ThreadRunSummary' is imported here
23 │ ThreadRuntimeSummary,
╰────
help: Consider removing this import.
⚠ unicorn(no-new-array): Do not use `new Array(singleArgument)`.
╭─[apps/web/src/terminal/ghostty/core.ts:194:19]
193 │ const count = Math.min(CHUNK_SIZE, graphemeLength - start);
194 │ const codes = new Array<number>(count);
· ────────────────────────
195 │ for (let index = 0; index < count; index += 1) {
╰────
help: It's not clear whether the argument is meant to be the length of the array or the only element. If the argument is the array's length, consider using `Array.from({ length: n })`. If the argument is the only element, use `[element]`.
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:682:6]
681 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
682 │ [props.snoozePresetMinute, swipeActions.secondary],
· ────────────┬───────────
· ╰── Unnecessary dependency `props.snoozePresetMinute`
683 │ );
╰────
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:728:7]
727 │ thread.pinnedAt,
728 │ variant,
· ───┬───
· ╰── Unnecessary dependency `variant`
729 │ ],
╰────
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(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:660:76]
659 │ const [snoozeGateClock, setSnoozeGateClock] = useState(() => ({ thread, now: Date.now() }));
660 │ if (snoozeGateClock.thread !== thread) setSnoozeGateClock({ thread, now: Date.now() });
· ─────┬────
· ╰── Cannot call impure function
661 │ 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(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:1178:21]
1177 │ {providerDrivers.slice(0, -1).map((driver, index) => (
1178 │ <View key={`${driver}:${index}`} className="-mr-1 opacity-30">
· ──────────────────────────
1179 │ <ProviderIcon provider={driver} size={12} />
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ 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(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:595:27]
594 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
595 │ const gesture = Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
596 │ .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(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
86 │
87 │ const cardCoverage = props.cardCoverage;
· ──────┬─────
· ╰── `cardCoverage` originates here
88 │ const barHeightRef = useRef(0);
89 │ const cardHeightRef = useRef(0);
90 │ const cardHeight = useSharedValue(0);
91 │ const notifyCoverage = useCallback(() => {
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── `cardCoverage` cannot be modified
101 │ return;
╰────
help: Do not mutate component props or hook arguments. If the value should change, update it where it is owned and pass an update callback, or use local state
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/PendingUserInputCard.tsx:118:7]
89 │ const cardHeightRef = useRef(0);
90 │ const cardHeight = useSharedValue(0);
· ─────┬────
· ╰── `cardHeight` originates here
91 │ const notifyCoverage = useCallback(() => {
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
101 │ return;
102 │ }
103 │ cardCoverage.value = withTiming(coverage, {
104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
105 │ easing: Easing.out(Easing.cubic),
106 │ });
107 │ }, [cardCoverage]);
108 │ const handleBarLayout = useCallback(
109 │ (event: LayoutChangeEvent) => {
110 │ barHeightRef.current = event.nativeEvent.layout.height;
111 │ notifyCoverage();
112 │ },
113 │ [notifyCoverage],
114 │ );
115 │ const handleCardLayout = useCallback(
116 │ (event: LayoutChangeEvent) => {
117 │ cardHeightRef.current = event.nativeEvent.layout.height;
118 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── `cardHeight` cannot be modified
119 │ notifyCoverage();
╰────
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/PendingUserInputCard.tsx:100:7]
90 │ const cardHeight = useSharedValue(0);
91 │ const notifyCoverage = useCallback(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── This modifies `cardCoverage`
101 │ return;
╰────
help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
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/PendingUserInputCard.tsx:100:7]
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── This modifies `cardCoverage`
101 │ return;
102 │ }
103 │ cardCoverage.value = withTiming(coverage, {
104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
105 │ easing: Easing.out(Easing.cubic),
106 │ });
107 │ }, [cardCoverage]);
108 │ const handleBarLayout = useCallback(
109 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
110 │ barHeightRef.current = event.nativeEvent.layout.height;
╰────
help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
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/PendingUserInputCard.tsx:118:7]
115 │ const handleCardLayout = useCallback(
116 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardHeight` after render
117 │ cardHeightRef.current = event.nativeEvent.layout.height;
118 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── This modifies `cardHeight`
119 │ notifyCoverage();
╰────
help: This argument is a function which may reassign or mutate `cardHeight` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/lib/useHoverGesture.ts:8:15]
7 │ () =>
8 │ Gesture.Hover()
· ──┬──
· ╰── `Hover` may be a component
9 │ .manualActivation(true)
╰────
help: Render `Hover` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Hover` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ 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.
⚠ 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/state/use-vcs-action-state.ts:86:5]
83 │ const [nowMs, setNowMs] = useState(() => Date.now());
84 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
85 │ if (!actionState.isRunning) return;
86 │ setNowMs(Date.now());
· ────┬───
· ╰── Avoid calling setState() directly within an effect
87 │ const interval = setInterval(() => setNowMs(Date.now()), 1000);
╰────
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/review/ReviewSheet.tsx:462:7]
461 │ showAuxiliaryPane("inspector");
462 │ }, [environmentId, showAuxiliaryPane, threadId]);
· ──────┬────── ────┬───
· │ ╰── Unnecessary dependency `threadId`
· ╰── Unnecessary dependency `environmentId`
463 │ const {
╰────
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(static-components): Cannot create components during render
╭─[apps/mobile/src/features/review/ReviewSheet.tsx:733:20]
500 │ // same check.
501 │ const NativeReviewDiffView = resolveNativeReviewDiffView();
· ─────────────┬─────────────
· ╰── The component is created during render here
502 │ const nativeReviewDiffViewRef = useRef<NativeReviewDiffViewHandle>(null);
503 │ const showcasedReviewDrawRef = useRef<string | null>(null);
504 │ const [isPullRefreshing, setIsPullRefreshing] = useState(false);
505 │ const handlePullToRefresh = async () => {
506 │ setIsPullRefreshing(true);
507 │ await refreshSelectedSection();
508 │ setIsPullRefreshing(false);
509 │ };
510 │ const reviewFileNavigatorRef = useRef<ReviewFileNavigatorHandle>(null);
511 │ const reviewFiles = parsedDiff.kind === "files" ? parsedDiff.files : [];
512 │ const fileVisibility = useReviewFileVisibility({
513 │ threadKey: reviewCache.threadKey,
514 │ sectionId: selectedSection?.id ?? null,
515 │ files: reviewFiles,
516 │ cachedExpandedFileIds: selectedSection?.id
517 │ ? reviewCache.expandedFileIdsBySection[selectedSection.id]
518 │ : undefined,
519 │ cachedViewedFileIds: selectedSection?.id
520 │ ? reviewCache.viewedFileIdsBySection[selectedSection.id]
521 │ : undefined,
522 │ });
523 │ const { collapsedFileIds, toggleExpandedFile, toggleViewedFile, viewedFileIds } = fileVisibility;
524 │ const commentSelection = useReviewCommentSelectionController({
525 │ environmentId,
526 │ threadId,
527 │ selectedSection,
528 │ nativeReviewDiffData,
529 │ });
530 │ const nativeBridge = useNativeReviewDiffBridge({
531 │ threadKey: reviewCache.threadKey,
532 │ sectionId: selectedSection?.id ?? null,
533 │ diff: selectedSection?.diff,
534 │ data: nativeReviewDiffData,
535 │ collapsedFileIds,
536 │ viewedFileIds,
537 │ selectedRowIds: commentSelection.selectedRowIds,
538 │ canHighlight: parsedDiff.kind === "files",
539 │ });
540 │ const showcaseReviewKey =
541 │ SHOWCASE_ENABLED && parsedDiff.kind === "files" && selectedSection
542 │ ? `${reviewCache.threadKey}:${selectedSection.id}:${nativeBridge.tokensResetKey}:${nativeBridge.themeId}`
543 │ : null;
544 │ const handleNativeDebug = (event: NativeSyntheticEvent<Record<string, unknown>>) => {
545 │ nativeBridge.onDebug(event);
546 │ if (
547 │ showcaseReviewKey === null ||
548 │ showcasedReviewDrawRef.current === showcaseReviewKey ||
549 │ !isNativeReviewDiffDrawEvent(event.nativeEvent)
550 │ ) {
551 │ return;
552 │ }
553 │ showcasedReviewDrawRef.current = showcaseReviewKey;
554 │ reportShowcaseSceneRendered({ scene: "review", themeId: nativeBridge.themeId });
555 │ };
556 │
557 │ const handleSelectFile = async (fileId: string | null) => {
558 │ loadVisibleFile(fileId, true);
559 │ commentSelection.clearSelection();
560 │ if (fileId !== null && collapsedFileIds.includes(fileId)) {
561 │ toggleExpandedFile(fileId);
562 │ }
563 │ const nativeView = nativeReviewDiffViewRef.current;
564 │ if (!nativeView) return;
565 │ const result = await settlePromise(() =>
566 │ fileId === null ? nativeView.scrollToTop(true) : nativeView.scrollToFile(fileId, true),
567 │ );
568 │ if (AsyncResult.isFailure(result)) {
569 │ console.error("[review] Failed to navigate to diff file", squashAtomCommandFailure(result));
570 │ }
571 │ };
572 │ const handleVisibleFileChange = (
573 │ event: NativeSyntheticEvent<{ readonly fileId?: string | null }>,
574 │ ) => {
575 │ loadVisibleFile(event.nativeEvent.fileId ?? null);
576 │ reviewFileNavigatorRef.current?.setVisibleFile(event.nativeEvent.fileId ?? null);
577 │ };
578 │ const renderInspector = () => (
579 │ <ReviewFileNavigator
580 │ ref={reviewFileNavigatorRef}
581 │ files={nativeReviewDiffData.files}
582 │ headerInset={insets.top}
583 │ sectionId={selectedSection?.id ?? null}
584 │ onSelectFile={(fileId) => void handleSelectFile(fileId)}
585 │ />
586 │ );
587 │
588 │ const handleNativeToggleFile = (event: NativeSyntheticEvent<{ readonly fileId?: string }>) => {
589 │ const { fileId } = event.nativeEvent;
590 │ if (fileId) {
591 │ loadVisibleFile(fileId, true);
592 │ toggleExpandedFile(fileId);
593 │ }
594 │ };
595 │
596 │ const handleNativeToggleViewedFile = (
597 │ event: NativeSyntheticEvent<{ readonly fileId?: string }>,
598 │ ) => {
599 │ const { fileId } = event.nativeEvent;
600 │ if (fileId) {
601 │ toggleViewedFile(fileId);
602 │ }
603 │ };
604 │
605 │ const parsedDiffNotice =
606 │ parsedDiff.kind === "files" || parsedDiff.kind === "raw" ? parsedDiff.notice : null;
607 │ const hasCachedSelectedDiff = selectedSection?.diff != null;
608 │ const hasAnyCachedDiff = reviewSections.some((section) => section.diff != null);
609 │ const sectionMenu = buildReviewSectionMenu(reviewSections);
610 │ const { showConnectionNotice, showSectionToolbar } = resolveReviewAvailability({
611 │ hasEnvironmentPresentation: environment.isReady,
612 │ isEnvironmentConnected: isEnvironmentReady,
613 │ hasCachedSelectedDiff,
614 │ hasAnyCachedDiff,
615 │ });
616 │ const handleRetryEnvironment = () => {
617 │ void retryEnvironment(environmentId);
618 │ };
619 │ const handleReturnToThread = () => {
620 │ if (navigation.canGoBack()) {
621 │ navigation.goBack();
622 │ return;
623 │ }
624 │ navigation.navigate("Thread", {
625 │ environmentId: String(environmentId),
626 │ threadId: String(threadId),
627 │ });
628 │ };
629 │ const androidHeaderSubtitle = [
630 │ selectedSection?.title,
631 │ headerDiffSummary.additions,
632 │ headerDiffSummary.deletions,
633 │ ]
634 │ .filter((part): part is string => Boolean(part))
635 │ .join(" · ");
636 │
637 │ const showChangedFilesPane =
638 │ !showConnectionNotice &&
639 │ selectedSection !== null &&
640 │ parsedDiff.kind === "files" &&
641 │ NativeReviewDiffView !== null;
642 │ useRegisterWorkspaceInspector(showChangedFilesPane ? renderInspector : undefined);
643 │ const showChangedFilesToggle = panes.supportsAuxiliaryPane && showChangedFilesPane;
644 │
645 │ const listHeader = (() => {
646 │ const children: ReactElement[] = [];
647 │
648 │ if (error) {
649 │ children.push(
650 │ <View
651 │ key="review-error"
652 │ className={cn(
653 │ "bg-card px-4 py-3",
654 │ Platform.OS === "android" ? "m-2 rounded-[20px]" : "border-b border-border",
655 │ )}
656 │ >
657 │ <Text className="text-sm font-t3-bold text-foreground">Review unavailable</Text>
658 │ <Text className="text-xs leading-normal text-foreground-muted">{error}</Text>
659 │ </View>,
660 │ );
661 │ }
662 │
663 │ if (parsedDiffNotice) {
664 │ children.push(<ReviewNotice key="review-notice" notice={parsedDiffNotice} />);
665 │ }
666 │
667 │ if (children.length === 0) {
668 │ return null;
669 │ }
670 │
671 │ return <>{children}</>;
672 │ })();
673 │ const headerSubtitle = [
674 │ headerDiffSummary.additions,
675 │ headerDiffSummary.deletions,
676 │ pendingReviewCommentCount > 0
677 │ ? `${pendingReviewCommentCount} comment${pendingReviewCommentCount === 1 ? "" : "s"}`
678 │ : null,
679 │ ]
680 │ .filter(Boolean)
681 │ .join(" · ");
682 │ const headerTitleText = selectedSection?.title ?? "Review changes";
683 │
684 │ return (
685 │ <>
686 │ <ReviewHeader
687 │ environmentId={environmentId}
688 │ threadId={threadId}
689 │ title={headerTitleText}
690 │ subtitle={headerSubtitle}
691 │ androidSubtitle={androidHeaderSubtitle}
692 │ iconColor={headerIcon}
693 │ selectedThreadCwd={selectedThreadCwd}
694 │ sectionMenu={sectionMenu}
695 │ selectedSection={selectedSection}
696 │ showSectionToolbar={showSectionToolbar}
697 │ showChangedFilesToggle={showChangedFilesToggle}
698 │ onRefresh={handlePullToRefresh}
699 │ onSelectSection={selectSection}
700 │ onReturnToThread={handleReturnToThread}
701 │ />
702 │
703 │ <ScreenContent>
704 │ <View className="flex-1 bg-sheet android:bg-sheet-solid">
705 │ {showConnectionNotice ? (
706 │ <View className="flex-1" style={{ paddingTop: topContentInset }}>
707 │ <EnvironmentConnectionNotice
708 │ environmentLabel={environment.presentation?.entry.target.label ?? "Environment"}
709 │ connection={
710 │ environment.presentation?.connection ?? {
711 │ phase: "available",
712 │ error: null,
713 │ traceId: null,
714 │ }
715 │ }
716 │ resourceName="review"
717 │ onRetry={handleRetryEnvironment}
718 │ />
719 │ </View>
720 │ ) : selectedSection && parsedDiff.kind === "files" && NativeReviewDiffView ? (
721 │ <View
722 │ className="flex-1"
723 │ style={{
724 │ backgroundColor: nativeBridge.theme.background,
725 │ }}
726 │ >
727 │ <View
728 │ className="min-w-0 flex-1"
729 │ style={listHeader ? { paddingTop: topContentInset } : undefined}
730 │ >
731 │ {listHeader}
732 │ <View className="min-w-0 flex-1" collapsable={false}>
733 │ <NativeReviewDiffView
· ──────────┬─────────
· ╰── This component is created during render
734 │ collapsable={false}
╰────
help: Components created during render will reset their state each time they are created. Declare components outside of render
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/review/ReviewCommentCard.tsx:223:31]
222 │ ? snippetTokens.map((line, lineIndex) => (
223 │ <NativeText key={lineIndex}>
· ───────────────
224 │ {lineIndex > 0 ? "\n" : ""}
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/review/ReviewCommentCard.tsx:227:25]
226 │ <NativeText
227 │ key={tokenIndex}
· ────────────────
228 │ style={{
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/review/ReviewCommentComposerSheet.tsx:103:7]
100 │
101 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
102 │ if (!target || selectedLines.length === 0) {
103 │ setHighlightedLinesById({});
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
104 │ 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/files/FileTreeBrowser.tsx:155:5]
150 │
151 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
152 │ if (!controlledSelectedPath) {
153 │ return;
154 │ }
155 │ setExpandedPaths((current) => {
· ────────┬───────
· ╰── Avoid calling setState() directly within an effect
156 │ const ancestors = ancestorPaths(controlledSelectedPath);
╰────
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/review/useReviewCommentSelectionController.ts:107:5]
104 │
105 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
106 │ clearReviewCommentTarget();
107 │ setPendingNativeCommentSelection(null);
· ────────────────┬───────────────
· ╰── Avoid calling setState() directly within an effect
108 │ }, [selectedSection?.id]);
╰────
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/review/useReviewCommentSelectionController.ts:112:7]
109 │
110 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
111 │ if (activeCommentTarget === null) {
112 │ setPendingNativeCommentSelection(null);
· ────────────────┬───────────────
· ╰── Avoid calling setState() directly within an effect
113 │ }
╰────
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/review/useReviewCommentSelectionController.ts:108:7]
107 │ setPendingNativeCommentSelection(null);
108 │ }, [selectedSection?.id]);
· ─────────┬─────────
· ╰── Unnecessary dependency `selectedSection?.id`
109 │
╰────
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/files/SourceFileSurface.tsx:257:7]
256 │ return () => cancelAnimationFrame(frame);
257 │ }, [props.path, targetIndex]);
· ─────┬────
· ╰── Unnecessary dependency `props.path`
258 │
╰────
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(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:293:23]
292 │ <SourceText
293 │ key={`${index}:${tokenIndex}`}
· ──────────────────────────────
294 │ style={{
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:309:27]
308 │ return (
309 │ <SourceText key={index}>
· ───────────
310 │ {body}
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/review/useNativeReviewDiffHighlighting.ts:60:5]
55 │
56 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
57 │ scheduler.reset();
58 │ highlightedRowIdsRef.current = new Set();
59 │ visibleChunkIndexRef.current = 0;
60 │ setVisibleRange({ firstRowIndex: 0, lastRowIndex: 80 });
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
61 │ setTokensPatchJson(createEmptyTokenPatch(resetKey));
╰────
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/review/useNativeReviewDiffHighlighting.ts:63:7]
62 │ return () => scheduler.cancel();
63 │ }, [enabled, resetKey, rows.length, scheduler]);
· ───┬─── ─────┬─────
· │ ╰── Unnecessary dependency `rows.length`
· ╰── Unnecessary dependency `enabled`
64 │
╰────
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(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:138:28]
137 │ visit(parser.parse(markdown));
138 │ for (const edit of edits.reverse())
· ───────
139 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:169:28]
168 │ visit(parser.parse(markdown));
169 │ for (const edit of edits.reverse())
· ───────
170 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:223:38]
222 │ visit(parser.parse(markdown));
223 │ for (const lineStart of lineStarts.reverse()) {
· ───────
224 │ // The header row may be a lazy line without its container markers (`>` or list indent),
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:79:5]
76 │
77 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
78 │ const { host, code } = parsePairingUrl(connectionPairingUrl);
79 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
80 │ setCodeInput(code);
╰────
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/connection/ConnectionsNewRouteScreen.tsx:89:5]
82 │
83 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
84 │ if (routePairingUrl.length === 0) {
85 │ return;
86 │ }
87 │
88 │ const { host, code } = parsePairingUrl(routePairingUrl);
89 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
90 │ setCodeInput(code);
╰────
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/connection/ConnectionsNewRouteScreen.tsx:95:7]
92 │
93 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
94 │ if (pairingConnectionError) {
95 │ setIsSubmitting(false);
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
96 │ }
╰────
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(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(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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:262:5]
260 │ .join("|");
261 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
262 │ stop();
· ──┬─
· ╰── Avoid calling setState() directly within an effect
263 │ }, [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(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:250:9]
249 │ const latest = useRef({ rows, planners, moveThread });
250 │ latest.current = { rows, planners, moveThread };
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
251 │
╰────
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:248:22]
247 │ const [preview, setPreview] = useState<Drag | null>(null);
248 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
249 │ 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(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:248:22]
247 │ const [preview, setPreview] = useState<Drag | null>(null);
248 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
249 │ 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(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:248:22]
247 │ const [preview, setPreview] = useState<Drag | null>(null);
248 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
249 │ 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(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:248:22]
247 │ const [preview, setPreview] = useState<Drag | null>(null);
248 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
249 │ 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(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:262:5]
261 │ useEffect(() => {
262 │ stop();
· ──┬─
· ╰── Missing dependency `stop`
263 │ }, [orderVersion]);
· ──────┬─────
· ╰── Unnecessary dependency `orderVersion`
264 │ 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(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:325:16]
324 │ update(0);
325 │ let last = performance.now();
· ────────┬────────
· ╰── Cannot call impure function
326 │ 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(immutability): This value cannot be modified
╭─[apps/mobile/src/features/connection/ConnectionStatusDot.tsx:58:7]
53 │ function usePulseAnimation(pulse: boolean) {
54 │ const pulseProgress = useSharedValue(0);
· ──────┬──────
· ╰── `pulseProgress` originates here
55 │
56 │ useEffect(() => {
57 │ if (pulse) {
58 │ pulseProgress.value = withRepeat(
· ──────┬──────
· ╰── `pulseProgress` cannot be modified
59 │ withTiming(1, {
╰────
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/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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:84:5]
79 │
80 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
81 │ if (!needsPreparation || !initialProjectRef.branch || waitingForProject) return;
82 │ const branchName = initialProjectRef.branch;
83 │ let active = true;
84 │ setPendingCheckouts((count) => count + 1);
· ─────────┬─────────
· ╰── Avoid calling setState() directly within an effect
85 │ // 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
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:289:50]
288 │ return (
289 │ <ExistingThreadSettingsRouteContext.Provider value={value}>
· ─────────────
290 │ {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:653:44]
652 │ return (
653 │ <ThreadSettingsSessionContext.Provider value={value}>
· ─────────────
654 │ {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:1456:55]
1455 │ return (
1456 │ <ThreadSettingsPickerPresentationContext.Provider value={presentation}>
· ────────────────────
1457 │ <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.
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:282:7]
281 │ mountedRef.current = false;
282 │ flow.setBranchQuery("");
· ──┬─
· ╰── Missing dependency `flow`
283 │ };
284 │ }, [flow.setBranchQuery]);
· ─────────┬─────────
· ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
285 │
╰────
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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:487:5]
485 │ }, []);
486 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
487 │ setKeyboardStateSuspect(false);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
488 │ }, [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:838:7]
835 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
836 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
837 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
838 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
· ─────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
839 │ }
╰────
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:1081:5]
1077 │
1078 │ useLayoutEffect(() => {
· ───────┬───────
· ╰── This is the containing effect
1079 │ selectedThreadKeyRef.current = selectedThreadKey;
1080 │ // A replaced or unmounted native editor may not emit a blur event.
1081 │ setComposerFocused(false);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1082 │ }, [selectedThreadKey, showContent]);
╰────
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:1085:5]
1083 │
1084 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1085 │ setAnchorMessageId(null);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1086 │ 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:488:7]
487 │ setKeyboardStateSuspect(false);
488 │ }, [isKeyboardVisible, liveKeyboardHeight]);
· ────────┬──────── ─────────┬────────
· │ ╰── Unnecessary dependency `liveKeyboardHeight`
· ╰── Unnecessary dependency `isKeyboardVisible`
489 │ 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:1031:7]
1030 │ userInputInsetProgress.set(1);
1031 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
· ────────────┬───────────
· ╰── Unnecessary dependency `activeUserInputRequestId`
1032 │ 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:1082:26]
1081 │ setComposerFocused(false);
1082 │ }, [selectedThreadKey, showContent]);
· ─────┬─────
· ╰── Unnecessary dependency `showContent`
1083 │
╰────
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:1091:15]
1090 │ freeze.set(false);
1091 │ }, [freeze, selectedThreadKey]);
· ────────┬────────
· ╰── Unnecessary dependency `selectedThreadKey`
1092 │
╰────
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:919:5]
914 │ const composerPopoverHeight = useSharedValue(0);
915 │ const floatingControlCoverage = useSharedValue(
· ───────────┬───────────
· ╰── `floatingControlCoverage` originates here
916 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
917 │ );
918 │ useEffect(() => {
919 │ floatingControlCoverage.value = withTiming(
· ───────────┬───────────
· ╰── `floatingControlCoverage` cannot be modified
920 │ 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:937:7]
927 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
928 │ const combinedContentInsetEndAdjustment = useSharedValue(
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` originates here
929 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
930 │ );
931 │ useAnimatedReaction(
932 │ () =>
933 │ contentInsetEndAdjustment.value +
934 │ floatingControlCoverage.value +
935 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
936 │ (value) => {
937 │ combinedContentInsetEndAdjustment.value = value;
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` cannot be modified
938 │ },
╰────
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/ThreadNavigationSidebar.tsx:282:5]
280 │ const [snoozeWakeTick, bumpSnoozeWakeTick] = useState(0);
281 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
282 │ setNow(new Date().toISOString());
· ───┬──
· ╰── Avoid calling setState() directly within an effect
283 │ 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
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:362:25]
361 │ // range) the boundary string is identical and the chain would die.
362 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
· ───────┬──────
· ╰── Unnecessary dependency `snoozeWakeTick`
363 │ 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:353:53]
352 │ if (Number.isNaN(wakeAtMs)) return;
353 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
· ─────┬────
· ╰── Cannot call impure function
354 │ 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
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[apps/mobile/src/state/use-model-option-memory.ts:21:7]
20 │ [instanceId]: {
21 │ ...(state[instanceId] ?? {}),
· ────────────────────────────
22 │ [model]: options,
╰────
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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/thread-inspector-content-stack.tsx:57:5]
55 │
56 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
57 │ setMountedModes((current) => {
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
58 │ 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
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/state/use-thread-outbox-drain.ts:1315:5]
1314 │ queuedMessagesByThreadKey,
1315 │ retryTick,
· ────┬────
· ╰── Unnecessary dependency `retryTick`
1316 │ restoreQueuedMessage,
╰────
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/state/thread-order.ts:29:7]
28 │ getPendingThreadOrder();
29 │ }, [nowMinute, snoozeWakeTick]);
· ────┬──── ───────┬──────
· │ ╰── Unnecessary dependency `snoozeWakeTick`
· ╰── Unnecessary dependency `nowMinute`
30 │ return pending;
╰────
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:590:9]
589 │ };
590 │ }, [props.environmentId, attachment.id, httpBaseUrl]),
· ─────────┬───────── ──────┬────── ─────┬─────
· │ │ ╰── Unnecessary dependency `httpBaseUrl`
· │ ╰── Unnecessary dependency `attachment.id`
· ╰── Unnecessary dependency `props.environmentId`
591 │ );
╰────
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/ThreadFeed.tsx:1845:5]
1843 │ );
1844 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1845 │ setExpandedVideo(null);
· ────────┬───────
· ╰── Avoid calling setState() directly within an effect
1846 │ 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
⚠ eslint(no-unused-vars): Identifier 'isMarkdownFileLinkLabel' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:64:10]
63 │ import { resolveAssetUrl } from "@t3tools/client-runtime/state/assets";
64 │ import { isMarkdownFileLinkLabel } from "@t3tools/shared/markdownLinks";
· ───────────┬───────────
· ╰── 'isMarkdownFileLinkLabel' is imported here
65 │ 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:90:3]
89 │ import {
90 │ createContext,
· ──────┬──────
· ╰── 'createContext' is imported here
91 │ memo,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:104:3]
103 │ import {
104 │ ActivityIndicator,
· ────────┬────────
· ╰── 'ActivityIndicator' is imported here
105 │ Image,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ScrollView' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:111:3]
110 │ Pressable,
111 │ ScrollView,
· ─────┬────
· ╰── 'ScrollView' is imported here
112 │ StyleSheet,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'NativeText' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:113:11]
112 │ StyleSheet,
113 │ Text as NativeText,
· ─────┬────
· ╰── 'NativeText' is imported here
114 │ 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:135:10]
134 │ import { copyTextWithHaptic } from "../../lib/copyTextWithHaptic";
135 │ import { tryOpenExternalUrl } from "../../lib/openExternalUrl";
· ─────────┬────────
· ╰── 'tryOpenExternalUrl' is imported here
136 │ 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:138:10]
137 │ import { hasWideMarkdownBlock } from "../../lib/wideMarkdownBlocks";
138 │ import { faviconUrlForOrigin } from "@t3tools/shared/favicon";
· ─────────┬─────────
· ╰── 'faviconUrlForOrigin' is imported here
139 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'MediaVideoPlayer' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:152:10]
151 │ import { VideoAttachmentTile } from "../../components/VideoAttachmentTile";
152 │ import { MediaVideoPlayer } from "../../components/MediaVideoPlayer";
· ────────┬───────
· ╰── 'MediaVideoPlayer' is imported here
153 │ 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:156:3]
155 │ attachmentVideoPreviewSource,
156 │ mediaVideoPreviewUri,
· ──────────┬─────────
· ╰── 'mediaVideoPreviewUri' is imported here
157 │ mediaVideoThumbnailKey,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'mediaVideoThumbnailKey' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:157:3]
156 │ mediaVideoPreviewUri,
157 │ mediaVideoThumbnailKey,
· ───────────┬──────────
· ╰── 'mediaVideoThumbnailKey' is imported here
158 │ 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:158:8]
157 │ mediaVideoThumbnailKey,
158 │ type MediaVideoPreviewSource,
· ───────────┬───────────
· ╰── 'MediaVideoPreviewSource' is imported here
159 │ } 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:166:15]
165 │ import { parseReviewCommentMessageSegments } from "../review/reviewCommentSelection";
166 │ import type { ReviewDiffTheme } from "../review/shikiReviewHighlighter";
· ───────┬───────
· ╰── 'ReviewDiffTheme' is imported here
167 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownFontSizes' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:181:3]
180 │ import {
181 │ resolveMarkdownFontSizes,
· ────────────┬───────────
· ╰── 'resolveMarkdownFontSizes' is imported here
182 │ resolveNativeMarkdownTypography,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'markdownLinkIconSource' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:186:10]
185 │ import { PierreEntryIcon } from "../../components/PierreEntryIcon";
186 │ import { markdownLinkIconSource } from "../../lib/markdownLinkIcons";
· ───────────┬──────────
· ╰── 'markdownLinkIconSource' is imported here
187 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownInlineCodePresentation' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:189:3]
188 │ normalizeNativeMarkdownUrl,
189 │ resolveMarkdownInlineCodePresentation,
· ──────────────────┬──────────────────
· ╰── 'resolveMarkdownInlineCodePresentation' is imported here
190 │ resolveMarkdownLinkIcon,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownLinkIcon' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:190:3]
189 │ resolveMarkdownInlineCodePresentation,
190 │ resolveMarkdownLinkIcon,
· ───────────┬───────────
· ╰── 'resolveMarkdownLinkIcon' is imported here
191 │ resolveMarkdownLinkPresentation,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useMarkdownCodeHighlight' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:225:10]
224 │ import { ThreadMcpApp } from "./McpAppWebView";
225 │ import { useMarkdownCodeHighlight } from "./markdownCodeHighlightState";
· ────────────┬───────────
· ╰── 'useMarkdownCodeHighlight' is imported here
226 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useAssetUrlState' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:229:3]
228 │ useAssetUrl,
229 │ useAssetUrlState,
· ────────┬───────
· ╰── 'useAssetUrlState' is imported here
230 │ useRefreshAssetUrl,
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:1847:7]
1846 │ setExpandedFile(null);
1847 │ }, [props.environmentId, props.threadId, props.contentPresentation.kind]);
· ─────────┬───────── ───────┬────── ───────────────┬──────────────
· │ │ ╰── Unnecessary dependency `props.contentPresentation.kind`
· │ ╰── Unnecessary dependency `props.threadId`
· ╰── Unnecessary dependency `props.environmentId`
1848 │ 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:2302:30]
2301 │ transitionEndFollow({ type: "reset" });
2302 │ }, [clearUserScrollSettle, feedThreadKey, transitionEndFollow]);
· ──────┬──────
· ╰── Unnecessary dependency `feedThreadKey`
2303 │ useEffect(() => {
╰────
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:2320:7]
2319 │ reportHeaderMaterialVisibility(false);
2320 │ }, [feedThreadKey, reportHeaderMaterialVisibility]);
· ──────┬──────
· ╰── Unnecessary dependency `feedThreadKey`
2321 │
╰────
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:2352:7]
2351 │ }
2352 │ }, [listMountKey, props.contentInsetEndAdjustment, listRef]);
· ──────┬─────
· ╰── Unnecessary dependency `listMountKey`
2353 │
╰────
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:2447:7]
2446 │ }
2447 │ }, [expandedTurnIds, expandedWorkGroups, expandedWorkRows, settleDisclosureAfterLayout]);
· ───────┬─────── ─────────┬──────── ────────┬───────
· │ │ ╰── Unnecessary dependency `expandedWorkRows`
· │ ╰── Unnecessary dependency `expandedWorkGroups`
· ╰── Unnecessary dependency `expandedTurnIds`
2448 │
╰────
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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:431:5]
426 │ : null;
427 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
428 │ if (activeDraftKey !== null || editingPendingTask !== null || selectedProject === null) {
429 │ return;
430 │ }
431 │ setActiveDraftKey(
· ────────┬────────
· ╰── Avoid calling setState() directly within an effect
432 │ 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:1212:39]
1211 │
1212 │ return <NewTaskFlowContext.Provider value={value}>{props.children}</NewTaskFlowContext.Provider>;
· ─────────────
1213 │ }
╰────
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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:388:5]
386 │
387 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
388 │ setInspectorSelection((current) => {
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
389 │ 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:516:24]
515 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
516 │ ╭─▶ const GitInspector = () => (
517 │ │ <GitOverviewSheet
518 │ │ headerInset={inspectorHeaderInset}
519 │ │ presentation="inspector"
520 │ │ route={{ params: props.route.params }}
521 │ │ />
522 │ ╰─▶ );
523 │ 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:523:26]
522 │ );
523 │ ╭─▶ const FilesInspector = () =>
524 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
525 │ │ <ThreadFileNavigatorPane
526 │ │ cwd={selectedThreadCwd}
527 │ │ environmentId={selectedThread.environmentId}
528 │ │ headerInset={inspectorHeaderInset}
529 │ │ projectName={selectedThreadProject?.title ?? "Files"}
530 │ │ selectedPath={null}
531 │ │ onSelectFile={handleSelectInspectorFile}
532 │ │ />
533 │ ╰─▶ ) : null;
534 │ 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/NewTaskDraftScreen.tsx:552:7]
546 │ }, [cancelledIncomingShareId, navigation, props.incomingShareId]);
547 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
548 │ if (!isReturningToProjectPicker) {
549 │ return;
550 │ }
551 │ if (requestedInitialProjectAvailable) {
552 │ setIsReturningToProjectPicker(false);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
553 │ 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:700:9]
643 │
644 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
645 │ if (props.pendingTaskId || props.draftId) {
646 │ return;
647 │ }
648 │ if (lastInitialProjectRefRef.current !== props.initialProjectRef) {
649 │ lastInitialProjectRefRef.current = props.initialProjectRef;
650 │ appliedInitialProjectKeyRef.current = null;
651 │ }
652 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
653 │ const initialProjectId = props.initialProjectRef?.projectId;
654 │ if (initialEnvironmentId && initialProjectId) {
655 │ const directProject =
656 │ projects.find(
657 │ (project) =>
658 │ project.environmentId === initialEnvironmentId && project.id === initialProjectId,
659 │ ) ?? null;
660 │
661 │ if (directProject) {
662 │ // Apply the route's project once. Re-applying on every change would
663 │ // instantly revert environment/project switches made in the picker.
664 │ const directProjectKey = `${directProject.environmentId}:${directProject.id}`;
665 │ if (appliedInitialProjectKeyRef.current === directProjectKey) {
666 │ return;
667 │ }
668 │ if (props.initialProjectRef?.branch) {
669 │ if (
670 │ selectedProject?.environmentId !== directProject.environmentId ||
671 │ selectedProject.id !== directProject.id
672 │ ) {
673 │ setProject(directProject);
674 │ return;
675 │ }
676 │ if (!flow.draftKey) return;
677 │ // The route completes checkout before mounting this composer. Local
678 │ // mode reuses an existing worktree; worktree mode would create another.
679 │ updateComposerDraftSettings(flow.draftKey, {
680 │ workspaceSelection: {
681 │ mode: "local",
682 │ branch: props.initialProjectRef.branch,
683 │ worktreePath: props.initialProjectRef.worktreePath ?? null,
684 │ startFromOrigin: false,
685 │ },
686 │ });
687 │ }
688 │ appliedInitialProjectKeyRef.current = directProjectKey;
689 │ if (
690 │ selectedProject?.environmentId === directProject.environmentId &&
691 │ selectedProject.id === directProject.id
692 │ ) {
693 │ return;
694 │ }
695 │ setProject(directProject);
696 │ return;
697 │ }
698 │
699 │ if (projects.length > 0) {
700 │ setIsReturningToProjectPicker(true);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
701 │ }
╰────
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:800:5]
741 │
742 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
743 │ const shareId = props.incomingShareId;
744 │ const draftKey = flow.draftKey;
745 │ const destinationProject = selectedProject;
746 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
747 │ const initialProjectId = props.initialProjectRef?.projectId;
748 │ const selectedProjectMatchesRoute =
749 │ !initialEnvironmentId ||
750 │ !initialProjectId ||
751 │ (destinationProject?.environmentId === initialEnvironmentId &&
752 │ destinationProject.id === initialProjectId);
753 │ if (
754 │ !shareId ||
755 │ !draftKey ||
756 │ !destinationProject ||
757 │ !selectedProjectMatchesRoute ||
758 │ cancelledIncomingShareId === shareId
759 │ ) {
760 │ return;
761 │ }
762 │ const importKey = `${shareId}:${draftKey}`;
763 │ if (
764 │ startedShareImportKeyRef.current === importKey ||
765 │ cancellingShareImportKeyRef.current === importKey
766 │ ) {
767 │ return;
768 │ }
769 │
770 │ if (!incomingShare) {
771 │ if (isIncomingShareUnavailable && alertedUnavailableIncomingShareIdRef.current !== shareId) {
772 │ alertedUnavailableIncomingShareIdRef.current = shareId;
773 │ Dialog.alert(
774 │ "Shared content unavailable",
775 │ "The shared content is no longer in the inbox. You can continue editing this task draft.",
776 │ );
777 │ }
778 │ return;
779 │ }
780 │
781 │ if (
782 │ incomingShare.attachments.some((attachment) => attachment.type === "file") &&
783 │ selectedEnvironmentServerConfig === null
784 │ ) {
785 │ return;
786 │ }
787 │
788 │ if (alertedUnavailableIncomingShareIdRef.current === shareId) {
789 │ alertedUnavailableIncomingShareIdRef.current = null;
790 │ }
791 │ startedShareImportKeyRef.current = importKey;
792 │ const draftBackup =
793 │ shareImportDraftBackupRef.current.get(importKey) ?? getComposerDraftSnapshot(draftKey);
794 │ shareImportDraftBackupRef.current.set(importKey, draftBackup);
795 │ const importToken = Symbol(importKey);
796 │ let didReserveShare = false;
797 │ let didConsumeShare = false;
798 │ let needsDraftRestore = false;
799 │ activeShareImportTokenRef.current = importToken;
800 │ setImportingShareKey(importKey);
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
801 │ 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:720:5]
719 │ props.initialProjectRef,
720 │ props.incomingShareId,
· ──────────┬──────────
· ╰── Unnecessary dependency `props.incomingShareId`
721 │ 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:739:5]
738 │ loadedBranchesProjectKeyRef.current = projectKey;
739 │ flow.loadBranches();
· ──┬─
· ╰── Missing dependency `flow`
740 │ }, [flow.loadBranches, selectedProject]);
· ────────┬────────
· ╰── Overly precise dependency `flow.loadBranches`, use `flow` instead
741 │
╰────
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:962:5]
961 │ flow.draftKey,
962 │ hasImportedIncomingShare,
· ────────────┬───────────
· ╰── Unnecessary dependency `hasImportedIncomingShare`
963 │ incomingShare,
964 │ isIncomingShareInboxLoading,
· ─────────────┬─────────────
· ╰── Unnecessary dependency `isIncomingShareInboxLoading`
965 │ isIncomingShareUnavailable,
966 │ props.incomingShareId,
967 │ props.initialProjectRef?.environmentId,
968 │ props.initialProjectRef?.projectId,
969 │ releaseShareReservation,
970 │ reserveShare,
971 │ selectedEnvironmentServerConfig,
972 │ selectedProject,
973 │ shareImportAttempt,
· ─────────┬────────
· ╰── Unnecessary dependency `shareImportAttempt`
974 │ ]);
╰────
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
Found 0 errors and 361 warnings in 5241 files (6.9s, 8 threads)
Post job cleanup.
##[start-action display=Cache full pnpm store;id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__actions_cache_2]
Post job cleanup.
Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-68ecfee7dce3960a4e095879378684d06946a297346201d9bd411a74fc6057ea, not saving cache.
##[end-action id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__actions_cache_2;outcome=success;conclusion=success;duration_ms=107]
##[start-action display=Setup Vite+;id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__voidzero-dev_setup-vp]
Post job cleanup.
##[end-action id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__voidzero-dev_setup-vp;outcome=success;conclusion=success;duration_ms=68]
##[start-action display=Cache Vite+;id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__actions_cache]
Post job cleanup.
Cache hit occurred on the primary key vite-plus-home-v1-Linux-X64-1.0.0, not saving cache.
##[end-action id=__dc76fdd1-1c51-4e2a-ac43-f2397a4cd527.__actions_cache;outcome=success;conclusion=success;duration_ms=66]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/f14e02d3-3a85-4f03-9b07-a6140fd406b1' 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: 149
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 422
BLACKSMITH_CHECK_RUN_ID: 119018884336
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