GitHub check
256 KB of 595 KB loaded Download the full log (595 KB)
339 KB of earlier output not loaded
/react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ 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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftRouteScreen.tsx:84:5]
79 │
80 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
81 │ if (!needsPreparation || !initialProjectRef.branch || waitingForProject) return;
82 │ const branchName = initialProjectRef.branch;
83 │ let active = true;
84 │ setPendingCheckouts((count) => count + 1);
· ─────────┬─────────
· ╰── Avoid calling setState() directly within an effect
85 │ // Serialize replacements: ignoring a stale result cannot undo its Git mutation.
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(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/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
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[apps/mobile/src/state/use-model-option-memory.ts:21:7]
20 │ [instanceId]: {
21 │ ...(state[instanceId] ?? {}),
· ────────────────────────────
22 │ [model]: options,
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/state/use-vcs-action-state.ts:86:5]
83 │ const [nowMs, setNowMs] = useState(() => Date.now());
84 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
85 │ if (!actionState.isRunning) return;
86 │ setNowMs(Date.now());
· ────┬───
· ╰── Avoid calling setState() directly within an effect
87 │ const interval = setInterval(() => setNowMs(Date.now()), 1000);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(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
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/state/thread-order.ts:29:7]
28 │ getPendingThreadOrder();
29 │ }, [nowMinute, snoozeWakeTick]);
· ────┬──── ───────┬──────
· │ ╰── Unnecessary dependency `snoozeWakeTick`
· ╰── Unnecessary dependency `nowMinute`
30 │ return pending;
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:553:7]
547 │ }, [cancelledIncomingShareId, navigation, props.incomingShareId]);
548 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
549 │ if (!isReturningToProjectPicker) {
550 │ return;
551 │ }
552 │ if (requestedInitialProjectAvailable) {
553 │ setIsReturningToProjectPicker(false);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
554 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:701:9]
644 │
645 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
646 │ if (props.pendingTaskId || props.draftId) {
647 │ return;
648 │ }
649 │ if (lastInitialProjectRefRef.current !== props.initialProjectRef) {
650 │ lastInitialProjectRefRef.current = props.initialProjectRef;
651 │ appliedInitialProjectKeyRef.current = null;
652 │ }
653 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
654 │ const initialProjectId = props.initialProjectRef?.projectId;
655 │ if (initialEnvironmentId && initialProjectId) {
656 │ const directProject =
657 │ projects.find(
658 │ (project) =>
659 │ project.environmentId === initialEnvironmentId && project.id === initialProjectId,
660 │ ) ?? null;
661 │
662 │ if (directProject) {
663 │ // Apply the route's project once. Re-applying on every change would
664 │ // instantly revert environment/project switches made in the picker.
665 │ const directProjectKey = `${directProject.environmentId}:${directProject.id}`;
666 │ if (appliedInitialProjectKeyRef.current === directProjectKey) {
667 │ return;
668 │ }
669 │ if (props.initialProjectRef?.branch) {
670 │ if (
671 │ selectedProject?.environmentId !== directProject.environmentId ||
672 │ selectedProject.id !== directProject.id
673 │ ) {
674 │ setProject(directProject);
675 │ return;
676 │ }
677 │ if (!flow.draftKey) return;
678 │ // The route completes checkout before mounting this composer. Local
679 │ // mode reuses an existing worktree; worktree mode would create another.
680 │ updateComposerDraftSettings(flow.draftKey, {
681 │ workspaceSelection: {
682 │ mode: "local",
683 │ branch: props.initialProjectRef.branch,
684 │ worktreePath: props.initialProjectRef.worktreePath ?? null,
685 │ startFromOrigin: false,
686 │ },
687 │ });
688 │ }
689 │ appliedInitialProjectKeyRef.current = directProjectKey;
690 │ if (
691 │ selectedProject?.environmentId === directProject.environmentId &&
692 │ selectedProject.id === directProject.id
693 │ ) {
694 │ return;
695 │ }
696 │ setProject(directProject);
697 │ return;
698 │ }
699 │
700 │ if (projects.length > 0) {
701 │ setIsReturningToProjectPicker(true);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
702 │ }
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:801:5]
742 │
743 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
744 │ const shareId = props.incomingShareId;
745 │ const draftKey = flow.draftKey;
746 │ const destinationProject = selectedProject;
747 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
748 │ const initialProjectId = props.initialProjectRef?.projectId;
749 │ const selectedProjectMatchesRoute =
750 │ !initialEnvironmentId ||
751 │ !initialProjectId ||
752 │ (destinationProject?.environmentId === initialEnvironmentId &&
753 │ destinationProject.id === initialProjectId);
754 │ if (
755 │ !shareId ||
756 │ !draftKey ||
757 │ !destinationProject ||
758 │ !selectedProjectMatchesRoute ||
759 │ cancelledIncomingShareId === shareId
760 │ ) {
761 │ return;
762 │ }
763 │ const importKey = `${shareId}:${draftKey}`;
764 │ if (
765 │ startedShareImportKeyRef.current === importKey ||
766 │ cancellingShareImportKeyRef.current === importKey
767 │ ) {
768 │ return;
769 │ }
770 │
771 │ if (!incomingShare) {
772 │ if (isIncomingShareUnavailable && alertedUnavailableIncomingShareIdRef.current !== shareId) {
773 │ alertedUnavailableIncomingShareIdRef.current = shareId;
774 │ Dialog.alert(
775 │ "Shared content unavailable",
776 │ "The shared content is no longer in the inbox. You can continue editing this task draft.",
777 │ );
778 │ }
779 │ return;
780 │ }
781 │
782 │ if (
783 │ incomingShare.attachments.some((attachment) => attachment.type === "file") &&
784 │ selectedEnvironmentServerConfig === null
785 │ ) {
786 │ return;
787 │ }
788 │
789 │ if (alertedUnavailableIncomingShareIdRef.current === shareId) {
790 │ alertedUnavailableIncomingShareIdRef.current = null;
791 │ }
792 │ startedShareImportKeyRef.current = importKey;
793 │ const draftBackup =
794 │ shareImportDraftBackupRef.current.get(importKey) ?? getComposerDraftSnapshot(draftKey);
795 │ shareImportDraftBackupRef.current.set(importKey, draftBackup);
796 │ const importToken = Symbol(importKey);
797 │ let didReserveShare = false;
798 │ let didConsumeShare = false;
799 │ let needsDraftRestore = false;
800 │ activeShareImportTokenRef.current = importToken;
801 │ setImportingShareKey(importKey);
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
802 │ void (async () => {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:721:5]
720 │ props.initialProjectRef,
721 │ props.incomingShareId,
· ──────────┬──────────
· ╰── Unnecessary dependency `props.incomingShareId`
722 │ props.pendingTaskId,
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:740:5]
739 │ loadedBranchesProjectKeyRef.current = projectKey;
740 │ flow.loadBranches();
· ──┬─
· ╰── Missing dependency `flow`
741 │ }, [flow.loadBranches, selectedProject]);
· ────────┬────────
· ╰── Overly precise dependency `flow.loadBranches`, use `flow` instead
742 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:963:5]
962 │ flow.draftKey,
963 │ hasImportedIncomingShare,
· ────────────┬───────────
· ╰── Unnecessary dependency `hasImportedIncomingShare`
964 │ incomingShare,
965 │ isIncomingShareInboxLoading,
· ─────────────┬─────────────
· ╰── Unnecessary dependency `isIncomingShareInboxLoading`
966 │ isIncomingShareUnavailable,
967 │ props.incomingShareId,
968 │ props.initialProjectRef?.environmentId,
969 │ props.initialProjectRef?.projectId,
970 │ releaseShareReservation,
971 │ reserveShare,
972 │ selectedEnvironmentServerConfig,
973 │ selectedProject,
974 │ shareImportAttempt,
· ─────────┬────────
· ╰── Unnecessary dependency `shareImportAttempt`
975 │ ]);
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/connection/ConnectionStatusDot.tsx:58:7]
53 │ function usePulseAnimation(pulse: boolean) {
54 │ const pulseProgress = useSharedValue(0);
· ──────┬──────
· ╰── `pulseProgress` originates here
55 │
56 │ useEffect(() => {
57 │ if (pulse) {
58 │ pulseProgress.value = withRepeat(
· ──────┬──────
· ╰── `pulseProgress` cannot be modified
59 │ withTiming(1, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:707:7]
706 │ if (settingsSheetPresentation.isActive) {
707 │ settingsRoutePresentation.present(settingsRouteSession);
· ────────────┬────────────
· ╰── Missing dependency `settingsRoutePresentation`
708 │ }
709 │ }, [settingsRoutePresentation.present, settingsRouteSession, settingsSheetPresentation.isActive]);
· ────────────────┬────────────────
· ╰── Overly precise dependency `settingsRoutePresentation.present`, use `settingsRoutePresentation` instead
710 │
╰────
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:302:5]
298 │ typeof props.style.borderRadius === "number" ? props.style.borderRadius : 0;
299 │ const animatedBorderRadius = useSharedValue(targetBorderRadius);
· ──────────┬─────────
· ╰── `animatedBorderRadius` originates here
300 │ const shouldAnimate = props.animateLayout !== false && Platform.OS !== "android";
301 │ useLayoutEffect(() => {
302 │ animatedBorderRadius.value = shouldAnimate
· ──────────┬─────────
· ╰── `animatedBorderRadius` cannot be modified
303 │ ? withTiming(targetBorderRadius, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(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(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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:79:5]
76 │
77 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
78 │ const { host, code } = parsePairingUrl(connectionPairingUrl);
79 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
80 │ setCodeInput(code);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:89:5]
82 │
83 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
84 │ if (routePairingUrl.length === 0) {
85 │ return;
86 │ }
87 │
88 │ const { host, code } = parsePairingUrl(routePairingUrl);
89 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
90 │ setCodeInput(code);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:95:7]
92 │
93 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
94 │ if (pairingConnectionError) {
95 │ setIsSubmitting(false);
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
96 │ }
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:388:5]
386 │
387 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
388 │ setInspectorSelection((current) => {
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
389 │ if (props.renderInspector === undefined) {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:516:24]
515 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
516 │ ╭─▶ const GitInspector = () => (
517 │ │ <GitOverviewSheet
518 │ │ headerInset={inspectorHeaderInset}
519 │ │ presentation="inspector"
520 │ │ route={{ params: props.route.params }}
521 │ │ />
522 │ ╰─▶ );
523 │ const FilesInspector = () =>
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:523:26]
522 │ );
523 │ ╭─▶ const FilesInspector = () =>
524 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
525 │ │ <ThreadFileNavigatorPane
526 │ │ cwd={selectedThreadCwd}
527 │ │ environmentId={selectedThread.environmentId}
528 │ │ headerInset={inspectorHeaderInset}
529 │ │ projectName={selectedThreadProject?.title ?? "Files"}
530 │ │ selectedPath={null}
531 │ │ onSelectFile={handleSelectInspectorFile}
532 │ │ />
533 │ ╰─▶ ) : null;
534 │ const RouteInspector = () => props.renderInspector?.(inspectorHeaderInset);
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(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(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.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:282:5]
280 │ const [snoozeWakeTick, bumpSnoozeWakeTick] = useState(0);
281 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
282 │ setNow(new Date().toISOString());
· ───┬──
· ╰── Avoid calling setState() directly within an effect
283 │ const id = setInterval(() => setNow(new Date().toISOString()), 60_000);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:362:25]
361 │ // range) the boundary string is identical and the chain would die.
362 │ }, [nextSnoozeWakeAt, snoozeWakeTick]);
· ───────┬──────
· ╰── Unnecessary dependency `snoozeWakeTick`
363 │ const listItems = ((): readonly SidebarListItem[] => {
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx:353:53]
352 │ if (Number.isNaN(wakeAtMs)) return;
353 │ const delayMs = Math.min(Math.max(0, wakeAtMs - Date.now()) + 50, 2_147_483_647);
· ─────┬────
· ╰── Cannot call impure function
354 │ const id = setTimeout(() => {
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-worktree-setup.ts:30:40]
28 │ const snapshot = resolveWorktreeSetupSnapshot(input.threadId, query.data, live);
29 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
30 │ if (snapshot && snapshot !== live) setHeld({ key, snapshot });
· ───┬───
· ╰── Avoid calling setState() directly within an effect
31 │ }, [key, live, snapshot]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/provider/Drivers/CodexDriver.test.ts:418:14]
417 │
418 │ for (const {} of ["direct", "wrapper"] as const) {
· ──
419 │ }
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[apps/mobile/src/state/use-composer-drafts.ts:1022:15]
1021 │ instanceId,
1022 │ { ...(persisted.modelOptionMemory[instanceId] ?? {}), ...models },
· ──────────────────────────────────────────────────
1023 │ ]),
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:282:7]
281 │ mountedRef.current = false;
282 │ flow.setBranchQuery("");
· ──┬─
· ╰── Missing dependency `flow`
283 │ };
284 │ }, [flow.setBranchQuery]);
· ─────────┬─────────
· ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
285 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ 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.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:496:5]
494 │ }, []);
495 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
496 │ setKeyboardStateSuspect(false);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
497 │ }, [isKeyboardVisible, liveKeyboardHeight]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:850:7]
847 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
848 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
849 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
850 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
· ─────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
851 │ }
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1095:5]
1093 │
1094 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1095 │ setAnchorMessageId(null);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1096 │ setSubmittedMessageId(null);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:497:7]
496 │ setKeyboardStateSuspect(false);
497 │ }, [isKeyboardVisible, liveKeyboardHeight]);
· ────────┬──────── ─────────┬────────
· │ ╰── Unnecessary dependency `liveKeyboardHeight`
· ╰── Unnecessary dependency `isKeyboardVisible`
498 │ const handleOwnedInputFocusChange = (focused: boolean) => {
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1043:7]
1042 │ userInputInsetProgress.set(1);
1043 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
· ────────────┬───────────
· ╰── Unnecessary dependency `activeUserInputRequestId`
1044 │ const showContent = props.showContent ?? true;
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:1101:15]
1100 │ freeze.set(false);
1101 │ }, [freeze, selectedThreadKey]);
· ────────┬────────
· ╰── Unnecessary dependency `selectedThreadKey`
1102 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:931:5]
926 │ const composerPopoverHeight = useSharedValue(0);
927 │ const floatingControlCoverage = useSharedValue(
· ───────────┬───────────
· ╰── `floatingControlCoverage` originates here
928 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
929 │ );
930 │ useEffect(() => {
931 │ floatingControlCoverage.value = withTiming(
· ───────────┬───────────
· ╰── `floatingControlCoverage` cannot be modified
932 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:949:7]
939 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
940 │ const combinedContentInsetEndAdjustment = useSharedValue(
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` originates here
941 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
942 │ );
943 │ useAnimatedReaction(
944 │ () =>
945 │ contentInsetEndAdjustment.value +
946 │ floatingControlCoverage.value +
947 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
948 │ (value) => {
949 │ combinedContentInsetEndAdjustment.value = value;
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` cannot be modified
950 │ },
╰────
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-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/shared/src/atomicWrite.test.ts:139:5]
138 │ Effect.gen(function* () {
139 │ ╭─▶ while (fiber.pollUnsafe() === undefined) {
140 │ │ yield* TestClock.adjust("100 millis");
141 │ │ // oxlint-disable-next-line t3code/no-real-time-wait-in-tests -- a macrotask boundary so the real stat I/O can finish; time moves only via TestClock
142 │ │ yield* Effect.promise(() => new Promise((resolve) => setImmediate(resolve)));
143 │ ╰─▶ }
144 │ return yield* Fiber.join(fiber);
╰────
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/processRunner.test.ts:266:14]
265 │
266 │ for (const {} of ["timeout", "success"] as const) {
· ──
267 │ }
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/mobile/src/features/agent-awareness/remoteRegistration.test.ts:223:5]
222 │ let idlePasses = 0;
223 │ ╭─▶ for (;;) {
224 │ │ yield* Effect.promise(() => Promise.resolve());
225 │ │ const pending = backgroundRuntime.pending.shift();
226 │ │ if (!pending) {
227 │ │ idlePasses++;
228 │ │ if (idlePasses >= 3) {
229 │ │ return;
230 │ │ }
231 │ │ continue;
232 │ │ }
233 │ │ idlePasses = 0;
234 │ │ const exit = yield* Effect.exit(
235 │ │ pending.operation as Effect.Effect<unknown, unknown, ManagedRelay.ManagedRelayClient>,
236 │ │ );
237 │ │ yield* Effect.sync(() => {
238 │ │ pending.resolve(exit);
239 │ │ });
240 │ ╰─▶ }
241 │ },
╰────
⚠ react(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): 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.
⚠ eslint(no-unused-vars): Parameter 'stopSessions' is declared but never used. Unused parameters should start with a '_'.
╭─[apps/server/src/provider/AntigravityAuth.ts:285:20]
284 │ },
285 │ (effect, flow, stopSessions) =>
· ──────┬─────
· ╰── 'stopSessions' is declared here
286 │ effect.pipe(
╰────
help: Consider removing this parameter.
⚠ 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
⚠ 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
⚠ t3code(no-inline-schema-compile): Hoist Schema.encodeEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[apps/server/src/assets/AssetAccess.test.ts:1043:32]
1042 │ expect(error._tag).toBe("AssetGitHubMediaUrlValidationError");
1043 │ const encoded = yield* Schema.encodeEffect(Schema.fromJsonString(AssetAccessError))(error);
· ───────────────────
1044 │ expect(encoded).not.toContain(url);
╰────
⚠ unicorn(prefer-array-find): Prefer `find` over filtering and accessing the first result.
╭─[apps/server/src/terminal/Manager.test.ts:731:31]
730 │ );
731 │ const snapshot = events.filter((event) => event.type === "snapshot").at(-1)?.snapshot;
· ──────
732 │ expect(snapshot?.history).toBe("aa😀\rEND");
╰────
help: Use `find(predicate)` instead of `filter(predicate)[0]` or similar patterns.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/pull-requests/PullRequestRouteScreen.tsx:335:7]
330 │ };
331 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
332 │ if (!guidesEnabled && section === "guide") {
333 │ requestedSection.current = "overview";
334 │ currentScrollOffset.current = scrollOffsets.current.overview ?? -insets.top;
335 │ setSection("overview");
· ─────┬────
· ╰── Avoid calling setState() directly within an effect
336 │ }
╰────
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 effect dependencies
╭─[apps/mobile/src/features/pull-requests/PullRequestRouteScreen.tsx:337:6]
332 │ if (!guidesEnabled && section === "guide") {
333 │ requestedSection.current = "overview";
· ────────┬───────
· ╰── Missing dependency `requestedSection`. 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
334 │ currentScrollOffset.current = scrollOffsets.current.overview ?? -insets.top;
· ─────────┬───────── ──────┬──────
· │ ╰── Missing dependency `scrollOffsets`. 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
· ╰── Missing dependency `currentScrollOffset`. 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
335 │ setSection("overview");
336 │ }
337 │ }, [guidesEnabled, section, insets.top]);
· ──────────────────┬─────────────────
· ╰── This dependency list is missing values used by the callback
338 │ const tabContent = activityContent;
╰────
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 effect dependencies
╭─[apps/mobile/src/features/pull-requests/PullRequestRouteScreen.tsx:873:6]
856 │ if (
857 │ lastSelection.current.path === route.params.path &&
· ──────┬──────
· ╰── Missing dependency `lastSelection`. 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
858 │ lastSelection.current.id === route.params.fileSelectionId
859 │ )
860 │ return;
861 │ lastSelection.current = { path: route.params.path, id: route.params.fileSelectionId };
862 │ if (route.params.focus) navigation.setParams({ focus: undefined });
863 │ setJumpPath(route.params.path);
864 │ setSelectedRowId(null);
865 │ jumpStarted.current = false;
866 │ const file = data.files.find((entry) => entry.path === route.params.path);
867 │ if (!file || !nativeView.current) return;
· ─────┬────
· ╰── Missing dependency `nativeView`. 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
868 │ setCollapsedIds((ids) => ids.filter((id) => id !== file.id));
869 │ jumpStarted.current = true;
870 │ void nativeView.current.scrollToFile(file.id, false).catch(() => {
871 │ jumpStarted.current = false;
872 │ });
873 │ }, [route.params.path, route.params.fileSelectionId, route.params.focus, data.files, navigation]);
· ──────────────────────────────────────────────┬──────────────────────────────────────────────
· ╰── This dependency list is missing values used by the callback
874 │ const appliedFilter = useRef(filter.hideTestFiles);
╰────
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(purity): Cannot call impure function during render
╭─[apps/web/src/components/chat/useThreadLifecycle.tsx:178:58]
177 │ if (snoozeClockState.shell !== activeThreadShell) {
178 │ setSnoozeClockState({ shell: activeThreadShell, now: new Date().toISOString() });
· ─────┬────
· ╰── Cannot call impure function
179 │ }
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[packages/shared/src/serverSettings.ts:343:9]
342 │ const entry: ProjectSettingsOverrides = {
343 │ ...(entries.get(projectId) ?? currentEntries[projectId] ?? {}),
· ──────────────────────────────────────────────────────────────
344 │ };
╰────
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:429:24]
428 │ const favorites =
429 │ setModelFavorites?.reduce((current, change) => {
· ───┬──
· ╰── For this reduce
430 │ const exists = current.some(
431 │ (favorite) => favorite.provider === change.provider && favorite.model === change.model,
432 │ );
433 │ return change.favorite
434 │ ? exists
435 │ ? current
436 │ : [...current, { provider: change.provider, model: change.model }]
· ─────┬────
· ╰── From this spread
437 │ : 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:447:3]
445 │ null;
446 │ let nextModelPreferences = initialModelPreferences;
· ──────────┬─────────
· ╰── From this accumulator
447 │ for (const change of setModelsHidden ?? []) {
· ─┬─
· ╰── For this loop
448 │ const preferences = nextModelPreferences?.[change.provider] ?? {
449 │ hiddenModels: [],
450 │ modelOrder: [],
451 │ };
452 │ const hiddenModels = preferences.hiddenModels.filter((model) => model !== change.model);
453 │ if (change.hidden) hiddenModels.push(change.model);
454 │ nextModelPreferences = {
455 │ ...nextModelPreferences,
· ───────────┬───────────
· ╰── From this spread
456 │ [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.
⚠ 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.
╭─[apps/server/src/auth/RpcAuthorization.ts:236:17]
235 │ const requiredScopesForSettingsUpdate = (payload: unknown) => {
236 │ const input = Schema.decodeUnknownSync(SettingsUpdate)(payload);
· ────────────────────────
237 │ const scopes = requiredScopesForServerSettingsPatch(input.patch);
╰────
⚠ 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.
╭─[apps/server/src/auth/RpcAuthorization.ts:255:26]
254 │ if (method === WS_METHODS.assetsCreateUrl) {
255 │ const { resource } = Schema.decodeUnknownSync(AssetCreateUrlInput)(payload);
· ────────────────────────
256 │ return [
╰────
⚠ 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
⚠ eslint(no-unused-vars): Identifier 'identity' is imported but never used.
╭─[apps/server/src/auth/http.ts:28:10]
27 │ import * as Schema from "effect/Schema";
28 │ import { identity } from "effect/Function";
· ────┬───
· ╰── 'identity' is imported here
29 │ import * as Layer from "effect/Layer";
╰────
help: Consider removing this import.
⚠ typescript(no-this-alias): Unexpected aliasing of 'this' to local variable.
╭─[apps/web/src/contextMenuFallback.test.ts:38:9]
37 │ get isConnected() {
38 │ let current: FakeElement | null = this;
· ───────
39 │ while (current?.parent) {
╰────
help: Assigning a variable to this instead of properly using arrow lambdas may be a symptom of pre-ES2015 practices or not managing scope well.
⚠ 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.
⚠ eslint(no-unused-vars): Function 'summarizePayload' is declared but never used.
╭─[packages/provider-acp/src/server/nativeLogging.ts:22:10]
21 │
22 │ function summarizePayload(payload: unknown): Readonly<Record<string, unknown>> {
· ────────┬───────
· ╰── 'summarizePayload' is declared here
23 │ if (payload === null) return { valueType: "null" };
╰────
help: Consider removing this declaration.
⚠ 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.is(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[apps/server/src/provider/acp/AntigravityProtocol.ts:263:20]
262 │ ...(update._meta !== undefined
263 │ ? { _meta: Schema.is(Schema.Record(Schema.String, Schema.Json))(meta) ? meta : null }
· ─────────
264 │ : {}),
╰────
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
86 │
87 │ const cardCoverage = props.cardCoverage;
· ──────┬─────
· ╰── `cardCoverage` originates here
88 │ const barHeightRef = useRef(0);
89 │ const cardHeightRef = useRef(0);
90 │ const cardHeight = useSharedValue(0);
91 │ const notifyCoverage = useCallback(() => {
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── `cardCoverage` cannot be modified
101 │ return;
╰────
help: Do not mutate component props or hook arguments. If the value should change, update it where it is owned and pass an update callback, or use local state
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:118:7]
89 │ const cardHeightRef = useRef(0);
90 │ const cardHeight = useSharedValue(0);
· ─────┬────
· ╰── `cardHeight` originates here
91 │ const notifyCoverage = useCallback(() => {
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
101 │ return;
102 │ }
103 │ cardCoverage.value = withTiming(coverage, {
104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
105 │ easing: Easing.out(Easing.cubic),
106 │ });
107 │ }, [cardCoverage]);
108 │ const handleBarLayout = useCallback(
109 │ (event: LayoutChangeEvent) => {
110 │ barHeightRef.current = event.nativeEvent.layout.height;
111 │ notifyCoverage();
112 │ },
113 │ [notifyCoverage],
114 │ );
115 │ const handleCardLayout = useCallback(
116 │ (event: LayoutChangeEvent) => {
117 │ cardHeightRef.current = event.nativeEvent.layout.height;
118 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── `cardHeight` cannot be modified
119 │ notifyCoverage();
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
90 │ const cardHeight = useSharedValue(0);
91 │ const notifyCoverage = useCallback(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
92 │ if (!cardCoverage) {
93 │ return;
94 │ }
95 │ const coverage = Math.max(0, cardHeightRef.current - barHeightRef.current);
96 │ if (coverage === cardCoverage.value) {
97 │ return;
98 │ }
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── This modifies `cardCoverage`
101 │ return;
╰────
help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:100:7]
99 │ if (cardCoverage.value === 0) {
100 │ cardCoverage.value = coverage;
· ──────┬─────
· ╰── This modifies `cardCoverage`
101 │ return;
102 │ }
103 │ cardCoverage.value = withTiming(coverage, {
104 │ duration: USER_INPUT_TOGGLE_DURATION_MS,
105 │ easing: Easing.out(Easing.cubic),
106 │ });
107 │ }, [cardCoverage]);
108 │ const handleBarLayout = useCallback(
109 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
110 │ barHeightRef.current = event.nativeEvent.layout.height;
╰────
help: This argument is a function which may reassign or mutate `cardCoverage` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:118:7]
115 │ const handleCardLayout = useCallback(
116 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardHeight` after render
117 │ cardHeightRef.current = event.nativeEvent.layout.height;
118 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── This modifies `cardHeight`
119 │ notifyCoverage();
╰────
help: This argument is a function which may reassign or mutate `cardHeight` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/process/externalLauncher.test.ts:186:12]
185 │
186 │ for (const {} of ["darwin", "linux"] as const) {
· ──
187 │ }
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/process/externalLauncher.test.ts:189:12]
188 │
189 │ for (const {} of [
· ──
190 │ { kind: "browser", folderVerb: "none" },
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/process/externalLauncher.test.ts:311:12]
310 │
311 │ for (const {} of ["rejected", "spawn-error", "stalled"] as const) {
· ──
312 │ }
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/process/externalLauncher.test.ts:314:12]
313 │
314 │ for (const {} of [
· ──
315 │ {
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ 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-unused-vars): Type 'Scope' is imported but never used.
╭─[apps/server/src/provider/ProviderAuthService.ts:15:18]
14 │ import * as Layer from "effect/Layer";
15 │ import type * as Scope from "effect/Scope";
· ──┬──
· ╰── 'Scope' is imported here
16 │ import * as Stream from "effect/Stream";
╰────
help: Consider removing this import.
⚠ 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.
⚠ eslint(no-unused-vars): Variable 'layerTest' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/usage/UsageService.ts:169:7]
168 │
169 │ const layerTest = Layer.succeed(
· ────┬────
· ╰── 'layerTest' is declared here
170 │ UsageService,
╰────
help: Consider removing this declaration.
⚠ 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(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
⚠ 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/usage/UsageService.test.ts:2374:7]
2373 │ let orphanedAt: number | undefined;
2374 │ ╭─▶ for (let interruptAt = 1; interruptAt <= 31; interruptAt += 1) {
2375 │ │ const tasks: Array<() => void> = [];
2376 │ │ const dispatcher: Scheduler.SchedulerDispatcher = {
2377 │ │ scheduleTask: (task) => tasks.push(task),
2378 │ │ flush: () => {
2379 │ │ let task: (() => void) | undefined;
2380 │ │ while ((task = tasks.shift()) !== undefined) task();
2381 │ │ },
2382 │ │ };
2383 │ │
2384 │ │ let requestFiber: Fiber.Fiber<unknown, unknown> | undefined;
2385 │ │ let requestChecks = 0;
2386 │ │ const scheduler: Scheduler.Scheduler = {
2387 │ │ executionMode: "async",
2388 │ │ makeDispatcher: () => dispatcher,
2389 │ │ shouldYield: (fiber) => {
2390 │ │ if (fiber !== requestFiber) return false;
2391 │ │ requestChecks += 1;
2392 │ │ if (requestChecks !== interruptAt) return false;
2393 │ │ fiber.interruptUnsafe();
2394 │ │ return true;
2395 │ │ },
2396 │ │ };
2397 │ │
2398 │ │ const input: UsageSummaryInput = {
2399 │ │ ...WINDOW,
2400 │ │ sinceDay: UsageDay.make("2026-09-01"),
2401 │ │ untilDay: UsageDay.make(`2026-08-${String(interruptAt).padStart(2, "0")}`),
2402 │ │ };
2403 │ │ const first = yield* service
2404 │ │ .readSummary(input)
2405 │ │ .pipe(
2406 │ │ Effect.exit,
2407 │ │ Effect.provideService(Scheduler.Scheduler, scheduler),
2408 │ │ Effect.forkChild,
2409 │ │ );
2410 │ │ requestFiber = first;
2411 │ │ yield* Effect.yieldNow;
2412 │ │ dispatcher.flush();
2413 │ │
2414 │ │ const second = yield* service.readSummary(input).pipe(
2415 │ │ Effect.match({
2416 │ │ onFailure: (error) => error.reason,
2417 │ │ onSuccess: () => "success" as const,
2418 │ │ }),
2419 │ │ Effect.provideService(Scheduler.Scheduler, scheduler),
2420 │ │ Effect.forkChild,
2421 │ │ );
2422 │ │ yield* Effect.yieldNow;
2423 │ │ dispatcher.flush();
2424 │ │ const secondExit = second.pollUnsafe();
2425 │ │ if (secondExit === undefined) {
2426 │ │ second.interruptUnsafe();
2427 │ │ orphanedAt = interruptAt;
2428 │ │ break;
2429 │ │ }
2430 │ │ if (Exit.isFailure(secondExit)) {
2431 │ │ assert.fail("the matching request fiber was interrupted");
2432 │ │ }
2433 │ │ assert.strictEqual(secondExit.value, "invalidWindow");
2434 │ ╰─▶ }
2435 │
╰────
⚠ 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");
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.encodeEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[apps/server/src/serverSettings.test.ts:1718:32]
1717 │ const model = createModelSelection(ProviderInstanceId.make("codex"), "gpt-5.5");
1718 │ const modelJson = yield* Schema.encodeEffect(Schema.fromJsonString(ModelSelection))(model);
· ───────────────────
1719 │ const scriptsJson = yield* Schema.encodeEffect(
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.encodeEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[apps/server/src/serverSettings.test.ts:1719:34]
1718 │ const modelJson = yield* Schema.encodeEffect(Schema.fromJsonString(ModelSelection))(model);
1719 │ const scriptsJson = yield* Schema.encodeEffect(
· ───────────────────
1720 │ Schema.fromJsonString(Schema.Array(ProjectScript)),
╰────
⚠ 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 '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): Identifier 'HostProcess' is imported but never used.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:25:13]
24 │ import * as Schema from "effect/Schema";
25 │ import * as HostProcess from "@t3tools/shared/HostProcess";
· ─────┬─────
· ╰── 'HostProcess' is imported here
26 │
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Variable 'serverConfig' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:124:11]
123 │ const path = yield* Path.Path;
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
· ──────┬─────
· ╰── 'serverConfig' is declared here
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'serverSettings' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderTurnStartService.ts:125:11]
124 │ const serverConfig = yield* ServerConfig.ServerConfig;
125 │ const serverSettings = yield* ServerSettings.ServerSettingsService;
· ───────┬──────
· ╰── 'serverSettings' is declared here
126 │ const gitWorkflow = yield* GitWorkflowService.GitWorkflowService;
╰────
help: Consider removing this declaration.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/thread-work-log.tsx:174:5]
170 │ const expandedAngle = props.collapsedDirection === "right" ? 90 : 180;
171 │ const rotation = useSharedValue(props.expanded ? expandedAngle : 0);
· ────┬───
· ╰── `rotation` originates here
172 │
173 │ useLayoutEffect(() => {
174 │ rotation.value = withTiming(props.expanded ? expandedAngle : 0, {
· ────┬───
· ╰── `rotation` cannot be modified
175 │ duration: THREAD_DISCLOSURE_TRANSITION_MS,
╰────
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(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/threads/thread-work-log.tsx:1252:23]
1251 │ <Text
1252 │ key={`${index}:${line}`}
· ────────────────────────
1253 │ selectable
╰────
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/showcase/ShowcaseCaptureCoordinator.tsx:118:7]
113 │
114 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
115 │ if (orientationSettled) return;
116 │ const orientation = getNativeShowcaseOrientation();
117 │ if (orientation === null) {
118 │ setOrientationSettled(true);
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
119 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:317:7]
305 │
306 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
307 │ if (
308 │ scene === null ||
309 │ requestedScene === null ||
310 │ scene !== requestedScene ||
311 │ !hasFixture ||
312 │ !orientationSettled ||
313 │ !themeApplied ||
314 │ (scene === "agent-activity" && !agentActivityStaged) ||
315 │ !isShowcaseNativeContentReady({ scene, themeId, renderSignal })
316 │ ) {
317 │ setReadyScene(null);
· ──────┬──────
· ╰── Avoid calling setState() directly within an effect
318 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Variable 'lastOutcome' is declared but never used. Unused variables should start with a '_'.
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:123:9]
122 │ let cancelled = false;
123 │ let lastOutcome: string | null = null;
· ─────┬─────
· ╰── 'lastOutcome' is declared here
124 │ void retryShowcaseOperation(async () => applyNativeShowcaseOrientation(orientation), {
╰────
help: Consider removing this declaration.
⚠ 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
⚠ eslint(no-unused-vars): Identifier 'Fiber' is imported but never used.
╭─[apps/server/src/ws.ts:9:13]
8 │ import * as Effect from "effect/Effect";
9 │ import * as Fiber from "effect/Fiber";
· ──┬──
· ╰── 'Fiber' is imported here
10 │ import * as FileSystem from "effect/FileSystem";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'Schedule' is imported but never used.
╭─[apps/server/src/ws.ts:16:13]
15 │ import * as Ref from "effect/Ref";
16 │ import * as Schedule from "effect/Schedule";
· ────┬───
· ╰── 'Schedule' is imported here
17 │ import * as Schema from "effect/Schema";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Variable 'projectSetupScriptRunner' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/ws.ts:1251:13]
1250 │ const usageLimitSources = yield* UsageLimitSources.UsageLimitSources;
1251 │ const projectSetupScriptRunner = yield* ProjectSetupScriptRunner.ProjectSetupScriptRunner;
· ────────────┬───────────
· ╰── 'projectSetupScriptRunner' is declared here
1252 │ const worktreeSetupTracker = yield* WorktreeSetupTracker.WorktreeSetupTracker;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/serverRuntimeStartup.ts:728:7]
727 │
728 │ const layer = layerWithOptions();
· ──┬──
· ╰── 'layer' is declared here
╰────
help: Consider removing this declaration.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/files/FileTreeBrowser.tsx:155:5]
150 │
151 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
152 │ if (!controlledSelectedPath) {
153 │ return;
154 │ }
155 │ setExpandedPaths((current) => {
· ────────┬───────
· ╰── Avoid calling setState() directly within an effect
156 │ const ancestors = ancestorPaths(controlledSelectedPath);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/keyboard/HardwareKeyboardCommandProvider.tsx:116:34]
115 │ return [...commands];
116 │ }, [activeThreadRef, pathname, registrationVersion, navigation]);
· ─────────┬─────────
· ╰── Unnecessary dependency `registrationVersion`
117 │
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Variable 'layerTest' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/telemetry/AnalyticsService.ts:340:7]
339 │
340 │ const layerTest = AnalyticsService.layerTest;
· ────┬────
· ╰── 'layerTest' is declared here
╰────
help: Consider removing this declaration.
⚠ typescript(no-extraneous-class): Unexpected class with only a constructor.
╭─[apps/desktop/src/preview/Manager.test.ts:158:18]
157 │ BrowserWindow: browserWindowConstructor,
158 │ ╭─▶ ClipboardItem: class {
159 │ │ constructor(data: Record<string, unknown>) {
160 │ │ clipboardItemConstructor(data);
161 │ │ }
162 │ ╰─▶ },
163 │ clipboard: {
╰────
help: Try replacing this class with a standalone function or deleting it entirely
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:257:7]
256 │ return () => cancelAnimationFrame(frame);
257 │ }, [props.path, targetIndex]);
· ─────┬────
· ╰── Unnecessary dependency `props.path`
258 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:293:23]
292 │ <SourceText
293 │ key={`${index}:${tokenIndex}`}
· ──────────────────────────────
294 │ style={{
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:309:27]
308 │ return (
309 │ <SourceText key={index}>
· ───────────
310 │ {body}
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(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
⚠ 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.
⚠ 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.`);
╰────
⚠ 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.
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/project/ProjectEnrichmentService.test.ts:28:3]
27 │ ) {
28 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
29 │ │ const available = yield* service.peek(workspaceRoot);
30 │ │ if (predicate(available)) return available;
31 │ │ yield* Effect.yieldNow;
32 │ ╰─▶ }
33 │ return yield* Effect.die(`Project metadata for ${workspaceRoot} was not resolved in time.`);
╰────
⚠ eslint(no-unused-vars): 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-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
⚠ 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.
⚠ 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 │ });
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/client.ts:1269:11]
1268 │ extNotificationHandlers.set(CLIENT_METHODS.mcp_message, (params) =>
1269 │ Schema.decodeUnknownEffect(AcpSchemaV2.MessageMcpNotification)(params).pipe(
· ──────────────────────────
1270 │ Effect.mapError(() => AcpError.AcpRequestError.invalidParams()),
╰────
⚠ 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
⚠ eslint(no-unused-vars): Variable 'layerUnavailable' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/Orchestrator.ts:12232:7]
12231 │
12232 │ const layerUnavailable: Layer.Layer<OrchestratorV2> = Layer.succeed(
· ────────┬───────
· ╰── 'layerUnavailable' is declared here
12233 │ OrchestratorV2,
╰────
help: Consider removing this declaration.
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/effect-acp/src/errors.test.ts:129:28]
128 │ const secret = "acp-summary-secret";
129 │ const cause = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
130 │ Schema.Struct({
╰────
⚠ 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
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/effect-acp/src/protocol.test.ts:500:31]
499 │
500 │ const response = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
501 │ Schema.fromJsonString(JsonRpcErrorResponse),
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/schema.test.ts:18:12]
17 │ const command = { name: "plan", description: "Make a plan", input: { hint: "Task" } };
18 │ expect(Schema.is(V1.AvailableCommand)(command)).toBe(true);
· ─────────
19 │ expect(
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/schema.test.ts:20:7]
19 │ expect(
20 │ Schema.is(V2.AvailableCommand)({ ...command, input: { type: "text", hint: "Task" } }),
· ─────────
21 │ ).toBe(true);
╰────
⚠ 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.
⚠ eslint(no-unused-vars): Variable 'legacyCredentials' is declared but never used. Unused variables should start with a '_'.
╭─[packages/provider-cursor/src/server/credentialStore.test.ts:15:7]
14 │
15 │ const legacyCredentials = {
· ────────┬────────
· ╰── 'legacyCredentials' is declared here
16 │ version: 1 as const,
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Parameter 'stopSessions' is declared but never used. Unused parameters should start with a '_'.
╭─[packages/provider-cursor/src/server/auth.ts:249:20]
248 │ },
249 │ (effect, flow, stopSessions) =>
· ──────┬─────
· ╰── 'stopSessions' is declared here
250 │ effect.pipe(
╰────
help: Consider removing this parameter.
⚠ 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`
⚠ eslint(no-unused-vars): Type 'AuthSessionState' is imported but never used.
╭─[apps/web/src/components/settings/ProviderSettingsPanel.logic.ts:4:8]
3 │ AuthProvidersManageScope,
4 │ type AuthSessionState,
· ────────┬───────
· ╰── 'AuthSessionState' is imported here
5 │ type EnvironmentId,
╰────
help: Consider removing this import.
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/lib/useHoverGesture.ts:8:15]
7 │ () =>
8 │ Gesture.Hover()
· ──┬──
· ╰── `Hover` may be a component
9 │ .manualActivation(true)
╰────
help: Render `Hover` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Hover` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ unicorn(no-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.
Found 0 errors and 357 warnings in 5384 files (9.7s, 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=__76a3e230-a8ea-4336-a735-8e15fcf83273.__actions_cache_2]
Post job cleanup.
Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-d651407d7d0c7ecacd035718e6d120760bb0bb1ea0b966bcda4a8197c80ebc8f, not saving cache.
##[end-action id=__76a3e230-a8ea-4336-a735-8e15fcf83273.__actions_cache_2;outcome=success;conclusion=success;duration_ms=149]
##[start-action display=Setup Vite+;id=__76a3e230-a8ea-4336-a735-8e15fcf83273.__voidzero-dev_setup-vp]
Post job cleanup.
##[end-action id=__76a3e230-a8ea-4336-a735-8e15fcf83273.__voidzero-dev_setup-vp;outcome=success;conclusion=success;duration_ms=93]
##[start-action display=Cache Vite+;id=__76a3e230-a8ea-4336-a735-8e15fcf83273.__actions_cache]
Post job cleanup.
Cache hit occurred on the primary key vite-plus-home-v1-Linux-X64-1.3.0, not saving cache.
##[end-action id=__76a3e230-a8ea-4336-a735-8e15fcf83273.__actions_cache;outcome=success;conclusion=success;duration_ms=112]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/0a767e33-5eba-4b00-8263-6ba6a28d3968' 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: 200
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 456
BLACKSMITH_CHECK_RUN_ID: 119748187318
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