GitHub check
256 KB of 594 KB loaded Download the full log (594 KB)
338 KB of earlier output not loaded
01:51:03.5952381Z 616 │ navigation.navigate("Thread", {
617 │ environmentId: String(environmentId),
618 │ threadId: String(threadId),
619 │ });
620 │ };
621 │ const androidHeaderSubtitle = [
622 │ selectedSection?.title,
623 │ headerDiffSummary.additions,
624 │ headerDiffSummary.deletions,
625 │ ]
626 │ .filter((part): part is string => Boolean(part))
627 │ .join(" · ");
628 │
629 │ const showChangedFilesPane =
630 │ !showConnectionNotice &&
631 │ selectedSection !== null &&
632 │ parsedDiff.kind === "files" &&
633 │ NativeReviewDiffView !== null;
634 │ useRegisterWorkspaceInspector(showChangedFilesPane ? renderInspector : undefined);
635 │ const showChangedFilesToggle = panes.supportsAuxiliaryPane && showChangedFilesPane;
636 │
637 │ const listHeader = (() => {
638 │ const children: ReactElement[] = [];
639 │
640 │ if (error) {
641 │ children.push(
642 │ <View
643 │ key="review-error"
644 │ className={cn(
645 │ "bg-card px-4 py-3",
646 │ Platform.OS === "android" ? "m-2 rounded-[20px]" : "border-b border-border",
647 │ )}
648 │ >
649 │ <Text className="text-sm font-t3-bold text-foreground">Review unavailable</Text>
650 │ <Text className="text-xs leading-normal text-foreground-muted">{error}</Text>
651 │ </View>,
652 │ );
653 │ }
654 │
655 │ if (parsedDiffNotice) {
656 │ children.push(<ReviewNotice key="review-notice" notice={parsedDiffNotice} />);
657 │ }
658 │
659 │ if (children.length === 0) {
660 │ return null;
661 │ }
662 │
663 │ return <>{children}</>;
664 │ })();
665 │ const headerSubtitle = [
666 │ headerDiffSummary.additions,
667 │ headerDiffSummary.deletions,
668 │ pendingReviewCommentCount > 0
669 │ ? `${pendingReviewCommentCount} comment${pendingReviewCommentCount === 1 ? "" : "s"}`
670 │ : null,
671 │ ]
672 │ .filter(Boolean)
673 │ .join(" · ");
674 │ const headerTitleText = selectedSection?.title ?? "Review changes";
675 │
676 │ return (
677 │ <>
678 │ <ReviewHeader
679 │ environmentId={environmentId}
680 │ threadId={threadId}
681 │ title={headerTitleText}
682 │ subtitle={headerSubtitle}
683 │ androidSubtitle={androidHeaderSubtitle}
684 │ iconColor={headerIcon}
685 │ selectedThreadCwd={selectedThreadCwd}
686 │ sectionMenu={sectionMenu}
687 │ selectedSection={selectedSection}
688 │ showSectionToolbar={showSectionToolbar}
689 │ showChangedFilesToggle={showChangedFilesToggle}
690 │ onRefresh={handlePullToRefresh}
691 │ onSelectSection={selectSection}
692 │ onReturnToThread={handleReturnToThread}
693 │ />
694 │
695 │ <ScreenContent>
696 │ <View className="flex-1 bg-sheet android:bg-sheet-solid">
697 │ {showConnectionNotice ? (
698 │ <View className="flex-1" style={{ paddingTop: topContentInset }}>
699 │ <EnvironmentConnectionNotice
700 │ environmentLabel={environment.presentation?.entry.target.label ?? "Environment"}
701 │ connection={
702 │ environment.presentation?.connection ?? {
703 │ phase: "available",
704 │ error: null,
705 │ traceId: null,
706 │ }
707 │ }
708 │ resourceName="review"
709 │ onRetry={handleRetryEnvironment}
710 │ />
711 │ </View>
712 │ ) : selectedSection && parsedDiff.kind === "files" && NativeReviewDiffView ? (
713 │ <View
714 │ className="flex-1"
715 │ style={{
716 │ backgroundColor: nativeBridge.theme.background,
717 │ }}
718 │ >
719 │ <View
720 │ className="min-w-0 flex-1"
721 │ style={listHeader ? { paddingTop: topContentInset } : undefined}
722 │ >
723 │ {listHeader}
724 │ <View className="min-w-0 flex-1" collapsable={false}>
725 │ <NativeReviewDiffView
· ──────────┬─────────
· ╰── This component is created during render
726 │ 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(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
⚠ 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(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(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/threads/ThreadArrangementSheet.tsx:261:5]
259 │ .join("|");
260 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
261 │ stop();
· ──┬─
· ╰── Avoid calling setState() directly within an effect
262 │ }, [orderVersion]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
260 │ useEffect(() => {
261 │ stop();
· ──┬─
· ╰── Missing dependency `stop`
262 │ }, [orderVersion]);
· ──────┬─────
· ╰── Unnecessary dependency `orderVersion`
263 │ useEffect(
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:96:9]
95 │ const latest = useRef(props);
96 │ latest.current = props;
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
97 │ const gesture = useMemo(
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:104:18]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───────────────┬──────────────
· ╰── Passing a ref to a function may read its value during render
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:105:19]
104 │ .onStart(() => latest.current.onStart())
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:106:16]
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:107:21]
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
· ───────────────────────┬──────────────────────
· ╰── Passing a ref to a function may read its value during render
108 │ [props.disabled],
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:249:9]
248 │ const latest = useRef({ rows, planners, moveThread });
249 │ latest.current = { rows, planners, moveThread };
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
250 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:247:22]
246 │ const [preview, setPreview] = useState<Drag | null>(null);
247 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
248 │ const latest = useRef({ rows, planners, moveThread });
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:324:16]
323 │ update(0);
324 │ let last = performance.now();
· ────────┬────────
· ╰── Cannot call impure function
325 │ const tick = () => {
╰────
help: `performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:99:15]
98 │ () =>
99 │ Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
100 │ .enabled(!props.disabled)
╰────
help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(memo-dependencies): Found missing memoization dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:108:5]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───┬──
· ╰── Missing dependency `latest`. Refs, setState functions, and other "stable" values generally do not need to be added as dependencies, but this variable may change over time to point to different values
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
108 │ [props.disabled],
· ────────┬───────
· ╰── This dependency list is missing values used by the callback
109 │ );
╰────
help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx:814:17]
813 │ <div
814 │ key={`${index}:${check.name}:${check.url ?? ""}`}
· ─────────────────────────────────────────────────
815 │ className="group flex items-center gap-2 rounded-md pr-1 hover:bg-accent/60"
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ eslint(no-unused-vars): Identifier 'Image' is imported but never used.
╭─[apps/mobile/src/native/T3ComposerEditor.native.tsx:17:10]
16 │ import type { NativeSyntheticEvent, ViewProps } from "react-native";
17 │ import { Image, Platform, StyleSheet } from "react-native";
· ──┬──
· ╰── 'Image' is imported here
18 │
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found missing effect dependencies
╭─[apps/mobile/src/native/T3ComposerEditor.native.tsx:227:6]
223 │ nativeEventSnapshotsRef.current = pruneAcknowledgedComposerNativeEvents(
224 │ 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
225 │ mostRecentEventCount,
226 │ );
227 │ }, [acknowledgesLatestNativeEvent, mostRecentEventCount]);
· ──────────────────────────┬──────────────────────────
· ╰── This dependency list is missing values used by the callback
228 │ 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.native.tsx:235:7]
234 │ nativeEventSnapshotsRef.current = assumeComposerControlledState(
235 │ 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
236 │ controlledEventCount,
237 │ assumedValue,
238 │ );
239 │ }, [assumedValue, controlledEventCount, isNativeEcho, controlledDocumentJson]);
· ───────────┬──────────
· ╰── Unnecessary dependency `controlledDocumentJson`
240 │ 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
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/native/T3ComposerEditor.native.tsx:160:29]
159 │ const tokens = collectComposerInlineTokens(props.value, {
160 │ preserveTrailingFrom: confirmedTokensRef.current,
· ─────────────┬────────────
· ╰── Cannot access ref value during render
161 │ });
╰────
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.native.tsx:160:29]
159 │ const tokens = collectComposerInlineTokens(props.value, {
160 │ preserveTrailingFrom: confirmedTokensRef.current,
· ─────────────┬────────────
· ╰── Passing a ref to a function may read its value during render
161 │ });
╰────
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.native.tsx:162:23]
161 │ });
162 │ confirmedTokensRef.current = tokens;
· ─────────┬────────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
163 │ 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.native.tsx:204:5]
203 │ mostRecentEventCount,
204 │ nativeEventSnapshotsRef.current,
· ───────────────┬───────────────
· ╰── Passing a ref to a function may read its value during render
205 │ );
╰────
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.native.tsx:210:5]
209 │ mostRecentEventCount,
210 │ nativeEventSnapshotsRef.current,
· ───────────────┬───────────────
· ╰── Passing a ref to a function may read its value during render
211 │ );
╰────
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.native.tsx:195:6]
159 │ const tokens = collectComposerInlineTokens(props.value, {
160 │ 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
161 │ });
162 │ confirmedTokensRef.current = tokens;
163 │ return JSON.stringify(
164 │ composerContextEditorTokens(props.value, tokens, skillLabels).map((token) => {
165 │ const record =
166 │ token.type === "context"
167 │ ? props.context?.records.find((record) => record.contextId === token.contextId)
168 │ : undefined;
169 │ const presentation = contextChipPresentation(
170 │ token.type === "context" ? token.kind : token.type,
171 │ record,
172 │ );
173 │ const icon = contextChipIcon(
174 │ presentation,
175 │ token.type === "mention" ? token.value : contextRecordFileName(record),
176 │ );
177 │ return {
178 │ type: token.type,
179 │ source: token.source,
180 │ start: token.start,
181 │ end: token.end,
182 │ accent: presentation.accent,
183 │ label:
184 │ token.type === "skill"
185 │ ? (skillLabels.get(token.value) ?? token.value)
186 │ : token.type === "context"
187 │ ? `${token.label}${props.context?.records.some((record) => record.contextId === token.contextId) ? "" : " · unavailable"}`
188 │ : basename(token.value),
189 │ detail: token.type === "context" ? composerChipSizeSuffix(record) : "",
190 │ iconUri: contextChipIconUri(icon),
191 │ tintsIcon: icon.kind === "chip",
192 │ };
193 │ }),
194 │ );
195 │ }, [props.value, props.context, skillLabels]);
· ────────────────────┬────────────────────
· ╰── This dependency list is missing values used by the callback
196 │ // 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.native.tsx:257:5]
249 │ mostRecentEventCountRef.current = acknowledgedEventCount;
250 │ 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
251 │ eventCount: acknowledgedEventCount,
252 │ value,
253 │ selection: nextSelection,
254 │ });
255 │ return acknowledgedEventCount;
256 │ },
257 │ [],
· ─┬
· ╰── This dependency list is missing values used by the callback
258 │ );
╰────
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/components/MediaVideoPlayer.tsx:60:5]
57 │
58 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
59 │ const controller = new AbortController();
60 │ setLoadState("pending");
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
61 │ // A renewed signature is used on Retry, not as a reason to reset the native player.
╰────
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/MediaVideoPlayer.tsx:71:7]
70 │ return () => controller.abort();
71 │ }, [player, props.playRequested, attempt]);
· ───┬── ─────────┬───────── ───┬───
· │ │ ╰── Unnecessary dependency `attempt`
· │ ╰── Unnecessary dependency `props.playRequested`
· ╰── Unnecessary dependency `player_0`
72 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ unicorn(prefer-set-has): should be a `Set`, and use `.has()` to check existence or non-existence.
╭─[apps/web/src/components/pullRequest/pullRequestList.logic.ts:187:9]
186 │ ): boolean {
187 │ const labels = entry.labels.map((label) => label.name.trim().toLowerCase());
· ─────────────────────────────────────────────────────────────────────
188 │ const holds = (label: string) => labels.includes(label.trim().toLowerCase());
╰────
help: Switch to `Set`
⚠ eslint(no-unused-vars): Variable 'layerDaemon' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/EffectWorker.ts:911:7]
910 │
911 │ const layerDaemon: Layer.Layer<never, never, OrchestrationEffectWorkerV2> = Layer.effectDiscard(
· ─────┬─────
· ╰── 'layerDaemon' is declared here
912 │ runDaemon.pipe(Effect.forkScoped),
╰────
help: Consider removing this declaration.
⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
╭─[apps/web/src/components/pullRequest/PullRequestListFilters.tsx:387:19]
386 │ onFilters,
387 │ authorOptions = [],
· ──
388 │ labelOptions = [],
╰────
help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
╭─[apps/web/src/components/pullRequest/PullRequestListFilters.tsx:388:18]
387 │ authorOptions = [],
388 │ labelOptions = [],
· ──
389 │ host,
╰────
help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
⚠ 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
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ThreadPullRequestService.ts:408:7]
407 │
408 │ const layer = Layer.effect(ThreadPullRequestServiceV2, make);
· ──┬──
· ╰── 'layer' is declared here
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'layerFromProviderAdapter' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderAdapterRegistry.ts:346:7]
345 │
346 │ const layerFromProviderAdapter: Layer.Layer<
· ────────────┬───────────
· ╰── 'layerFromProviderAdapter' is declared here
347 │ ProviderAdapterRegistryV2,
╰────
help: Consider removing this declaration.
⚠ eslint(no-unsafe-optional-chaining): Unsafe usage of optional chaining
╭─[apps/server/src/orchestration-v2/ThreadLaunchService.test.ts:1783:8]
1782 │ assert.equal(
1783 │ (stored.context?.records[0] as { attachmentId: string }).attachmentId,
· ──────────────────────────
1784 │ stored.attachments[0]?.id,
╰────
help: If this short-circuits with 'undefined' the evaluation will throw TypeError
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/components/VideoPreviewModal.ios.tsx:63:55]
61 │ }, []);
62 │ useEffect(() => {
· ────┬────
· ╰── 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(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/components/ComposerEditor.tsx:82:6]
81 │ },
82 │ [draftKey],
· ────┬───
· ╰── Unnecessary dependency `draftKey`
83 │ );
╰────
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
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:566:7]
565 │ let afterSequence = created[0]!.sequence;
566 │ ╭─▶ for (let index = 1; index <= 32; index += 1) {
567 │ │ const nextEvent = {
568 │ │ id: EventId.make(`event:foundation-stream-race:${index}`),
569 │ │ type: "thread.metadata-updated" as const,
570 │ │ threadId,
571 │ │ providerInstanceId,
572 │ │ occurredAt: now,
573 │ │ payload: { ...thread, title: `Race update ${index}` },
574 │ │ } satisfies OrchestrationV2DomainEvent;
575 │ │ const reader = yield* eventSink
576 │ │ .stream({ threadId, afterSequence })
577 │ │ .pipe(Stream.runHead, Effect.forkChild);
578 │ │ yield* Effect.yieldNow;
579 │ │ const written = yield* eventSink.write({ events: [nextEvent] });
580 │ │ const received = yield* Fiber.join(reader);
581 │ │ if (Option.isNone(received)) {
582 │ │ return yield* Effect.die("The event stream ended before delivering the live event.");
583 │ │ }
584 │ │ assert.equal(received.value.sequence, written[0]?.sequence);
585 │ │ assert.equal(received.value.event.id, nextEvent.id);
586 │ │ afterSequence = received.value.sequence;
587 │ ╰─▶ }
588 │ }),
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:2327:9]
2326 │ let settled = false;
2327 │ ╭─▶ while (!settled) {
2328 │ │ settled = (yield* outbox.listByCommandId(commandId)).every(
2329 │ │ (effect) => effect.status === "succeeded",
2330 │ │ );
2331 │ │ if (!settled) yield* Effect.yieldNow;
2332 │ ╰─▶ }
2333 │ }).pipe(Effect.provide(layerWorker), Effect.scoped);
╰────
⚠ unicorn(prefer-set-has): should be a `Set`, and use `.has()` to check existence or non-existence.
╭─[apps/web/src/components/chat/useComposerSend.ts:978:13]
977 │ const changedBeforeDecline = draftChangedSinceSend();
978 │ ╭─▶ const pendingIdsBeforeDecline = pendingApprovalsRef.current.map(
979 │ │ (approval) => approval.requestId,
980 │ ╰─▶ );
981 │ const approvalResponding = approvalsToDecline.some((approval) =>
╰────
help: Switch to `Set`
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/components/ui/AndroidAnchoredMenu.tsx:152:27]
151 │ <View ref={anchorRef} collapsable={false} className={props.className} style={props.style}>
152 │ {props.children(open)}
· ──┬─
· ╰── Cannot access ref value during render
153 │ </View>
╰────
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/extra memoization dependencies
╭─[apps/mobile/src/components/ui/AndroidAnchoredMenu.tsx:140:9]
139 │ if (action.id !== undefined) {
140 │ props.onPressAction?.({
· ──┬──
· ╰── Missing dependency `props`
141 │ nativeEvent: { event: action.id },
142 │ } as Parameters<NonNullable<MenuComponentProps["onPressAction"]>>[0]);
143 │ }
144 │ },
145 │ [close, props.onPressAction],
· ─────────┬─────────
· ╰── Overly precise dependency `props.onPressAction`, use `props` instead
146 │ );
╰────
help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI. Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/background/HostPowerMonitor.test.ts:133:11]
132 │ const monitor = yield* HostPowerMonitor.HostPowerMonitor;
133 │ ╭─▶ for (
134 │ │ let attempt = 0;
135 │ │ attempt < 100 && (yield* monitor.snapshot).onBattery !== "true";
136 │ │ attempt += 1
137 │ │ ) {
138 │ │ yield* Effect.yieldNow;
139 │ ╰─▶ }
140 │ expect((yield* monitor.snapshot).onBattery).toBe("true");
╰────
⚠ 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.
⚠ eslint(no-unused-vars): Identifier 'HostProcess' is imported but never used.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:25:13]
24 │ import * as Schema from "effect/Schema";
25 │ import * as HostProcess from "@t3tools/shared/HostProcess";
· ─────┬─────
· ╰── 'HostProcess' is imported here
26 │
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Variable 'serverConfig' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:124:11]
123 │ const path = yield* Path.Path;
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
· ──────┬─────
· ╰── 'serverConfig' is declared here
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'serverSettings' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:125:11]
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
· ───────┬──────
· ╰── 'serverSettings' is declared here
126 │ const gitWorkflow = yield* GitWorkflowService.GitWorkflowService;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:121:27]
120 │ const scope = makeScope(options.capabilities ?? new Set(["preview", "worktree"]));
121 │ const dispatch = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
122 │ (options.dispatchGate ?? Effect.void).pipe(
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:134:39]
133 │ );
134 │ const listLocalBranchNames = vi.fn((_: string) =>
· ┬
· ╰── '_' is declared here
135 │ Effect.succeed(
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:178:31]
177 │ });
178 │ const sendToThread = vi.fn((_: unknown) => {
· ┬
· ╰── '_' is declared here
179 │ switch (options.continuation ?? "queued") {
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:203:33]
202 │ );
203 │ const removeWorktree = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
204 │ options.removeWorktreeFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:208:36]
207 │ );
208 │ const deleteLocalBranch = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
209 │ options.deleteLocalBranchFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:213:42]
212 │ );
213 │ const fetchWorktreeBaseCommit = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
214 │ options.fetchWorktreeBaseFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:254:30]
253 │ );
254 │ const localStatus = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
255 │ Effect.succeed({
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:264:32]
263 │ );
264 │ const refreshStatus = vi.fn((_: string) => Effect.die("refreshStatus stub"));
· ┬
· ╰── '_' is declared here
265 │ const runForThread = vi.fn((input: { readonly worktreePath: string }) => {
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Variable 'revokeActiveMcpThread' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/mcp/McpSessionRegistry.ts:218:7]
217 │
218 │ const revokeActiveMcpThread = (threadId: ThreadId): Effect.Effect<void> =>
· ──────────┬──────────
· ╰── 'revokeActiveMcpThread' is declared here
219 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeThread(threadId) : Effect.void;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'revokeAllActiveMcpCredentials' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/mcp/McpSessionRegistry.ts:221:7]
220 │
221 │ const revokeAllActiveMcpCredentials = (): Effect.Effect<void> =>
· ──────────────┬──────────────
· ╰── 'revokeAllActiveMcpCredentials' is declared here
222 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeAll : Effect.void;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Identifier 'HookForwarder' is imported but never used.
╭─[infra/relay/src/http/Api.ts:69:13]
68 │ import * as EnvironmentLinks from "../environments/EnvironmentLinks.ts";
69 │ import * as HookForwarder from "../hooks/HookForwarder.ts";
· ──────┬──────
· ╰── 'HookForwarder' is imported here
70 │ import * as HeldHooks from "../hooks/HeldHooks.ts";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:555:70]
554 │ assert.deepStrictEqual(
555 │ (yield* Ref.get(fixture.syncCommands)).map(({ commandId: _, ...rest }) => rest),
· ┬
· ╰── '_' is declared here
556 │ [
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts:1155:70]
1154 │ assert.deepStrictEqual(
1155 │ (yield* Ref.get(fixture.linkCommands)).map(({ commandId: _, ...rest }) => rest),
· ┬
· ╰── '_' is declared here
1156 │ [
╰────
help: Consider removing this parameter.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/thread-inspector-content-stack.tsx:60:5]
58 │
59 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
60 │ setMountedModes((current) => {
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
61 │ if (current.has(props.mode)) {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-new): Do not use 'new' for side effects.
╭─[apps/server/src/mcp/McpToolAccess.test.ts:168:3]
167 │ // @ts-expect-error a declaration constructed directly
168 │ new McpToolAccess.Declaration(unchecked);
· ─────────────────────────────
169 │ // @ts-expect-error a handlers layer built outside McpToolAccess
╰────
help: Assign the result of 'new' to a variable or compare it to a reference.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:285:5]
283 │ const [snoozeWakeTick, bumpSnoozeWakeTick] = useState(0);
284 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
285 │ setNow(new Date().toISOString());
· ───┬──
· ╰── Avoid calling setState() directly within an effect
286 │ 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:365:25]
364 │ // range) the boundary string is identical and the chain would die.
365 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
· ───────┬──────
· ╰── Unnecessary dependency `snoozeWakeTick`
366 │ 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:356:53]
355 │ if (Number.isNaN(wakeAtMs)) return;
356 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
· ─────┬────
· ╰── Cannot call impure function
357 │ 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
⚠ eslint(no-empty-pattern): Empty array binding pattern
╭─[apps/server/src/pullRequest/PullRequestService.test.ts:1429:12]
1428 │
1429 │ for (const [] of [
· ──
1430 │ ["github", "github.com"],
╰────
help: Passing non-iterable values (null, undefined, numbers, booleans, etc.) will result in a runtime error because these values are not iterable.
⚠ 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(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:643:5]
638 │
639 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
640 │ if (pendingLaunchEntry.key === launchTargetKey) {
641 │ return;
642 │ }
643 │ setPendingLaunchEntry({
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
644 │ key: launchTargetKey,
╰────
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/terminal/ThreadTerminalRouteScreen.tsx:653:5]
648 │
649 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
650 │ if (initialAttachGridEntry.key === launchTargetKey) {
651 │ return;
652 │ }
653 │ setInitialAttachGridEntry({
· ────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
654 │ key: launchTargetKey,
╰────
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/terminal/ThreadTerminalRouteScreen.tsx:746:7]
743 │
744 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
745 │ if (!routeEnvironmentId || !routeThreadId) {
746 │ setLastGridSize({
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
747 │ cols: DEFAULT_TERMINAL_COLS,
╰────
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/terminal/ThreadTerminalRouteScreen.tsx:538:24]
537 │ });
538 │ }, [terminal.buffer, terminal.buffer.length, terminalKey]);
· ───────────┬──────────
· ╰── Overly precise dependency `terminal.buffer.length`, use `terminal.buffer` instead
539 │ const cwd = terminal.summary?.cwd ?? selectedThreadProject?.workspaceRoot ?? null;
╰────
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/terminal/ThreadTerminalRouteScreen.tsx:709:7]
708 │ sentInitialInputKeyRef.current = null;
709 │ }, [terminalKey]);
· ─────┬─────
· ╰── Unnecessary dependency `terminalKey`
710 │
╰────
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/terminal/ThreadTerminalRouteScreen.tsx:800:52]
799 │ };
800 │ }, [canOperateTerminal, isRunning, pasteSession, terminal.lifecycleVersion, terminalKey]);
· ────────────┬──────────── ─────┬─────
· │ ╰── Unnecessary dependency `terminalKey`
· ╰── Unnecessary dependency `terminal.lifecycleVersion`
801 │
╰────
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(refs): Cannot access refs during render
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:793:24]
792 │ }
793 │ const pasteSession = pasteSessionRef.current;
· ───────────┬───────────
· ╰── Cannot access ref value during render
794 │
╰────
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
⚠ eslint(no-unused-vars): Variable 'layerUnavailable' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/Orchestrator.ts:12235:7]
12234 │
12235 │ const layerUnavailable: Layer.Layer<OrchestratorV2> = Layer.succeed(
· ────────┬───────
· ╰── 'layerUnavailable' is declared here
12236 │ OrchestratorV2,
╰────
help: Consider removing this declaration.
⚠ 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
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/project/ProjectService.test.ts:94:3]
93 │ ) {
94 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
95 │ │ const project = Option.getOrThrow(yield* service.getById(projectId));
96 │ │ if (predicate(project)) return project;
97 │ │ yield* Effect.yieldNow;
98 │ ╰─▶ }
99 │ return yield* Effect.die(`Project ${projectId} was not enriched in time.`);
╰────
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/components/ProjectFavicon.tsx:158:5]
153 │ const [activeFaviconRequest, setActiveFaviconRequest] = useState<typeof faviconRequest>(null);
154 │ useLayoutEffect(() => {
· ───────┬───────
· ╰── This is the containing effect
155 │ if (faviconRequest === null) return;
156 │
157 │ const endRequest = beginProjectFaviconRequest(faviconRequest);
158 │ setActiveFaviconRequest(faviconRequest);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
159 │ return endRequest;
╰────
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/terminal/terminalLaunchContext.ts:117:5]
112 │ const [entry, setEntry] = useState(() => ({ key: input.targetKey, location: candidate }));
113 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
114 │ if (entry.key === input.targetKey && (entry.location !== null || candidate === null)) {
115 │ return;
116 │ }
117 │ setEntry({ key: input.targetKey, location: candidate });
· ────┬───
· ╰── Avoid calling setState() directly within an effect
118 │ }, [candidate, entry.key, entry.location, input.targetKey]);
╰────
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-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/terminal/TerminalContextSheet.tsx:72:15]
71 │ <Pressable
72 │ key={index}
· ───────────
73 │ accessibilityRole="button"
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(static-components): Cannot create components during render
╭─[apps/mobile/src/features/terminal/NativeTerminalSurface.tsx:234:10]
196 │ const { onInput, onResize } = props;
197 │ const NativeTerminalSurfaceView = resolveNativeTerminalSurfaceView();
· ────────────────┬───────────────
· ╰── The component is created during render here
198 │ const hasNativeSurface = Boolean(NativeTerminalSurfaceView);
199 │
200 │ useEffect(() => {
201 │ terminalDebugLog("native:surface", {
202 │ terminalKey: props.terminalKey,
203 │ native: hasNativeSurface,
204 │ hardwareKeyRevision: getNativeTerminalHardwareKeyRevision(),
205 │ bufferLen: props.buffer.length,
206 │ isRunning: props.isRunning,
207 │ });
208 │ }, [hasNativeSurface, props.buffer.length, props.isRunning, props.terminalKey]);
209 │ const handleNativeInput = useCallback(
210 │ (event: NativeSyntheticEvent<TerminalInputEvent>) => {
211 │ if (!props.isRunning || props.readOnly) {
212 │ return;
213 │ }
214 │ terminalDebugLog("native:onInput", {
215 │ codes: Array.from(event.nativeEvent.data, (char) => char.codePointAt(0)),
216 │ });
217 │ onInput(event.nativeEvent.data);
218 │ },
219 │ [onInput, props.isRunning, props.readOnly],
220 │ );
221 │ const handleNativeResize = useCallback(
222 │ (event: NativeSyntheticEvent<TerminalResizeEvent>) => {
223 │ onResize({
224 │ cols: event.nativeEvent.cols,
225 │ rows: event.nativeEvent.rows,
226 │ });
227 │ },
228 │ [onResize],
229 │ );
230 │
231 │ if (NativeTerminalSurfaceView) {
232 │ return (
233 │ <View style={props.style}>
234 │ <NativeTerminalSurfaceView
· ────────────┬────────────
· ╰── This component is created during render
235 │ appearanceScheme={themeAppearance}
╰────
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(purity): Cannot call impure function during render
╭─[apps/web/src/components/CommandPalette.tsx:1996:20]
1995 │ title: inferProjectTitleFromPath(destinationPath),
1996 │ createdAt: new Date().toISOString(),
· ─────┬────
· ╰── Cannot call impure function
1997 │ remoteUrl: addProjectCloneFlow.remoteUrl,
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ 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
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/project/ProjectEnrichmentService.test.ts:28:3]
27 │ ) {
28 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
29 │ │ const available = yield* service.peek(workspaceRoot);
30 │ │ if (predicate(available)) return available;
31 │ │ yield* Effect.yieldNow;
32 │ ╰─▶ }
33 │ return yield* Effect.die(`Project metadata for ${workspaceRoot} was not resolved in time.`);
╰────
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:602:27]
601 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
602 │ const gesture = Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
603 │ .enabled(!props.disabled)
╰────
help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ eslint(no-unneeded-ternary): Unnecessary use of boolean literals in conditional expression
╭─[packages/shared/src/serverSettings.test.ts:35:7]
34 │ const fallback = fallbackTextGenerationModelSelection(providerInstances, (instanceId) =>
35 │ instanceId === configured ? true : false,
· ────────────────────────────────────────
36 │ );
╰────
help: Remove this ternary operator
⚠ 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(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(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
⚠ eslint(no-unused-vars): Variable 'useDragRegion' is declared but never used. Unused variables should start with a '_'.
╭─[apps/web/src/components/preview/PreviewPanelShell.tsx:61:9]
60 │ ) {
61 │ const useDragRegion = isElectron && props.mode !== "sheet" && props.mode !== "embedded";
· ──────┬──────
· ╰── 'useDragRegion' is declared here
62 │ const isInline = props.mode === "inline";
╰────
help: Consider removing this declaration.
⚠ 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-inline-schema-compile): Hoist Schema.encodeUnknownSync(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/contracts/src/baseSchemas.test.ts:39:9]
38 │ JSON.stringify(
39 │ Schema.encodeUnknownSync(Schema.toCodecJson(Named))([
· ────────────────────────
40 │ { name: "a" },
╰────
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/keyboard/HardwareKeyboardCommandProvider.tsx:116:34]
115 │ return [...commands];
116 │ }, [activeThreadRef, pathname, registrationVersion, navigation]);
· ─────────┬─────────
· ╰── Unnecessary dependency `registrationVersion`
117 │
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ 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.
⚠ t3code(no-inline-schema-compile): Hoist Schema.encodeUnknownSync(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/contracts/src/composerContext.test.ts:181:18]
180 │ it("sends a message without the records the wire cannot carry", () => {
181 │ const wire = Schema.encodeUnknownSync(Schema.toCodecJson(OrchestrationMessageContext))({
· ────────────────────────
182 │ version: 1,
╰────
⚠ unicorn(require-module-specifiers): Empty import specifier is not allowed
╭─[packages/contracts/src/rpc.ts:295:8]
294 │ } from "./device.ts";
295 │ import {} from "./previewAutomation.ts";
· ──
296 │ import {
╰────
help: Remove empty braces
⚠ eslint(no-unused-vars): Function 'resolveThreadWorkspaceCwd' is declared but never used.
╭─[apps/server/src/checkpointing/Utils.ts:12:10]
11 │
12 │ function resolveThreadWorkspaceCwd(input: {
· ────────────┬────────────
· ╰── 'resolveThreadWorkspaceCwd' is declared here
13 │ readonly thread: {
╰────
help: Consider removing this declaration.
⚠ 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(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
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownSync(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/contracts/src/auth.test.ts:17:12]
16 │ it("decodes legacy review credentials without offering them in new grants", () => {
17 │ expect(Schema.decodeUnknownSync(AuthEnvironmentScopes)(["review:write"])).toEqual([
· ────────────────────────
18 │ "review:write",
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownSync(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/contracts/src/auth.test.ts:20:18]
19 │ ]);
20 │ expect(() => Schema.decodeUnknownSync(AuthGrantScopes)(["review:write"])).toThrow();
· ────────────────────────
21 │ expect(AuthStandardClientScopes).not.toContain("review:write");
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownSync(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/contracts/src/auth.test.ts:58:21]
57 │ it("ignores unknown response permissions without falling back to broader scopes", () => {
58 │ const session = Schema.decodeUnknownSync(AuthSessionState)({
· ────────────────────────
59 │ authenticated: true,
╰────
⚠ unicorn(require-module-specifiers): Empty import specifier is not allowed
╭─[apps/server/src/sourceControl/SourceControlProviderRegistry.ts:15:13]
14 │ } from "@t3tools/contracts";
15 │ import type {} from "@t3tools/contracts";
· ──
16 │ import { detectSourceControlProviderFromRemoteUrl } from "@t3tools/shared/sourceControl";
╰────
help: Remove empty braces
⚠ 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/modules/t3-source-text/src/SourceText.tsx:36:9]
35 │ <T3SourceTextRunNativeComponent
36 │ key={index}
· ───────────
37 │ style={flattenedStyle}
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ 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
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:771:7]
770 │ if (settingsSheetPresentation.isActive) {
771 │ settingsRoutePresentation.present(settingsRouteSession);
· ────────────┬────────────
· ╰── Missing dependency `settingsRoutePresentation`
772 │ }
773 │ }, [settingsRoutePresentation.present, settingsRouteSession, settingsSheetPresentation.isActive]);
· ────────────────┬────────────────
· ╰── Overly precise dependency `settingsRoutePresentation.present`, use `settingsRoutePresentation` instead
774 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:389:5]
385 │ typeof props.style.borderRadius === "number" ? props.style.borderRadius : 0;
386 │ const animatedBorderRadius = useSharedValue(targetBorderRadius);
· ──────────┬─────────
· ╰── `animatedBorderRadius` originates here
387 │ const shouldAnimate = props.animateLayout !== false && Platform.OS !== "android";
388 │ useLayoutEffect(() => {
389 │ animatedBorderRadius.value = shouldAnimate
· ──────────┬─────────
· ╰── `animatedBorderRadius` cannot be modified
390 │ ? withTiming(targetBorderRadius, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[packages/provider-opencode/src/server/OpenCodeRuntime.environment.test.ts:53:14]
52 │
53 │ for (const {} of [
· ──
54 │ { healthy: true },
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ 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
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[packages/shared/src/composerContextLegacySend.ts:19:45]
18 │ const occurrences = collectComposerContextReferences(text);
19 │ for (const occurrence of [...occurrences].reverse()) {
· ───────
20 │ const record = recordsById.get(occurrence.contextId);
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[packages/shared/src/serverSettings.ts:346:9]
345 │ const entry: ProjectSettingsOverrides = {
346 │ ...(entries.get(projectId) ?? currentEntries[projectId] ?? {}),
· ──────────────────────────────────────────────────────────────
347 │ };
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ oxc(no-accumulating-spread): Do not spread accumulators in Array.prototype.reduce()
╭─[packages/shared/src/serverSettings.ts:448:24]
447 │ const favorites =
448 │ setModelFavorites?.reduce((current, change) => {
· ───┬──
· ╰── For this reduce
449 │ const exists = current.some(
450 │ (favorite) => favorite.provider === change.provider && favorite.model === change.model,
451 │ );
452 │ return change.favorite
453 │ ? exists
454 │ ? current
455 │ : [...current, { provider: change.provider, model: change.model }]
· ─────┬────
· ╰── From this spread
456 │ : current.filter(
╰────
help: Consider using `Object.assign()` or `Array.prototype.push()` to mutate the accumulator instead.
note: Using spreads within accumulators leads to `O(n^2)` time complexity.
⚠ oxc(no-accumulating-spread): Do not spread accumulators in loops
╭─[packages/shared/src/serverSettings.ts:466:3]
464 │ null;
465 │ let nextModelPreferences = initialModelPreferences;
· ──────────┬─────────
· ╰── From this accumulator
466 │ for (const change of setModelsHidden ?? []) {
· ─┬─
· ╰── For this loop
467 │ const preferences = nextModelPreferences?.[change.provider] ?? {
468 │ hiddenModels: [],
469 │ modelOrder: [],
470 │ };
471 │ const hiddenModels = preferences.hiddenModels.filter((model) => model !== change.model);
472 │ if (change.hidden) hiddenModels.push(change.model);
473 │ nextModelPreferences = {
474 │ ...nextModelPreferences,
· ───────────┬───────────
· ╰── From this spread
475 │ [change.provider]: { ...preferences, hiddenModels },
╰────
help: Consider using `Object.assign()` to mutate the accumulator instead.
note: Using spreads within accumulators leads to `O(n^2)` time complexity.
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[packages/provider-opencode/src/server/adapter.ts:3755:7]
3754 │
3755 │ const layer: Layer.Layer<ProviderAdapter.ProviderAdapterV2, never, OpenCodeAdapterV2DriverEnv> =
· ──┬──
· ╰── 'layer' is declared here
3756 │ Layer.effect(
╰────
help: Consider removing this declaration.
⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
╭─[apps/web/src/components/settings/SettingInheritance.tsx:163:24]
162 │ keys,
163 │ overridingProjects = [],
· ──
164 │ onClearOverrides,
╰────
help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CustomSnoozeDialog.tsx:140:58]
139 │ {...(weekStartsOn === undefined ? {} : { weekStartsOn })}
140 │ disabled={{ before: new Date(new Date().setHours(0, 0, 0, 0)) }}
· ─────┬────
· ╰── Cannot call impure function
141 │ onSelect={(selected) => {
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/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 │ },
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownOption(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/shared/src/otelEnvironment.ts:146:14]
145 │ name,
146 │ (raw) => Schema.decodeUnknownOption(OtlpProtocol)(raw.toLowerCase()),
· ──────────────────────────
147 │ `${name} is not http/protobuf or http/json, ${NOT_EXPORTED}`,
╰────
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:290:50]
289 │ return (
290 │ <ExistingThreadSettingsRouteContext.Provider value={value}>
· ─────────────
291 │ {props.children}
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:654:44]
653 │ return (
654 │ <ThreadSettingsSessionContext.Provider value={value}>
· ─────────────
655 │ {props.children}
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/ThreadSettingsSheet.tsx:1462:55]
1461 │ return (
1462 │ <ThreadSettingsPickerPresentationContext.Provider value={presentation}>
· ────────────────────
1463 │ <ThreadSettingsPickerStack.Navigator
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ eslint(no-unused-vars): Type 'AuthSessionState' is imported but never used.
╭─[apps/web/src/components/settings/ProviderSettingsPanel.logic.ts:4:8]
3 │ AuthProvidersManageScope,
4 │ type AuthSessionState,
· ────────┬───────
· ╰── 'AuthSessionState' is imported here
5 │ type EnvironmentId,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[packages/shared/src/qrCode.ts:458:44]
457 │ ): Array<byte> {
458 │ let result: Array<byte> = divisor.map((_) => 0);
· ┬
· ╰── '_' is declared here
459 │ for (const b of data) {
╰────
help: Consider removing this parameter.
⚠ 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(purity): Cannot call impure function during render
╭─[apps/web/src/components/sidebar/SidebarThreadRow.tsx:372:47]
371 │ const { open, onOpenChange, onSnooze, timestampFormat } = props;
372 │ const presets = open ? resolveSnoozePresets(new Date(), timestampFormat) : [];
· ─────┬────
· ╰── Cannot call impure function
373 │ return (
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/sidebar/SidebarThreadRow.tsx:853:39]
852 │ if (snoozeGateClock.thread !== thread) {
853 │ setSnoozeGateClock({ thread, now: new Date().toISOString() });
· ─────┬────
· ╰── Cannot call impure function
854 │ }
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:370:7]
369 │ mountedRef.current = false;
370 │ flow.setBranchQuery("");
· ──┬─
· ╰── Missing dependency `flow`
371 │ };
372 │ }, [flow.setBranchQuery]);
· ─────────┬─────────
· ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
373 │
╰────
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/layout/AdaptiveWorkspaceLayout.tsx:215:7]
214 │ }
215 │ }, [wrappedRender]);
· ──────┬──────
· ╰── Unnecessary dependency `wrappedRender`
216 │
╰────
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(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:817:35]
816 │ >
817 │ <AdaptiveWorkspaceContext value={contextValue}>
· ────────────────────
818 │ <NativeWorkspaceInspectorContext
╰────
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/layout/AdaptiveWorkspaceLayout.tsx:832:42]
831 │ >
832 │ <AdaptiveWorkspaceContext.Provider value={contextValue}>
· ────────────────────
833 │ <WindowHingeContext value={windowHinge}>
╰────
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(immutability): This value cannot be modified
╭─[apps/mobile/src/features/layout/workspace-inspector-pane.tsx:42:5]
35 │
36 │ const inspectorProgress = useSharedValue(inspectorVisible ? 1 : 0);
· ────────┬────────
· ╰── `inspectorProgress` originates here
37 │ const { renderedInspectorWidth } = props;
38 │ const renderedContentWidth = useSharedValue(inspectorWidth ?? 0);
39 │
40 │ const onClosed = props.onClosed;
41 │ useEffect(() => {
42 │ inspectorProgress.value = withTiming(
· ────────┬────────
· ╰── `inspectorProgress` cannot be modified
43 │ inspectorVisible ? 1 : 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/layout/workspace-inspector-pane.tsx:67:7]
37 │ const { renderedInspectorWidth } = props;
38 │ const renderedContentWidth = useSharedValue(inspectorWidth ?? 0);
· ──────────┬─────────
· ╰── `renderedContentWidth` originates here
39 │
40 │ const onClosed = props.onClosed;
41 │ useEffect(() => {
42 │ inspectorProgress.value = withTiming(
43 │ inspectorVisible ? 1 : 0,
44 │ WORKSPACE_PANE_TIMING,
45 │ (finished) => {
46 │ if (finished === true && !inspectorVisible && onClosed !== undefined) {
47 │ runOnJS(onClosed)();
48 │ }
49 │ },
50 │ );
51 │ const targetWidth = inspectorVisible ? (inspectorWidth ?? 0) : 0;
52 │ renderedInspectorWidth.set(
53 │ resizing ? targetWidth : withTiming(targetWidth, WORKSPACE_PANE_TIMING),
54 │ );
55 │ }, [
56 │ inspectorProgress,
57 │ inspectorVisible,
58 │ inspectorWidth,
59 │ onClosed,
60 │ renderedInspectorWidth,
61 │ resizing,
62 │ ]);
63 │
64 │ useEffect(() => {
65 │ const targetWidth = inspectorWidth ?? 0;
66 │ if (!inspectorVisible || resizing) {
67 │ renderedContentWidth.value = targetWidth;
· ──────────┬─────────
· ╰── `renderedContentWidth` cannot be modified
68 │ return;
╰────
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
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-codex-app-server/src/schema.test.ts:50:18]
49 │ for (const tool of ["sendMessage", "followupTask", "interruptAgent", "listAgents"]) {
50 │ assert.equal(Schema.is(CodexSchema.ServerNotification__CollabAgentTool)(tool), true);
· ─────────
51 │ assert.equal(Schema.is(CodexSchema.V2ThreadResumeResponse__CollabAgentTool)(tool), true);
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-codex-app-server/src/schema.test.ts:51:18]
50 │ assert.equal(Schema.is(CodexSchema.ServerNotification__CollabAgentTool)(tool), true);
51 │ assert.equal(Schema.is(CodexSchema.V2ThreadResumeResponse__CollabAgentTool)(tool), true);
· ─────────
52 │ }
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-codex-app-server/src/schema.test.ts:55:5]
54 │ assert.equal(
55 │ Schema.is(CodexSchema.ServerNotification__CollabAgentToolCallStatus)("interrupted"),
· ─────────
56 │ true,
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-codex-app-server/src/schema.test.ts:59:5]
58 │ assert.equal(
59 │ Schema.is(CodexSchema.V2ThreadResumeResponse__CollabAgentToolCallStatus)("interrupted"),
· ─────────
60 │ true,
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-codex-app-server/src/schema.test.ts:103:16]
102 │
103 │ assert.equal(Schema.is(CodexSchema.V2ThreadResumeResponse)(resumeResponse), true);
· ─────────
104 │ });
╰────
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/Stack.tsx:1044:21]
1043 │ <Navigator
1044 │ screenLayout={(props) => <GuardedScreenLayout {...props} />}
· ─────────────────────────────────────────────
1045 │ screenListeners={{
╰────
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.
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:131:9]
130 │ ) {
131 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
132 │ │ if (subscriptions.length >= count) {
133 │ │ return;
134 │ │ }
135 │ │ yield* Effect.yieldNow;
136 │ ╰─▶ }
137 │ return yield* Effect.die(new Error(`Expected ${count} durable subscriptions.`));
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:252:7]
251 │ yield* SubscriptionRef.set(activeSession, Option.some(session(firstClient)));
252 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 1; attempt += 1) {
253 │ │ yield* Effect.yieldNow;
254 │ ╰─▶ }
255 │ yield* SubscriptionRef.set(activeSession, Option.none());
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:258:7]
257 │
258 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
259 │ │ yield* Effect.yieldNow;
260 │ ╰─▶ }
261 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:322:7]
321 │ );
322 │ ╭─▶ for (let attempt = 0; attempt < 100 && observedFailures.length < 1; attempt += 1) {
323 │ │ yield* Effect.yieldNow;
324 │ ╰─▶ }
325 │
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:330:7]
329 │ yield* SubscriptionRef.set(activeSession, Option.some(session(secondClient)));
330 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
331 │ │ yield* Effect.yieldNow;
332 │ ╰─▶ }
333 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/state/threads-sync.test.ts:1228:7]
1227 │ yield* harness.replaceSession;
1228 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
1229 │ │ if ((yield* Ref.get(harness.subscriptionCount)) >= 2) {
1230 │ │ break;
1231 │ │ }
1232 │ │ yield* Effect.yieldNow;
1233 │ ╰─▶ }
1234 │ yield* Queue.offer(
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/state/threads-sync.test.ts:1337:7]
1336 │ yield* harness.replaceSession;
1337 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
1338 │ │ if ((yield* Ref.get(harness.subscriptionCount)) >= 2) break;
1339 │ │ yield* Effect.yieldNow;
1340 │ ╰─▶ }
1341 │ expect(yield* Ref.get(harness.subscriptionCount)).toBe(2);
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/session.test.ts:226:3]
225 │ ) {
226 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
227 │ │ const socket = sockets[index];
228 │ │ if (socket) {
229 │ │ return socket;
230 │ │ }
231 │ │ yield* Effect.yieldNow;
232 │ ╰─▶ }
233 │ return yield* Effect.die(new Error("Expected the RPC protocol to create a websocket."));
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/session.test.ts:240:3]
239 │ ) {
240 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
241 │ │ const request = socket.sent.map((message) => decodeJson(message)).filter(isRpcRequest)[index];
242 │ │ if (request) {
243 │ │ return request;
244 │ │ }
245 │ │ yield* Effect.yieldNow;
246 │ ╰─▶ }
247 │ return yield* Effect.die(new Error("Expected the RPC protocol to send a request."));
╰────
Found 0 errors and 358 warnings in 5402 files (6.4s, 8 threads)
Post job cleanup.
Cache hit occurred on the primary key electron-Linux-X64-854e11ddd491bd4f350eebb67a74265df119376a3984c8e153cfe5fc8ced6309, not saving cache.
Post job cleanup.
##[start-action display=Cache full pnpm store;id=__99bb687e-9ab0-4bfe-873b-e8f8a6fc74db.__actions_cache]
Post job cleanup.
Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-00e587c1edf31fe669c96bc4768c0e07a969fff8e8228235fb75ec6c0abf4161, not saving cache.
##[end-action id=__99bb687e-9ab0-4bfe-873b-e8f8a6fc74db.__actions_cache;outcome=success;conclusion=success;duration_ms=156]
##[start-action display=Cache Vite+;id=__99bb687e-9ab0-4bfe-873b-e8f8a6fc74db.vp_cache]
Post job cleanup.
Cache hit occurred on the primary key vite-plus-home-v2-Linux-X64-1.3.0-node26.12.1-pnpm@12.14.0, not saving cache.
##[end-action id=__99bb687e-9ab0-4bfe-873b-e8f8a6fc74db.vp_cache;outcome=success;conclusion=success;duration_ms=78]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/24ef0204-a28b-4bba-8ef9-8d46772b88ca' 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: 173
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 444
BLACKSMITH_CHECK_RUN_ID: 120194814446
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