GitHub check
256 KB of 604 KB loaded Download the full log (604 KB)
348 KB of earlier output not loaded
026-10-24T12:44:50.7023145Z · ╰── `loadingVisibility` cannot be modified
270 │ }, [loadingVisibility, props.loading]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:328:5]
325 │ }) {
326 │ const recordingVisibility = useSharedValue(props.phase === "recording" ? 1 : 0);
· ─────────┬─────────
· ╰── `recordingVisibility` originates here
327 │ useLayoutEffect(() => {
328 │ recordingVisibility.value = withTiming(props.phase === "recording" ? 1 : 0, DICTATION_TIMING);
· ─────────┬─────────
· ╰── `recordingVisibility` cannot be modified
329 │ }, [props.phase, recordingVisibility]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/components/VideoPreviewModal.ios.tsx:63:55]
61 │ }, []);
62 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
63 │ if (playbackUrl === null && resolvedUrl !== null) setPlaybackUrl(resolvedUrl);
· ───────┬──────
· ╰── Avoid calling setState() directly within an effect
64 │ }, [playbackUrl, resolvedUrl]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/Stack.tsx:1079:21]
1078 │ <Navigator
1079 │ screenLayout={(props) => <GuardedScreenLayout {...props} />}
· ─────────────────────────────────────────────
1080 │ screenOptions={({ route }) =>
╰────
help: Move this component definition out of the parent component `AdaptiveRootStack` and pass data as props. If you want to allow component creation in props, set `allowAsProps` option to true.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/GlobalVoiceInputControl.tsx:68:5]
65 │ const [expanded, setExpanded] = useState(false);
66 │ const progress = useSharedValue(0);
· ────┬───
· ╰── `progress` originates here
67 │ useEffect(() => {
68 │ progress.value = withTiming(expanded ? 1 : 0, MORPH_TIMING);
· ────┬───
· ╰── `progress` cannot be modified
69 │ }, [expanded, progress]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeEffect(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[apps/server/src/vcs/GitVcsDriverCore.test.ts:1786:34]
1785 │ const stat = branch.files!.find((file) => file.path === path)!;
1786 │ const request = yield* Schema.decodeEffect(ReviewDiffPreviewInput)({
· ───────────────────
1787 │ cwd,
╰────
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:123:7]
118 │
119 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
120 │ if (orientationSettled) return;
121 │ const orientation = getNativeShowcaseOrientation();
122 │ if (orientation === null) {
123 │ setOrientationSettled(true);
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
124 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:304:7]
292 │
293 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
294 │ if (
295 │ scene === null ||
296 │ requestedScene === null ||
297 │ scene !== requestedScene ||
298 │ !hasFixture ||
299 │ !orientationSettled ||
300 │ !themeApplied ||
301 │ (scene === "agent-activity" && !agentActivityStaged) ||
302 │ !isShowcaseNativeContentReady({ scene, themeId, renderSignal })
303 │ ) {
304 │ setReadyScene(null);
· ──────┬──────
· ╰── Avoid calling setState() directly within an effect
305 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Variable 'lastOutcome' is declared but never used. Unused variables should start with a '_'.
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:128:9]
127 │ let cancelled = false;
128 │ let lastOutcome: string | null = null;
· ─────┬─────
· ╰── 'lastOutcome' is declared here
129 │ void retryShowcaseOperation(async () => applyNativeShowcaseOrientation(orientation), {
╰────
help: Consider removing this declaration.
⚠ unicorn(prefer-string-starts-ends-with): Prefer String#startsWith over a regex with a caret.
╭─[apps/server/src/vcs/GitVcsDriverCore.ts:517:11]
516 │ GIT_DIAGNOSTIC_LINE_PATTERN.test(line) ||
517 │ (!/^remote:/.test(line) && SSH_TRANSPORT_REFUSAL_PATTERN.test(line)),
· ───────────────
518 │ )
╰────
help: Replace `/^remote:/.test(line)` with `line.startsWith('remote:')`.
⚠ 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(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:155:7]
154 │ }
155 │ }, [wrappedRender]);
· ──────┬──────
· ╰── Unnecessary dependency `wrappedRender`
156 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:800:42]
799 │ >
800 │ <AdaptiveWorkspaceContext.Provider value={contextValue}>
· ────────────────────
801 │ <WindowHingeContext value={windowHinge}>
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/layout/workspace-inspector-pane.tsx:42:5]
35 │
36 │ const inspectorProgress = useSharedValue(inspectorVisible ? 1 : 0);
· ────────┬────────
· ╰── `inspectorProgress` originates here
37 │ const { renderedInspectorWidth } = props;
38 │ const renderedContentWidth = useSharedValue(inspectorWidth ?? 0);
39 │
40 │ const onClosed = props.onClosed;
41 │ useEffect(() => {
42 │ inspectorProgress.value = withTiming(
· ────────┬────────
· ╰── `inspectorProgress` cannot be modified
43 │ inspectorVisible ? 1 : 0,
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/layout/workspace-inspector-pane.tsx:67:7]
37 │ const { renderedInspectorWidth } = props;
38 │ const renderedContentWidth = useSharedValue(inspectorWidth ?? 0);
· ──────────┬─────────
· ╰── `renderedContentWidth` originates here
39 │
40 │ const onClosed = props.onClosed;
41 │ useEffect(() => {
42 │ inspectorProgress.value = withTiming(
43 │ inspectorVisible ? 1 : 0,
44 │ WORKSPACE_PANE_TIMING,
45 │ (finished) => {
46 │ if (finished === true && !inspectorVisible && onClosed !== undefined) {
47 │ runOnJS(onClosed)();
48 │ }
49 │ },
50 │ );
51 │ const targetWidth = inspectorVisible ? (inspectorWidth ?? 0) : 0;
52 │ renderedInspectorWidth.set(
53 │ resizing ? targetWidth : withTiming(targetWidth, WORKSPACE_PANE_TIMING),
54 │ );
55 │ }, [
56 │ inspectorProgress,
57 │ inspectorVisible,
58 │ inspectorWidth,
59 │ onClosed,
60 │ renderedInspectorWidth,
61 │ resizing,
62 │ ]);
63 │
64 │ useEffect(() => {
65 │ const targetWidth = inspectorWidth ?? 0;
66 │ if (!inspectorVisible || resizing) {
67 │ renderedContentWidth.value = targetWidth;
· ──────────┬─────────
· ╰── `renderedContentWidth` cannot be modified
68 │ return;
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:131:9]
130 │ ) {
131 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
132 │ │ if (subscriptions.length >= count) {
133 │ │ return;
134 │ │ }
135 │ │ yield* Effect.yieldNow;
136 │ ╰─▶ }
137 │ return yield* Effect.die(new Error(`Expected ${count} durable subscriptions.`));
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:252:7]
251 │ yield* SubscriptionRef.set(activeSession, Option.some(session(firstClient)));
252 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 1; attempt += 1) {
253 │ │ yield* Effect.yieldNow;
254 │ ╰─▶ }
255 │ yield* SubscriptionRef.set(activeSession, Option.none());
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:258:7]
257 │
258 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
259 │ │ yield* Effect.yieldNow;
260 │ ╰─▶ }
261 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:322:7]
321 │ );
322 │ ╭─▶ for (let attempt = 0; attempt < 100 && observedFailures.length < 1; attempt += 1) {
323 │ │ yield* Effect.yieldNow;
324 │ ╰─▶ }
325 │
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/client.test.ts:330:7]
329 │ yield* SubscriptionRef.set(activeSession, Option.some(session(secondClient)));
330 │ ╭─▶ for (let attempt = 0; attempt < 100 && subscriptions.length < 2; attempt += 1) {
331 │ │ yield* Effect.yieldNow;
332 │ ╰─▶ }
333 │ yield* Fiber.interrupt(subscriptionFiber);
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/session.test.ts:226:3]
225 │ ) {
226 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
227 │ │ const socket = sockets[index];
228 │ │ if (socket) {
229 │ │ return socket;
230 │ │ }
231 │ │ yield* Effect.yieldNow;
232 │ ╰─▶ }
233 │ return yield* Effect.die(new Error("Expected the RPC protocol to create a websocket."));
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[packages/client-runtime/src/rpc/session.test.ts:240:3]
239 │ ) {
240 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
241 │ │ const request = socket.sent.map((message) => decodeJson(message)).filter(isRpcRequest)[index];
242 │ │ if (request) {
243 │ │ return request;
244 │ │ }
245 │ │ yield* Effect.yieldNow;
246 │ ╰─▶ }
247 │ return yield* Effect.die(new Error("Expected the RPC protocol to send a request."));
╰────
⚠ 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
⚠ 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.
⚠ 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 │
╰────
help: Remove empty braces
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:100:85]
99 │ const startEditor = startScheduledTaskEditor;
100 │ const resetEditor = useCallback(() => startEditor(defaultEditor), [defaultEditor, startEditor]);
· ─────┬─────
· ╰── Unnecessary dependency `startEditor`
101 │ const readEditor = useCallback(
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/settings/scheduled-task-editor.tsx:121:7]
120 │ setEditor,
121 │ startEditor,
· ─────┬─────
· ╰── Unnecessary dependency `startEditor`
122 │ hasChanges,
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:119:10]
117 │
118 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
119 │ void refreshNotifications();
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
120 │ const subscription = AppState.addEventListener("change", (state) => {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:128:7]
125 │
126 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
127 │ if (!isLoaded) {
128 │ setLiveActivityStatus("checking");
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
129 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Function 'nonEmptyString' is declared but never used.
╭─[packages/client-runtime/src/work-log/presentation.ts:237:10]
236 │
237 │ function nonEmptyString(value: unknown): string | null {
· ───────┬──────
· ╰── 'nonEmptyString' is declared here
238 │ return typeof value === "string" && value.trim().length > 0 ? value : null;
╰────
help: Consider removing this declaration.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/workspace/WorkspaceToolbar.ios.tsx:114:33]
113 │ return () => cancelAnimationFrame(frame);
114 │ }, [restoreSearch, tabActive, bottomSearch]);
· ──────┬─────
· ╰── Unnecessary dependency `bottomSearch`
115 │ const composeButton = nativeToolbarCompose ? (
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[apps/server/src/provider/Drivers/CodexDriver.test.ts:466:14]
465 │
466 │ for (const {} of ["direct", "wrapper"] as const) {
· ──
467 │ }
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ eslint(no-unused-vars): Variable 'layerFromProviderAdapter' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ProviderAdapterRegistry.ts:346:7]
345 │
346 │ const layerFromProviderAdapter: Layer.Layer<
· ────────────┬───────────
· ╰── 'layerFromProviderAdapter' is declared here
347 │ ProviderAdapterRegistryV2,
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'layerDaemon' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/EffectWorker.ts:914:7]
913 │
914 │ const layerDaemon: Layer.Layer<never, never, OrchestrationEffectWorkerV2> = Layer.effectDiscard(
· ─────┬─────
· ╰── 'layerDaemon' is declared here
915 │ runDaemon.pipe(Effect.forkScoped),
╰────
help: Consider removing this declaration.
⚠ eslint(no-new): Do not use 'new' for side effects.
╭─[apps/server/src/mcp/McpToolAccess.test.ts:168:3]
167 │ // @ts-expect-error a declaration constructed directly
168 │ new McpToolAccess.Declaration(unchecked);
· ─────────────────────────────
169 │ // @ts-expect-error a handlers layer built outside McpToolAccess
╰────
help: Assign the result of 'new' to a variable or compare it to a reference.
⚠ 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.
⚠ eslint(no-unused-vars): Type 'ThreadRunSummary' is imported but never used.
╭─[apps/web/src/types.ts:22:3]
21 │ EnvironmentThreadShell,
22 │ ThreadRunSummary,
· ────────┬───────
· ╰── 'ThreadRunSummary' is imported here
23 │ ThreadRuntimeSummary,
╰────
help: Consider removing this import.
⚠ 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(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
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:259:28]
258 │ visit(parser.parse(markdown), false, false);
259 │ for (const edit of edits.reverse())
· ───────
260 │ 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:290:28]
289 │ visit(parser.parse(markdown));
290 │ for (const edit of edits.reverse())
· ───────
291 │ 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:344:38]
343 │ visit(parser.parse(markdown));
344 │ for (const lineStart of lineStarts.reverse()) {
· ───────
345 │ // The header row may be a lazy line without its container markers (`>` or list indent),
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/hooks/useThreadActions.ts:821:56]
820 │ const resolved = resolveThreadTarget(target);
821 │ if (resolved && !canSnooze(resolved.thread, { now: new Date().toISOString() })) {
· ─────┬────
· ╰── Cannot call impure function
822 │ return AsyncResult.failure(
╰────
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/hooks/useThreadActions.ts:709:46]
708 │ const wokeAt = resolved
709 │ ? threadWokeAt(resolved.thread, { now: new Date().toISOString() })
· ─────┬────
· ╰── Cannot call impure function
710 │ : null;
╰────
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
⚠ 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): 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.
⚠ 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:2615:7]
2614 │ let orphanedAt: number | undefined;
2615 │ ╭─▶ for (let interruptAt = 1; interruptAt <= 31; interruptAt += 1) {
2616 │ │ const tasks: Array<() => void> = [];
2617 │ │ const dispatcher: Scheduler.SchedulerDispatcher = {
2618 │ │ scheduleTask: (task) => tasks.push(task),
2619 │ │ flush: () => {
2620 │ │ let task: (() => void) | undefined;
2621 │ │ while ((task = tasks.shift()) !== undefined) task();
2622 │ │ },
2623 │ │ };
2624 │ │
2625 │ │ let requestFiber: Fiber.Fiber<unknown, unknown> | undefined;
2626 │ │ let requestChecks = 0;
2627 │ │ const scheduler: Scheduler.Scheduler = {
2628 │ │ executionMode: "async",
2629 │ │ makeDispatcher: () => dispatcher,
2630 │ │ shouldYield: (fiber) => {
2631 │ │ if (fiber !== requestFiber) return false;
2632 │ │ requestChecks += 1;
2633 │ │ if (requestChecks !== interruptAt) return false;
2634 │ │ fiber.interruptUnsafe();
2635 │ │ return true;
2636 │ │ },
2637 │ │ };
2638 │ │
2639 │ │ const input: UsageSummaryInput = {
2640 │ │ ...WINDOW,
2641 │ │ sinceDay: UsageDay.make("2026-09-01"),
2642 │ │ untilDay: UsageDay.make(`2026-08-${String(interruptAt).padStart(2, "0")}`),
2643 │ │ };
2644 │ │ const first = yield* service
2645 │ │ .readSummary(input)
2646 │ │ .pipe(
2647 │ │ Effect.exit,
2648 │ │ Effect.provideService(Scheduler.Scheduler, scheduler),
2649 │ │ Effect.forkChild,
2650 │ │ );
2651 │ │ requestFiber = first;
2652 │ │ yield* Effect.yieldNow;
2653 │ │ dispatcher.flush();
2654 │ │
2655 │ │ const second = yield* service.readSummary(input).pipe(
2656 │ │ Effect.match({
2657 │ │ onFailure: (error) => error.reason,
2658 │ │ onSuccess: () => "success" as const,
2659 │ │ }),
2660 │ │ Effect.provideService(Scheduler.Scheduler, scheduler),
2661 │ │ Effect.forkChild,
2662 │ │ );
2663 │ │ yield* Effect.yieldNow;
2664 │ │ dispatcher.flush();
2665 │ │ const secondExit = second.pollUnsafe();
2666 │ │ if (secondExit === undefined) {
2667 │ │ second.interruptUnsafe();
2668 │ │ orphanedAt = interruptAt;
2669 │ │ break;
2670 │ │ }
2671 │ │ if (Exit.isFailure(secondExit)) {
2672 │ │ assert.fail("the matching request fiber was interrupted");
2673 │ │ }
2674 │ │ assert.strictEqual(secondExit.value, "invalidWindow");
2675 │ ╰─▶ }
2676 │
╰────
⚠ 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/ThreadArrangementSheet.tsx:261:5]
259 │ .join("|");
260 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
261 │ stop();
· ──┬─
· ╰── Avoid calling setState() directly within an effect
262 │ }, [orderVersion]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:261:5]
260 │ useEffect(() => {
261 │ stop();
· ──┬─
· ╰── Missing dependency `stop`
262 │ }, [orderVersion]);
· ──────┬─────
· ╰── Unnecessary dependency `orderVersion`
263 │ useEffect(
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:96:9]
95 │ const latest = useRef(props);
96 │ latest.current = props;
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
97 │ const gesture = useMemo(
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:104:18]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───────────────┬──────────────
· ╰── Passing a ref to a function may read its value during render
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:105:19]
104 │ .onStart(() => latest.current.onStart())
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:106:16]
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
· ──────────────────────────┬─────────────────────────
· ╰── Passing a ref to a function may read its value during render
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:107:21]
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
· ───────────────────────┬──────────────────────
· ╰── Passing a ref to a function may read its value during render
108 │ [props.disabled],
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:249:9]
248 │ const latest = useRef({ rows, planners, moveThread });
249 │ latest.current = { rows, planners, moveThread };
· ───┬──────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
250 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:247:22]
246 │ const [preview, setPreview] = useState<Drag | null>(null);
247 │ const translateY = useRef(new Animated.Value(0)).current;
· ──────────────────┬──────────────────
· ╰── Cannot access ref value during render
248 │ const latest = useRef({ rows, planners, moveThread });
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:324:16]
323 │ update(0);
324 │ let last = performance.now();
· ────────┬────────
· ╰── Cannot call impure function
325 │ const tick = () => {
╰────
help: `performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:99:15]
98 │ () =>
99 │ Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
100 │ .enabled(!props.disabled)
╰────
help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(memo-dependencies): Found missing memoization dependencies
╭─[apps/mobile/src/features/threads/ThreadArrangementSheet.tsx:108:5]
103 │ .runOnJS(true)
104 │ .onStart(() => latest.current.onStart())
· ───┬──
· ╰── Missing dependency `latest`. Refs, setState functions, and other "stable" values generally do not need to be added as dependencies, but this variable may change over time to point to different values
105 │ .onUpdate((event) => latest.current.onMove(event.translationY))
106 │ .onEnd((event) => latest.current.onMove(event.translationY))
107 │ .onFinalize((_, success) => latest.current.onEnd(!success)),
108 │ [props.disabled],
· ────────┬───────
· ╰── This dependency list is missing values used by the callback
109 │ );
╰────
help: Missing dependencies can cause a value to update less often than it should, resulting in stale UI
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:406:5]
404 │
405 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
406 │ setInspectorSelection((current) => {
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
407 │ if (props.renderInspector === undefined) {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:534:24]
533 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
534 │ ╭─▶ const GitInspector = () => (
535 │ │ <GitOverviewSheet
536 │ │ headerInset={inspectorHeaderInset}
537 │ │ presentation="inspector"
538 │ │ route={{ params: { environmentId: environmentId!, threadId: threadId! } }}
539 │ │ />
540 │ ╰─▶ );
541 │ const FilesInspector = () =>
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(no-unstable-nested-components): Do not define components during render.
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:541:26]
540 │ );
541 │ ╭─▶ const FilesInspector = () =>
542 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
543 │ │ <ThreadFileNavigatorPane
544 │ │ cwd={selectedThreadCwd}
545 │ │ environmentId={selectedThread.environmentId}
546 │ │ headerInset={inspectorHeaderInset}
547 │ │ projectName={selectedThreadProject?.title ?? "Files"}
548 │ │ selectedPath={null}
549 │ │ onSelectFile={handleSelectInspectorFile}
550 │ │ />
551 │ ╰─▶ ) : null;
552 │ const RouteInspector = () => props.renderInspector?.(inspectorHeaderInset);
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/pull-requests/PullRequestRouteScreen.tsx:333:7]
328 │ };
329 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
330 │ if (!guidesEnabled && section === "guide") {
331 │ requestedSection.current = "overview";
332 │ currentScrollOffset.current = scrollOffsets.current.overview ?? -insets.top;
333 │ setSection("overview");
· ─────┬────
· ╰── Avoid calling setState() directly within an effect
334 │ }
╰────
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:335:6]
330 │ if (!guidesEnabled && section === "guide") {
331 │ 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
332 │ 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
333 │ setSection("overview");
334 │ }
335 │ }, [guidesEnabled, section, insets.top]);
· ──────────────────┬─────────────────
· ╰── This dependency list is missing values used by the callback
336 │ 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:877:6]
860 │ if (
861 │ 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
862 │ lastSelection.current.id === route.params.fileSelectionId
863 │ )
864 │ return;
865 │ lastSelection.current = { path: route.params.path, id: route.params.fileSelectionId };
866 │ if (route.params.focus) navigation.setParams({ focus: undefined });
867 │ setJumpPath(route.params.path);
868 │ setSelectedRowId(null);
869 │ jumpStarted.current = false;
870 │ const file = data.files.find((entry) => entry.path === route.params.path);
871 │ 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
872 │ setCollapsedIds((ids) => ids.filter((id) => id !== file.id));
873 │ jumpStarted.current = true;
874 │ void nativeView.current.scrollToFile(file.id, false).catch(() => {
875 │ jumpStarted.current = false;
876 │ });
877 │ }, [route.params.path, route.params.fileSelectionId, route.params.focus, data.files, navigation]);
· ──────────────────────────────────────────────┬──────────────────────────────────────────────
· ╰── This dependency list is missing values used by the callback
878 │ 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
⚠ 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:237:17]
236 │ const requiredScopesForSettingsUpdate = (payload: unknown) => {
237 │ const input = Schema.decodeUnknownSync(SettingsUpdate)(payload);
· ────────────────────────
238 │ 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:256:26]
255 │ if (method === WS_METHODS.assetsCreateUrl) {
256 │ const { resource } = Schema.decodeUnknownSync(AssetCreateUrlInput)(payload);
· ────────────────────────
257 │ return [
╰────
⚠ 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.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/PendingUserInputCard.tsx:94:5]
83 │
84 │ const cardCoverage = props.cardCoverage;
· ──────┬─────
· ╰── `cardCoverage` originates here
85 │ const barHeightRef = useRef(0);
86 │ const cardHeightRef = useRef(0);
87 │ const cardHeight = useSharedValue(0);
88 │ const notifyCoverage = useCallback(() => {
89 │ if (!cardCoverage) {
90 │ return;
91 │ }
92 │ // The card resizes with the keyboard every frame, so easing each sample would leave the
93 │ // feed inset and floating controls trailing it.
94 │ cardCoverage.value = Math.max(0, cardHeightRef.current - barHeightRef.current);
· ──────┬─────
· ╰── `cardCoverage` cannot be modified
95 │ }, [cardCoverage]);
╰────
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:106:7]
86 │ const cardHeightRef = useRef(0);
87 │ const cardHeight = useSharedValue(0);
· ─────┬────
· ╰── `cardHeight` originates here
88 │ const notifyCoverage = useCallback(() => {
89 │ if (!cardCoverage) {
90 │ return;
91 │ }
92 │ // The card resizes with the keyboard every frame, so easing each sample would leave the
93 │ // feed inset and floating controls trailing it.
94 │ cardCoverage.value = Math.max(0, cardHeightRef.current - barHeightRef.current);
95 │ }, [cardCoverage]);
96 │ const handleBarLayout = useCallback(
97 │ (event: LayoutChangeEvent) => {
98 │ barHeightRef.current = event.nativeEvent.layout.height;
99 │ notifyCoverage();
100 │ },
101 │ [notifyCoverage],
102 │ );
103 │ const handleCardLayout = useCallback(
104 │ (event: LayoutChangeEvent) => {
105 │ cardHeightRef.current = event.nativeEvent.layout.height;
106 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── `cardHeight` cannot be modified
107 │ 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:94:5]
87 │ const cardHeight = useSharedValue(0);
88 │ const notifyCoverage = useCallback(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
89 │ if (!cardCoverage) {
90 │ return;
91 │ }
92 │ // The card resizes with the keyboard every frame, so easing each sample would leave the
93 │ // feed inset and floating controls trailing it.
94 │ cardCoverage.value = Math.max(0, cardHeightRef.current - barHeightRef.current);
· ──────┬─────
· ╰── This modifies `cardCoverage`
95 │ }, [cardCoverage]);
╰────
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:94:5]
93 │ // feed inset and floating controls trailing it.
94 │ cardCoverage.value = Math.max(0, cardHeightRef.current - barHeightRef.current);
· ──────┬─────
· ╰── This modifies `cardCoverage`
95 │ }, [cardCoverage]);
96 │ const handleBarLayout = useCallback(
97 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardCoverage` after render
98 │ 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:106:7]
103 │ const handleCardLayout = useCallback(
104 │ (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `cardHeight` after render
105 │ cardHeightRef.current = event.nativeEvent.layout.height;
106 │ cardHeight.value = event.nativeEvent.layout.height;
· ─────┬────
· ╰── This modifies `cardHeight`
107 │ notifyCoverage();
╰────
help: This argument is a function which may reassign or mutate `cardHeight` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:444:5]
434 │ : null;
435 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
436 │ if (
437 │ props.active === false ||
438 │ activeDraftKey !== null ||
439 │ editingPendingTask !== null ||
440 │ selectedProject === null
441 │ ) {
442 │ return;
443 │ }
444 │ setActiveDraftKey(
· ────────┬────────
· ╰── Avoid calling setState() directly within an effect
445 │ createNewTaskDraft({
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/threads/new-task-flow-provider.tsx:1244:36]
1243 │ <ActiveNewTaskContext value={activeNewTask}>
1244 │ <NewTaskFlowContext.Provider value={value}>{props.children}</NewTaskFlowContext.Provider>
· ─────────────
1245 │ </ActiveNewTaskContext>
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ eslint(no-unused-vars): Variable 'useDragRegion' is declared but never used. Unused variables should start with a '_'.
╭─[apps/web/src/components/preview/PreviewPanelShell.tsx:61:9]
60 │ ) {
61 │ const useDragRegion = isElectron && props.mode !== "sheet" && props.mode !== "embedded";
· ──────┬──────
· ╰── 'useDragRegion' is declared here
62 │ const isInline = props.mode === "inline";
╰────
help: Consider removing this declaration.
⚠ 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/scheduledTasks/ScheduledTaskService.webhook.test.ts:521:13]
520 │ })).delivery;
521 │ ╭─▶ while (delivery.outcome === "accepted") {
522 │ │ yield* Effect.yieldNow;
523 │ │ delivery = (yield* service.getWebhookDelivery({
524 │ │ id: task.id,
525 │ │ deliveryId: deliveryId!,
526 │ │ })).delivery;
527 │ ╰─▶ }
528 │ assert.equal(delivery.outcome, "dispatch_failed");
╰────
⚠ 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(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:773:7]
772 │ if (settingsSheetPresentation.isActive) {
773 │ settingsRoutePresentation.present(settingsRouteSession);
· ────────────┬────────────
· ╰── Missing dependency `settingsRoutePresentation`
774 │ }
775 │ }, [settingsRoutePresentation.present, settingsRouteSession, settingsSheetPresentation.isActive]);
· ────────────────┬────────────────
· ╰── Overly precise dependency `settingsRoutePresentation.present`, use `settingsRoutePresentation` instead
776 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/ThreadComposer.tsx:391:5]
387 │ typeof props.style.borderRadius === "number" ? props.style.borderRadius : 0;
388 │ const animatedBorderRadius = useSharedValue(targetBorderRadius);
· ──────────┬─────────
· ╰── `animatedBorderRadius` originates here
389 │ const shouldAnimate = props.animateLayout !== false && Platform.OS !== "android";
390 │ useLayoutEffect(() => {
391 │ animatedBorderRadius.value = shouldAnimate
· ──────────┬─────────
· ╰── `animatedBorderRadius` cannot be modified
392 │ ? withTiming(targetBorderRadius, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CommandPaletteThreadItems.tsx:152:58]
151 │ if (threadSearchQuery.trim().length > 0 && !threadSearchQuery.startsWith(">") && !isOpen) {
152 │ claimThreadOpen(thread.environmentId, thread.id, Date.now());
· ─────┬────
· ╰── Cannot call impure function
153 │ }
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:257:7]
256 │ return () => cancelAnimationFrame(frame);
257 │ }, [props.path, targetIndex]);
· ─────┬────
· ╰── Unnecessary dependency `props.path`
258 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:293:23]
292 │ <SourceText
293 │ key={`${index}:${tokenIndex}`}
· ──────────────────────────────
294 │ style={{
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/files/SourceFileSurface.tsx:309:27]
308 │ return (
309 │ <SourceText key={index}>
· ───────────
310 │ {body}
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:217:7]
213 │ };
214 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
215 │ const inserted = ownerKey ? readComposerDraftSelection(ownerKey, draftMessage) : null;
216 │ if (inserted) {
217 │ setSelection((current) =>
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
218 │ current.start === inserted.start && current.end === inserted.end ? current : inserted,
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:298:7]
286 │ }, [hasWorkspaceSnapshot]);
287 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
288 │ if (!environmentId || !projectCwd || !selectedProviderInstanceId) return;
289 │ const key = `${environmentId}:${selectedProviderInstanceId}:${projectCwd}`;
290 │ const now = Date.now();
291 │ const lastRequest = workspaceRefreshKeyRef.current;
292 │ if (
293 │ lastRequest?.key === key &&
294 │ now - lastRequest.requestedAt < PROVIDER_WORKSPACE_SNAPSHOT_TTL_MS
295 │ )
296 │ return;
297 │ if (hasCurrentProviderWorkspaceSnapshot(selectedProviderStatus, projectCwd, now)) {
298 │ setWorkspaceRefreshRetry(null);
· ────────────┬───────────
· ╰── Avoid calling setState() directly within an effect
299 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/use-composer-command-menu.ts:328:5]
327 │ }, [
328 │ draftMessage,
· ──────┬─────
· ╰── Unnecessary dependency `draftMessage`
329 │ environmentId,
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Function 'describeSchedule' is declared but never used.
╭─[apps/server/src/scheduledTasks/Schedule.ts:79:10]
78 │
79 │ function describeSchedule(schedule: ScheduledTaskSchedule): string {
· ────────┬───────
· ╰── 'describeSchedule' is declared here
80 │ if (schedule.type === "webhook") return "On webhook";
╰────
help: Consider removing this declaration.
⚠ 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
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:361:7]
355 │ }, [cancelledIncomingShareId, navigation, props.incomingShareId]);
356 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
357 │ if (!isReturningToProjectPicker) {
358 │ return;
359 │ }
360 │ if (requestedInitialProjectAvailable) {
361 │ setIsReturningToProjectPicker(false);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
362 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:504:9]
447 │
448 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
449 │ if (props.pendingTaskId || props.draftId) {
450 │ return;
451 │ }
452 │ if (lastInitialProjectRefRef.current !== props.initialProjectRef) {
453 │ lastInitialProjectRefRef.current = props.initialProjectRef;
454 │ appliedInitialProjectKeyRef.current = null;
455 │ }
456 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
457 │ const initialProjectId = props.initialProjectRef?.projectId;
458 │ if (initialEnvironmentId && initialProjectId) {
459 │ const directProject =
460 │ projects.find(
461 │ (project) =>
462 │ project.environmentId === initialEnvironmentId && project.id === initialProjectId,
463 │ ) ?? null;
464 │
465 │ if (directProject) {
466 │ // Apply the route's project once. Re-applying on every change would
467 │ // instantly revert environment/project switches made in the picker.
468 │ const directProjectKey = `${directProject.environmentId}:${directProject.id}`;
469 │ if (appliedInitialProjectKeyRef.current === directProjectKey) {
470 │ return;
471 │ }
472 │ if (props.initialProjectRef?.branch) {
473 │ if (
474 │ selectedProject?.environmentId !== directProject.environmentId ||
475 │ selectedProject.id !== directProject.id
476 │ ) {
477 │ setProject(directProject);
478 │ return;
479 │ }
480 │ if (!flow.draftKey) return;
481 │ // The route completes checkout before mounting this composer. Local
482 │ // mode reuses an existing worktree; worktree mode would create another.
483 │ updateComposerDraftSettings(flow.draftKey, {
484 │ workspaceSelection: {
485 │ mode: "local",
486 │ branch: props.initialProjectRef.branch,
487 │ worktreePath: props.initialProjectRef.worktreePath ?? null,
488 │ startFromOrigin: false,
489 │ },
490 │ });
491 │ }
492 │ appliedInitialProjectKeyRef.current = directProjectKey;
493 │ if (
494 │ selectedProject?.environmentId === directProject.environmentId &&
495 │ selectedProject.id === directProject.id
496 │ ) {
497 │ return;
498 │ }
499 │ setProject(directProject);
500 │ return;
501 │ }
502 │
503 │ if (projects.length > 0) {
504 │ setIsReturningToProjectPicker(true);
· ──────────────┬──────────────
· ╰── Avoid calling setState() directly within an effect
505 │ }
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:604:5]
545 │
546 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
547 │ const shareId = props.incomingShareId;
548 │ const draftKey = flow.draftKey;
549 │ const destinationProject = selectedProject;
550 │ const initialEnvironmentId = props.initialProjectRef?.environmentId;
551 │ const initialProjectId = props.initialProjectRef?.projectId;
552 │ const selectedProjectMatchesRoute =
553 │ !initialEnvironmentId ||
554 │ !initialProjectId ||
555 │ (destinationProject?.environmentId === initialEnvironmentId &&
556 │ destinationProject.id === initialProjectId);
557 │ if (
558 │ !shareId ||
559 │ !draftKey ||
560 │ !destinationProject ||
561 │ !selectedProjectMatchesRoute ||
562 │ cancelledIncomingShareId === shareId
563 │ ) {
564 │ return;
565 │ }
566 │ const importKey = `${shareId}:${draftKey}`;
567 │ if (
568 │ startedShareImportKeyRef.current === importKey ||
569 │ cancellingShareImportKeyRef.current === importKey
570 │ ) {
571 │ return;
572 │ }
573 │
574 │ if (!incomingShare) {
575 │ if (isIncomingShareUnavailable && alertedUnavailableIncomingShareIdRef.current !== shareId) {
576 │ alertedUnavailableIncomingShareIdRef.current = shareId;
577 │ Dialog.alert(
578 │ "Shared content unavailable",
579 │ "The shared content is no longer in the inbox. You can continue editing this task draft.",
580 │ );
581 │ }
582 │ return;
583 │ }
584 │
585 │ if (
586 │ incomingShare.attachments.some((attachment) => attachment.type === "file") &&
587 │ selectedEnvironmentServerConfig === null
588 │ ) {
589 │ return;
590 │ }
591 │
592 │ if (alertedUnavailableIncomingShareIdRef.current === shareId) {
593 │ alertedUnavailableIncomingShareIdRef.current = null;
594 │ }
595 │ startedShareImportKeyRef.current = importKey;
596 │ const draftBackup =
597 │ shareImportDraftBackupRef.current.get(importKey) ?? getComposerDraftSnapshot(draftKey);
598 │ shareImportDraftBackupRef.current.set(importKey, draftBackup);
599 │ const importToken = Symbol(importKey);
600 │ let didReserveShare = false;
601 │ let didConsumeShare = false;
602 │ let needsDraftRestore = false;
603 │ activeShareImportTokenRef.current = importToken;
604 │ setImportingShareKey(importKey);
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
605 │ void (async () => {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:524:5]
523 │ props.initialProjectRef,
524 │ props.incomingShareId,
· ──────────┬──────────
· ╰── Unnecessary dependency `props.incomingShareId`
525 │ props.pendingTaskId,
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:543:5]
542 │ loadedBranchesProjectKeyRef.current = projectKey;
543 │ flow.loadBranches();
· ──┬─
· ╰── Missing dependency `flow`
544 │ }, [flow.loadBranches, selectedProject]);
· ────────┬────────
· ╰── Overly precise dependency `flow.loadBranches`, use `flow` instead
545 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskDraftScreen.tsx:766:5]
765 │ flow.draftKey,
766 │ hasImportedIncomingShare,
· ────────────┬───────────
· ╰── Unnecessary dependency `hasImportedIncomingShare`
767 │ incomingShare,
768 │ isIncomingShareInboxLoading,
· ─────────────┬─────────────
· ╰── Unnecessary dependency `isIncomingShareInboxLoading`
769 │ isIncomingShareUnavailable,
770 │ props.incomingShareId,
771 │ props.initialProjectRef?.environmentId,
772 │ props.initialProjectRef?.projectId,
773 │ releaseShareReservation,
774 │ reserveShare,
775 │ selectedEnvironmentServerConfig,
776 │ selectedProject,
777 │ shareImportAttempt,
· ─────────┬────────
· ╰── Unnecessary dependency `shareImportAttempt`
778 │ ]);
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-empty-pattern): Empty array binding pattern
╭─[apps/server/src/pullRequest/PullRequestService.test.ts:1437:12]
1436 │
1437 │ for (const [] of [
· ──
1438 │ ["github", "github.com"],
╰────
help: Passing non-iterable values (null, undefined, numbers, booleans, etc.) will result in a runtime error because these values are not iterable.
⚠ react(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:473:19]
472 │ onFilters,
473 │ authorOptions = [],
· ──
474 │ 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:474:18]
473 │ authorOptions = [],
474 │ labelOptions = [],
· ──
475 │ optionScope,
╰────
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 '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(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/ThreadMarkdownImage.tsx:57:5]
55 │
56 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
57 │ setDecodedSize(null);
· ───────┬──────
· ╰── Avoid calling setState() directly within an effect
58 │ }, [props.sourceKey]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:61:5]
59 │
60 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
61 │ setFailedUri(null);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
62 │ }, [props.uri]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:7:10]
6 │ import { parse, SvgAst, type JsxAST } from "react-native-svg";
7 │ import { ActivityIndicator, Pressable, StyleSheet, View, type ViewStyle } from "react-native";
· ────────┬────────
· ╰── 'ActivityIndicator' is imported here
8 │
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:58:7]
57 │ setDecodedSize(null);
58 │ }, [props.sourceKey]);
· ───────┬───────
· ╰── Unnecessary dependency `props.sourceKey`
59 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadMarkdownImage.tsx:62:7]
61 │ setFailedUri(null);
62 │ }, [props.uri]);
· ────┬────
· ╰── Unnecessary dependency `props.uri`
63 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:111:5]
107 │ );
108 │ const separationProgress = useSharedValue(props.showScrollToEnd ? 1 : 0);
· ─────────┬────────
· ╰── `separationProgress` originates here
109 │
110 │ useEffect(() => {
111 │ separationProgress.value = withTiming(props.showScrollToEnd ? 1 : 0, CONTROL_TIMING);
· ─────────┬────────
· ╰── `separationProgress` cannot be modified
112 │ }, [props.showScrollToEnd, separationProgress]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
128 │ // and repeatedly retargets the animation as it grows.
129 │ const capsuleWidth = useSharedValue<number | null>(null);
· ──────┬─────
· ╰── `capsuleWidth` originates here
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
· ──────┬─────
· ╰── `capsuleWidth` cannot be modified
139 │ };
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
128 │ // and repeatedly retargets the animation as it grows.
129 │ const capsuleWidth = useSharedValue<number | null>(null);
· ──────┬─────
· ╰── `capsuleWidth` originates here
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
139 │ };
140 │ const hasStatus = props.status !== null;
141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
142 │ useEffect(() => {
143 │ if (!hasStatus) {
144 │ measuredWidthRef.current = null;
145 │ capsuleWidth.value = null;
· ──────┬─────
· ╰── `capsuleWidth` cannot be modified
146 │ }
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:145:7]
141 │ const hasCapsule = hasStatus || hasQueue || hasAgents || hasPreview;
142 │ useEffect(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
143 │ if (!hasStatus) {
144 │ measuredWidthRef.current = null;
145 │ capsuleWidth.value = null;
· ──────┬─────
· ╰── This modifies `capsuleWidth`
146 │ }
╰────
help: This argument is a function which may reassign or mutate `capsuleWidth` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/threads/floating-working-control.tsx:138:5]
130 │ const measuredWidthRef = useRef<number | null>(null);
131 │ const handleLabelLayout = (event: LayoutChangeEvent) => {
· ───────────────┬───────────────
· ╰── This function may (indirectly) reassign or modify `capsuleWidth` after render
132 │ const width = event.nativeEvent.layout.width;
133 │ if (width === measuredWidthRef.current) {
134 │ return;
135 │ }
136 │ const first = measuredWidthRef.current === null;
137 │ measuredWidthRef.current = width;
138 │ capsuleWidth.value = first ? width : withTiming(width, CONTROL_TIMING);
· ──────┬─────
· ╰── This modifies `capsuleWidth`
139 │ };
╰────
help: This argument is a function which may reassign or mutate `capsuleWidth` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2143:5]
2141 │ );
2142 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
2143 │ setExpandedVideo(null);
· ────────┬───────
· ╰── Avoid calling setState() directly within an effect
2144 │ setExpandedFile(null);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2644:9]
2635 │ const stopFollowingEnd = useEffectEvent(() => setEndFollow(false));
2636 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
2637 │ if (!jumpToMessageId || loadedListKey !== listMountKey) return;
2638 │ const index = presentedFeed.findIndex(
2639 │ (entry) => entry.type === "message" && entry.id === jumpToMessageId,
2640 │ );
2641 │ if (index === -1) {
2642 │ const runId = messageFoldRunId(props.feed, jumpToMessageId);
2643 │ if (runId && !expandedTurnIds.has(runId)) {
2644 │ setInteractionState((current) => ({
· ─────────┬─────────
· ╰── Avoid calling setState() directly within an effect
2645 │ ...current,
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Identifier 'isMarkdownFileLinkLabel' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:66:10]
65 │ import { resolveAssetUrl } from "@t3tools/client-runtime/state/assets";
66 │ import { isMarkdownFileLinkLabel } from "@t3tools/shared/markdownLinks";
· ───────────┬───────────
· ╰── 'isMarkdownFileLinkLabel' is imported here
67 │ import { formatAttachmentSize } from "@t3tools/client-runtime/state/attachments";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'createContext' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:92:3]
91 │ import {
92 │ createContext,
· ──────┬──────
· ╰── 'createContext' is imported here
93 │ memo,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ActivityIndicator' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:108:3]
107 │ import {
108 │ ActivityIndicator,
· ────────┬────────
· ╰── 'ActivityIndicator' is imported here
109 │ Image,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'ScrollView' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:115:3]
114 │ Pressable,
115 │ ScrollView,
· ─────┬────
· ╰── 'ScrollView' is imported here
116 │ StyleSheet,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'NativeText' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:117:11]
116 │ StyleSheet,
117 │ Text as NativeText,
· ─────┬────
· ╰── 'NativeText' is imported here
118 │ type ColorValue,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'tryOpenExternalUrl' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:140:10]
139 │ import { copyTextWithHaptic } from "../../lib/copyTextWithHaptic";
140 │ import { tryOpenExternalUrl } from "../../lib/openExternalUrl";
· ─────────┬────────
· ╰── 'tryOpenExternalUrl' is imported here
141 │ import { downloadAndShareAttachment } from "../../lib/attachmentDownload";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'faviconUrlForOrigin' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:143:10]
142 │ import { hasWideMarkdownBlock } from "../../lib/wideMarkdownBlocks";
143 │ import { faviconUrlForOrigin } from "@t3tools/shared/favicon";
· ─────────┬─────────
· ╰── 'faviconUrlForOrigin' is imported here
144 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'MediaVideoPlayer' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:157:10]
156 │ import { VideoAttachmentTile } from "../../components/VideoAttachmentTile";
157 │ import { MediaVideoPlayer } from "../../components/MediaVideoPlayer";
· ────────┬───────
· ╰── 'MediaVideoPlayer' is imported here
158 │ import { resolveMarkdownMediaPreview } from "../../lib/markdownMedia";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'mediaVideoPreviewUri' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:161:3]
160 │ attachmentVideoPreviewSource,
161 │ mediaVideoPreviewUri,
· ──────────┬─────────
· ╰── 'mediaVideoPreviewUri' is imported here
162 │ mediaVideoThumbnailKey,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'mediaVideoThumbnailKey' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:162:3]
161 │ mediaVideoPreviewUri,
162 │ mediaVideoThumbnailKey,
· ───────────┬──────────
· ╰── 'mediaVideoThumbnailKey' is imported here
163 │ type MediaVideoPreviewSource,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Type 'MediaVideoPreviewSource' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:163:8]
162 │ mediaVideoThumbnailKey,
163 │ type MediaVideoPreviewSource,
· ───────────┬───────────
· ╰── 'MediaVideoPreviewSource' is imported here
164 │ } from "../../lib/videoPreviewSource";
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Type 'ReviewDiffTheme' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:171:15]
170 │ import { parseReviewCommentMessageSegments } from "../review/reviewCommentSelection";
171 │ import type { ReviewDiffTheme } from "../review/shikiReviewHighlighter";
· ───────┬───────
· ╰── 'ReviewDiffTheme' is imported here
172 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownFontSizes' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:186:3]
185 │ import {
186 │ resolveMarkdownFontSizes,
· ────────────┬───────────
· ╰── 'resolveMarkdownFontSizes' is imported here
187 │ resolveNativeMarkdownTypography,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'resolveMarkdownInlineCodePresentation' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:193:3]
192 │ normalizeNativeMarkdownUrl,
193 │ resolveMarkdownInlineCodePresentation,
· ──────────────────┬──────────────────
· ╰── 'resolveMarkdownInlineCodePresentation' is imported here
194 │ resolveMarkdownLinkPresentation,
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useMarkdownCodeHighlight' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:233:10]
232 │ import { ThreadMcpApp } from "./McpAppWebView";
233 │ import { useMarkdownCodeHighlight } from "./markdownCodeHighlightState";
· ────────────┬───────────
· ╰── 'useMarkdownCodeHighlight' is imported here
234 │ import {
╰────
help: Consider removing this import.
⚠ eslint(no-unused-vars): Identifier 'useAssetUrlState' is imported but never used.
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:237:3]
236 │ useAssetUrl,
237 │ useAssetUrlState,
· ────────┬───────
· ╰── 'useAssetUrlState' is imported here
238 │ useRefreshAssetUrl,
╰────
help: Consider removing this import.
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2145:7]
2144 │ setExpandedFile(null);
2145 │ }, [props.environmentId, props.threadId, props.contentPresentation.kind]);
· ─────────┬───────── ───────┬────── ───────────────┬──────────────
· │ │ ╰── Unnecessary dependency `props.contentPresentation.kind`
· │ ╰── Unnecessary dependency `props.threadId`
· ╰── Unnecessary dependency `props.environmentId`
2146 │ const horizontalPadding = props.layoutVariant === "split" ? 20 : 16;
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2613:7]
2612 │ reportHeaderMaterialVisibility(false);
2613 │ }, [feedThreadKey, reportHeaderMaterialVisibility]);
· ──────┬──────
· ╰── Unnecessary dependency `feedThreadKey`
2614 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2629:7]
2628 │ }
2629 │ }, [listMountKey, props.contentInsetEndAdjustment, listRef]);
· ──────┬─────
· ╰── Unnecessary dependency `listMountKey`
2630 │ // Opening at a message: its run unfolds, the list stops following the end
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:2825:7]
2824 │ }
2825 │ }, [expandedTurnIds, expandedWorkGroups, expandedWorkRows, settleDisclosureAfterLayout]);
· ───────┬─────── ─────────┬──────── ────────┬───────
· │ │ ╰── Unnecessary dependency `expandedWorkRows`
· │ ╰── Unnecessary dependency `expandedWorkGroups`
· ╰── Unnecessary dependency `expandedTurnIds`
2826 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/ThreadFeed.tsx:617:9]
616 │ };
617 │ }, [props.environmentId, attachment.id, httpBaseUrl]),
· ─────────┬───────── ──────┬────── ─────┬─────
· │ │ ╰── Unnecessary dependency `httpBaseUrl`
· │ ╰── Unnecessary dependency `attachment.id`
· ╰── Unnecessary dependency `props.environmentId`
618 │ );
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:569:5]
567 │ }, []);
568 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
569 │ setKeyboardStateSuspect(false);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
570 │ }, [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:965:7]
962 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
963 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
964 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
965 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
· ─────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
966 │ }
╰────
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:1221:5]
1219 │
1220 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1221 │ setAnchorMessageId(null);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1222 │ 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:570:7]
569 │ setKeyboardStateSuspect(false);
570 │ }, [isKeyboardVisible, liveKeyboardHeight]);
· ────────┬──────── ─────────┬────────
· │ ╰── Unnecessary dependency `liveKeyboardHeight`
· ╰── Unnecessary dependency `isKeyboardVisible`
571 │ 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:1169:7]
1168 │ userInputInsetProgress.set(1);
1169 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
· ────────────┬───────────
· ╰── Unnecessary dependency `activeUserInputRequestId`
1170 │ 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:1227:15]
1226 │ freeze.set(false);
1227 │ }, [freeze, selectedThreadKey]);
· ────────┬────────
· ╰── Unnecessary dependency `selectedThreadKey`
1228 │
╰────
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:1057:5]
1052 │ const composerPopoverHeight = useSharedValue(0);
1053 │ const floatingControlCoverage = useSharedValue(
· ───────────┬───────────
· ╰── `floatingControlCoverage` originates here
1054 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
1055 │ );
1056 │ useEffect(() => {
1057 │ floatingControlCoverage.value = withTiming(
· ───────────┬───────────
· ╰── `floatingControlCoverage` cannot be modified
1058 │ 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:1075:7]
1065 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
1066 │ const combinedContentInsetEndAdjustment = useSharedValue(
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` originates here
1067 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
1068 │ );
1069 │ useAnimatedReaction(
1070 │ () =>
1071 │ contentInsetEndAdjustment.value +
1072 │ floatingControlCoverage.value +
1073 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
1074 │ (value) => {
1075 │ combinedContentInsetEndAdjustment.value = value;
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` cannot be modified
1076 │ },
╰────
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/mobile/src/features/threads/thread-list-v2-items.tsx:698:76]
697 │ const [snoozeGateClock, setSnoozeGateClock] = useState(() => ({ thread, now: Date.now() }));
698 │ if (snoozeGateClock.thread !== thread) setSnoozeGateClock({ thread, now: Date.now() });
· ─────┬────
· ╰── Cannot call impure function
699 │ const snoozeGateNow = new Date(snoozeGateClock.now).toISOString();
╰────
help: `Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(purity): Cannot call impure function during render
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:719:71]
718 │ const snoozePresets = useMemo(
719 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
· ─────┬────
· ╰── Cannot call impure function
720 │ [props.snoozePresetMinute, swipeActions.secondary],
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:720:6]
719 │ () => (swipeActions.secondary === "snooze" ? resolveSnoozePresets(new Date()) : ([] as const)),
720 │ [props.snoozePresetMinute, swipeActions.secondary],
· ────────────┬───────────
· ╰── Unnecessary dependency `props.snoozePresetMinute`
721 │ );
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:766:7]
765 │ thread.pinnedAt,
766 │ variant,
· ───┬───
· ╰── Unnecessary dependency `variant`
767 │ ],
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/threads/thread-list-v2-items.tsx:1216:21]
1215 │ {providerDrivers.slice(0, -1).map((driver, index) => (
1216 │ <View key={`${driver}:${index}`} className="-mr-1 opacity-30">
· ──────────────────────────
1217 │ <ProviderIcon provider={driver} size={12} />
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/Sidebar.tsx:1136:11]
1135 │ foldSearchQuery(threadSearchQuery),
1136 │ Date.now(),
· ─────┬────
· ╰── Cannot call impure function
1137 │ // A list filter, as on mobile: a pick would move rows unexplained.
╰────
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
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/project/ProjectService.test.ts:94:3]
93 │ ) {
94 │ ╭─▶ for (let attempt = 0; attempt < 100; attempt += 1) {
95 │ │ const project = Option.getOrThrow(yield* service.getById(projectId));
96 │ │ if (predicate(project)) return project;
97 │ │ yield* Effect.yieldNow;
98 │ ╰─▶ }
99 │ return yield* Effect.die(`Project ${projectId} was not enriched in time.`);
╰────
⚠ react(exhaustive-effect-dependencies): Found missing/extra effect dependencies
╭─[apps/mobile/src/features/threads/NewTaskContextPickerScreens.tsx:249:7]
248 │ mountedRef.current = false;
249 │ flow.setBranchQuery("");
· ──┬─
· ╰── Missing dependency `flow`
250 │ };
251 │ }, [flow.setBranchQuery]);
· ─────────┬─────────
· ╰── Overly precise dependency `flow.setBranchQuery`, use `flow` instead
252 │
╰────
help: Missing dependencies can cause an effect to fire less often than it should. Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ 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-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.
⚠ 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:1741:32]
1740 │ const model = createModelSelection(ProviderInstanceId.make("codex"), "gpt-5.5");
1741 │ const modelJson = yield* Schema.encodeEffect(Schema.fromJsonString(ModelSelection))(model);
· ───────────────────
1742 │ 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:1742:34]
1741 │ const modelJson = yield* Schema.encodeEffect(Schema.fromJsonString(ModelSelection))(model);
1742 │ const scriptsJson = yield* Schema.encodeEffect(
· ───────────────────
1743 │ Schema.fromJsonString(Schema.Array(ProjectScript)),
╰────
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:602:27]
601 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
602 │ const gesture = Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
603 │ .enabled(!props.disabled)
╰────
help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx:818:17]
817 │ <div
818 │ key={`${index}:${check.name}:${check.url ?? ""}`}
· ─────────────────────────────────────────────────
819 │ 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
⚠ 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.
╭─[apps/server/src/assets/AssetAccess.test.ts:975:35]
974 │ // Every client and server release spells the resource this way on the wire.
975 │ const { resource } = yield* Schema.decodeUnknownEffect(AssetCreateUrlInput)({
· ──────────────────────────
976 │ resource: { _tag: "github-media", cwd: "/repo", url },
╰────
⚠ 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:1012:32]
1011 │ expect(error._tag).toBe("AssetGitHubMediaUrlValidationError");
1012 │ const encoded = yield* Schema.encodeEffect(Schema.fromJsonString(AssetAccessError))(error);
· ───────────────────
1013 │ expect(encoded).not.toContain(url);
╰────
⚠ 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
Found 0 errors and 367 warnings in 5478 files (5.9s, 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=__c17805a4-df81-4837-925b-a1d05d7aa5c8.__actions_cache]
Post job cleanup.
Cache hit occurred on the primary key pnpm-full-v1-Linux-X64-fa50cf9b003d547cd32552f61b874eb4abe5dace3fdb4b1abd9610da2da24074, not saving cache.
##[end-action id=__c17805a4-df81-4837-925b-a1d05d7aa5c8.__actions_cache;outcome=success;conclusion=success;duration_ms=106]
##[start-action display=Cache Vite+;id=__c17805a4-df81-4837-925b-a1d05d7aa5c8.vp_cache]
Post job cleanup.
Cache hit occurred on the primary key vite-plus-home-v2-Linux-X64-1.3.0-node26.12.1-pnpm@12.14.0, not saving cache.
##[end-action id=__c17805a4-df81-4837-925b-a1d05d7aa5c8.vp_cache;outcome=success;conclusion=success;duration_ms=70]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/0c3b734d-d689-4807-a317-88263583a476' 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: 147
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 453
BLACKSMITH_CHECK_RUN_ID: 120875719752
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