GitHub check
256 KB of 598 KB loaded Download the full log (598 KB)
342 KB of earlier output not loaded
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:178:31]
177 │ });
178 │ const sendToThread = vi.fn((_: unknown) => {
· ┬
· ╰── '_' is declared here
179 │ switch (options.continuation ?? "queued") {
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:203:33]
202 │ );
203 │ const removeWorktree = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
204 │ options.removeWorktreeFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:208:36]
207 │ );
208 │ const deleteLocalBranch = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
209 │ options.deleteLocalBranchFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:213:42]
212 │ );
213 │ const fetchWorktreeBaseCommit = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
214 │ options.fetchWorktreeBaseFails
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:254:30]
253 │ );
254 │ const localStatus = vi.fn((_: unknown) =>
· ┬
· ╰── '_' is declared here
255 │ Effect.succeed({
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[apps/server/src/mcp/WorktreeMcpService.test.ts:264:32]
263 │ );
264 │ const refreshStatus = vi.fn((_: string) => Effect.die("refreshStatus stub"));
· ┬
· ╰── '_' is declared here
265 │ const runForThread = vi.fn((input: { readonly worktreePath: string }) => {
╰────
help: Consider removing this parameter.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadRouteScreen.tsx:400:5]
398 │
399 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
400 │ setInspectorSelection((current) => {
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
401 │ 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:528:24]
527 │ const inspectorHeaderInset = Platform.OS === "ios" ? 0 : safeAreaInsets.top;
528 │ ╭─▶ const GitInspector = () => (
529 │ │ <GitOverviewSheet
530 │ │ headerInset={inspectorHeaderInset}
531 │ │ presentation="inspector"
532 │ │ route={{ params: { environmentId: environmentId!, threadId: threadId! } }}
533 │ │ />
534 │ ╰─▶ );
535 │ 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:535:26]
534 │ );
535 │ ╭─▶ const FilesInspector = () =>
536 │ │ selectedThread !== null && selectedThreadCwd !== null ? (
537 │ │ <ThreadFileNavigatorPane
538 │ │ cwd={selectedThreadCwd}
539 │ │ environmentId={selectedThread.environmentId}
540 │ │ headerInset={inspectorHeaderInset}
541 │ │ projectName={selectedThreadProject?.title ?? "Files"}
542 │ │ selectedPath={null}
543 │ │ onSelectFile={handleSelectInspectorFile}
544 │ │ />
545 │ ╰─▶ ) : null;
546 │ const RouteInspector = () => props.renderInspector?.(inspectorHeaderInset);
╰────
help: Move this component definition out of the parent component `ThreadRouteContent` and pass data as props.
⚠ eslint(no-unused-vars): Function 'summarizePayload' is declared but never used.
╭─[packages/provider-acp/src/server/nativeLogging.ts:22:10]
21 │
22 │ function summarizePayload(payload: unknown): Readonly<Record<string, unknown>> {
· ────────┬───────
· ╰── 'summarizePayload' is declared here
23 │ if (payload === null) return { valueType: "null" };
╰────
help: Consider removing this declaration.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/ThreadDetailScreen.tsx:512:5]
510 │ }, []);
511 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
512 │ setKeyboardStateSuspect(false);
· ───────────┬───────────
· ╰── Avoid calling setState() directly within an effect
513 │ }, [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:872:7]
869 │ const [lastKnownKeyboardHeight, setLastKnownKeyboardHeight] = useState(0);
870 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
871 │ if (liveKeyboardHeight > 0 && liveKeyboardHeight !== lastKnownKeyboardHeight) {
872 │ setLastKnownKeyboardHeight(liveKeyboardHeight);
· ─────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
873 │ }
╰────
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:1119:5]
1117 │
1118 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
1119 │ setAnchorMessageId(null);
· ─────────┬────────
· ╰── Avoid calling setState() directly within an effect
1120 │ 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:513:7]
512 │ setKeyboardStateSuspect(false);
513 │ }, [isKeyboardVisible, liveKeyboardHeight]);
· ────────┬──────── ─────────┬────────
· │ ╰── Unnecessary dependency `liveKeyboardHeight`
· ╰── Unnecessary dependency `isKeyboardVisible`
514 │ 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:1067:7]
1066 │ userInputInsetProgress.set(1);
1067 │ }, [activeUserInputRequestId, userInputCardProgress, userInputInsetProgress]);
· ────────────┬───────────
· ╰── Unnecessary dependency `activeUserInputRequestId`
1068 │ 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:1125:15]
1124 │ freeze.set(false);
1125 │ }, [freeze, selectedThreadKey]);
· ────────┬────────
· ╰── Unnecessary dependency `selectedThreadKey`
1126 │
╰────
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:955:5]
950 │ const composerPopoverHeight = useSharedValue(0);
951 │ const floatingControlCoverage = useSharedValue(
· ───────────┬───────────
· ╰── `floatingControlCoverage` originates here
952 │ showFloatingStatus ? FLOATING_WORKING_CONTROL_COVERAGE : 0,
953 │ );
954 │ useEffect(() => {
955 │ floatingControlCoverage.value = withTiming(
· ───────────┬───────────
· ╰── `floatingControlCoverage` cannot be modified
956 │ 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:973:7]
963 │ const userInputCoverageApplies = Platform.OS === "ios" && activeUserInputRequestId !== null;
964 │ const combinedContentInsetEndAdjustment = useSharedValue(
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` originates here
965 │ Math.max(0, estimatedOverlayHeight - nativeInsetOvercount),
966 │ );
967 │ useAnimatedReaction(
968 │ () =>
969 │ contentInsetEndAdjustment.value +
970 │ floatingControlCoverage.value +
971 │ (userInputCoverageApplies ? userInputInsetProgress.value * userInputCardCoverage.value : 0),
972 │ (value) => {
973 │ combinedContentInsetEndAdjustment.value = value;
· ────────────────┬────────────────
· ╰── `combinedContentInsetEndAdjustment` cannot be modified
974 │ },
╰────
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.decodeUnknownOption(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/shared/src/otelEnvironment.ts:146:14]
145 │ name,
146 │ (raw) => Schema.decodeUnknownOption(OtlpProtocol)(raw.toLowerCase()),
· ──────────────────────────
147 │ `${name} is not http/protobuf or http/json, ${NOT_EXPORTED}`,
╰────
⚠ eslint(require-yield): This generator function does not have `yield`
╭─[packages/provider-acp/src/server/mcpOverAcpBridge.ts:81:78]
80 │
81 │ ╭─▶ export const makeAcpMcpOverAcpBridge = Effect.fn("AcpMcpOverAcpBridge.make")(function* (
82 │ │ options: AcpMcpOverAcpBridgeOptions,
83 │ │ ): Effect.fn.Return<AcpMcpOverAcpBridge> {
84 │ │ const fetchImplementation = options.fetchImplementation ?? fetch;
85 │ │ const connections = new Map<string, Connection>();
86 │ │
87 │ │ const connectionFor = (connectionId: string): Effect.Effect<Connection, AcpMcpOverAcpError> =>
88 │ │ Effect.suspend(() => {
89 │ │ const connection = connections.get(connectionId);
90 │ │ return connection === undefined
91 │ │ ? Effect.fail(new AcpMcpOverAcpError(`Unknown MCP-over-ACP connection "${connectionId}".`))
92 │ │ : Effect.succeed(connection);
93 │ │ });
94 │ │
95 │ │ const send = (
96 │ │ connection: Connection,
97 │ │ message: unknown,
98 │ │ ): Effect.Effect<ReadonlyArray<unknown>, AcpMcpOverAcpError> =>
99 │ │ connection.mutex.withPermits(1)(
100 │ │ Effect.gen(function* () {
101 │ │ const body = JSON.stringify(message);
102 │ │ if (Buffer.byteLength(body) > MAX_MESSAGE_BYTES) {
103 │ │ return yield* Effect.fail(new AcpMcpOverAcpError("MCP-over-ACP message exceeds 8 MiB."));
104 │ │ }
105 │ │ const response = yield* Effect.tryPromise({
106 │ │ try: (signal) =>
107 │ │ fetchImplementation(options.endpoint, {
108 │ │ method: "POST",
109 │ │ signal,
110 │ │ headers: {
111 │ │ "content-type": "application/json",
112 │ │ accept: "application/json, text/event-stream",
113 │ │ authorization: options.authorization,
114 │ │ ...(connection.sessionId === null
115 │ │ ? {}
116 │ │ : { "mcp-session-id": connection.sessionId }),
117 │ │ ...(connection.protocolVersion === null
118 │ │ ? {}
119 │ │ : { "mcp-protocol-version": connection.protocolVersion }),
120 │ │ },
121 │ │ body,
122 │ │ }),
123 │ │ catch: bridgeError,
124 │ │ });
125 │ │ connection.sessionId = response.headers.get("mcp-session-id") ?? connection.sessionId;
126 │ │ if (!response.ok) {
127 │ │ yield* Effect.promise(
128 │ │ () => response.body?.cancel().catch(() => undefined) ?? Promise.resolve(),
129 │ │ );
130 │ │ return yield* Effect.fail(
131 │ │ new AcpMcpOverAcpError(`T3 Code MCP endpoint responded with HTTP ${response.status}.`),
132 │ │ );
133 │ │ }
134 │ │ const payloads = [...(yield* Stream.runCollect(responsePayloads(response, bridgeError)))];
135 │ │ for (const payload of payloads) {
136 │ │ connection.protocolVersion = protocolVersionOf(payload) ?? connection.protocolVersion;
137 │ │ }
138 │ │ return payloads;
139 │ │ }).pipe(Effect.mapError(bridgeError)),
140 │ │ );
141 │ │
142 │ │ const disconnect = Effect.fn("mcpOverAcpBridge.disconnect")(function* (
143 │ │ request: AcpSchema.DisconnectMcpRequest,
144 │ │ ): Effect.fn.Return<AcpSchema.DisconnectMcpResponse, AcpMcpOverAcpError> {
145 │ │ const connection = yield* connectionFor(request.connectionId);
146 │ │ connections.delete(request.connectionId);
147 │ │ const sessionId = connection.sessionId;
148 │ │ if (sessionId !== null) {
149 │ │ const response = yield* Effect.tryPromise({
150 │ │ try: (signal) =>
151 │ │ fetchImplementation(options.endpoint, {
152 │ │ method: "DELETE",
153 │ │ signal,
154 │ │ headers: {
155 │ │ authorization: options.authorization,
156 │ │ "mcp-session-id": sessionId,
157 │ │ ...(connection.protocolVersion === null
158 │ │ ? {}
159 │ │ : { "mcp-protocol-version": connection.protocolVersion }),
160 │ │ },
161 │ │ }),
162 │ │ catch: bridgeError,
163 │ │ });
164 │ │ if (!response.ok && response.status !== 404) {
165 │ │ return yield* Effect.fail(
166 │ │ new AcpMcpOverAcpError(
167 │ │ `T3 Code MCP endpoint rejected disconnect with HTTP ${response.status}.`,
168 │ │ ),
169 │ │ );
170 │ │ }
171 │ │ yield* Effect.promise(
172 │ │ () => response.body?.cancel().catch(() => undefined) ?? Promise.resolve(),
173 │ │ );
174 │ │ }
175 │ │ return {};
176 │ │ });
177 │ │
178 │ │ return {
179 │ │ connect: Effect.fn("mcpOverAcpBridge.connect")(function* (request) {
180 │ │ if (request.serverId !== "t3-code") {
181 │ │ return yield* Effect.fail(
182 │ │ new AcpMcpOverAcpError(`Unknown ACP MCP server "${request.serverId}".`),
183 │ │ );
184 │ │ }
185 │ │ if (connections.size >= MAX_CONNECTIONS) {
186 │ │ return yield* Effect.fail(new AcpMcpOverAcpError("Too many MCP-over-ACP connections."));
187 │ │ }
188 │ │ const connectionId = yield* options.allocateConnectionId;
189 │ │ connections.set(connectionId, {
190 │ │ mutex: yield* Semaphore.make(1),
191 │ │ sessionId: null,
192 │ │ protocolVersion: null,
193 │ │ nextRequestId: 0,
194 │ │ });
195 │ │ return { connectionId };
196 │ │ }),
197 │ │ message: Effect.fn("mcpOverAcpBridge.message")(function* (request) {
198 │ │ const connection = yield* connectionFor(request.connectionId);
199 │ │ const id = ++connection.nextRequestId;
200 │ │ const payloads = yield* send(connection, {
201 │ │ jsonrpc: "2.0",
202 │ │ id,
203 │ │ method: request.method,
204 │ │ ...(request.params == null ? {} : { params: request.params }),
205 │ │ });
206 │ │ const response = payloads.find((payload) => asEnvelope(payload)?.id === id);
207 │ │ const envelope = asEnvelope(response);
208 │ │ if (envelope === null) {
209 │ │ return yield* Effect.fail(
210 │ │ new AcpMcpOverAcpError("MCP server did not return a matching response."),
211 │ │ );
212 │ │ }
213 │ │ if (envelope.error !== undefined) {
214 │ │ return yield* Effect.fail(new AcpMcpOverAcpError(errorMessage(envelope.error)));
215 │ │ }
216 │ │ return (envelope.result ?? null) as AcpSchema.MessageMcpResponse;
217 │ │ }),
218 │ │ notification: Effect.fn("mcpOverAcpBridge.notification")(function* (request) {
219 │ │ const connection = yield* connectionFor(request.connectionId);
220 │ │ yield* send(connection, {
221 │ │ jsonrpc: "2.0",
222 │ │ method: request.method,
223 │ │ ...(request.params == null ? {} : { params: request.params }),
224 │ │ });
225 │ │ }),
226 │ │ disconnect,
227 │ │ dispose: Effect.suspend(() =>
228 │ │ Effect.forEach(
229 │ │ [...connections.keys()],
230 │ │ (connectionId) => disconnect({ connectionId }).pipe(Effect.ignore),
231 │ │ { discard: true },
232 │ │ ),
233 │ │ ),
234 │ │ };
235 │ ╰─▶ });
╰────
help: Add a `yield` expression inside the generator body, or convert it to a regular function if iteration behavior is not needed.
⚠ eslint(no-empty-pattern): Empty object binding pattern
╭─[packages/provider-opencode/src/server/OpenCodeRuntime.environment.test.ts:53:14]
52 │
53 │ for (const {} of [
· ──
54 │ { healthy: true },
╰────
help: Passing `null` or `undefined` will result in runtime error because `null` and `undefined` cannot be destructured.
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/web/src/components/pullRequest/PullRequestChecksPopover.tsx:88:15]
87 │ <li
88 │ key={`${index}:${check.name}`}
· ──────────────────────────────
89 │ className="col-span-full grid grid-cols-subgrid items-center text-xs"
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[packages/shared/src/serverSettings.ts:346:9]
345 │ const entry: ProjectSettingsOverrides = {
346 │ ...(entries.get(projectId) ?? currentEntries[projectId] ?? {}),
· ──────────────────────────────────────────────────────────────
347 │ };
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ oxc(no-accumulating-spread): Do not spread accumulators in Array.prototype.reduce()
╭─[packages/shared/src/serverSettings.ts:448:24]
447 │ const favorites =
448 │ setModelFavorites?.reduce((current, change) => {
· ───┬──
· ╰── For this reduce
449 │ const exists = current.some(
450 │ (favorite) => favorite.provider === change.provider && favorite.model === change.model,
451 │ );
452 │ return change.favorite
453 │ ? exists
454 │ ? current
455 │ : [...current, { provider: change.provider, model: change.model }]
· ─────┬────
· ╰── From this spread
456 │ : current.filter(
╰────
help: Consider using `Object.assign()` or `Array.prototype.push()` to mutate the accumulator instead.
note: Using spreads within accumulators leads to `O(n^2)` time complexity.
⚠ oxc(no-accumulating-spread): Do not spread accumulators in loops
╭─[packages/shared/src/serverSettings.ts:466:3]
464 │ null;
465 │ let nextModelPreferences = initialModelPreferences;
· ──────────┬─────────
· ╰── From this accumulator
466 │ for (const change of setModelsHidden ?? []) {
· ─┬─
· ╰── For this loop
467 │ const preferences = nextModelPreferences?.[change.provider] ?? {
468 │ hiddenModels: [],
469 │ modelOrder: [],
470 │ };
471 │ const hiddenModels = preferences.hiddenModels.filter((model) => model !== change.model);
472 │ if (change.hidden) hiddenModels.push(change.model);
473 │ nextModelPreferences = {
474 │ ...nextModelPreferences,
· ───────────┬───────────
· ╰── From this spread
475 │ [change.provider]: { ...preferences, hiddenModels },
╰────
help: Consider using `Object.assign()` to mutate the accumulator instead.
note: Using spreads within accumulators leads to `O(n^2)` time complexity.
⚠ eslint(no-control-regex): Unexpected control character
╭─[apps/mobile/src/features/settings/SettingsProviderAccountsRouteScreen.tsx:220:46]
219 │ <Text selectable className="font-mono text-sm text-foreground">
220 │ {interaction.output.replace(/\x1b\[[0-?]*[ -/]*[@-~]/g, "")}
· ──┬─
· ╰── 'U+001B' is a control character.
221 │ </Text>
╰────
help: Avoid matching control characters in regular expressions. If intentional, disable this rule for the expression.
⚠ react(capitalized-calls): Capitalized function called without JSX
╭─[apps/mobile/src/features/threads/ThreadQueueControl.tsx:602:27]
601 │ const onEnd = useEffectEvent((y: number, success: boolean) => props.onEnd(y, success));
602 │ const gesture = Gesture.Pan()
· ─┬─
· ╰── `Pan` may be a component
603 │ .enabled(!props.disabled)
╰────
help: Render `Pan` with JSX if it is a component; otherwise rename it to start with a lowercase letter or allowlist it in the compiler configuration
note: `Pan` is treated as a component because it begins with an uppercase letter; React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:119:10]
117 │
118 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
119 │ void refreshNotifications();
· ──────────┬─────────
· ╰── Avoid calling setState() directly within an effect
120 │ const subscription = AppState.addEventListener("change", (state) => {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/settings/SettingsNotificationsRouteScreen.tsx:128:7]
125 │
126 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
127 │ if (!isLoaded) {
128 │ setLiveActivityStatus("checking");
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
129 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/thread-inspector-content-stack.tsx:60:5]
58 │
59 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
60 │ setMountedModes((current) => {
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
61 │ if (current.has(props.mode)) {
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Function 'promptResponseHasMissingXAiStopReason' is declared but never used.
╭─[packages/provider-grok/src/server/xaiAcpExtension.ts:1620:10]
1619 │
1620 │ function promptResponseHasMissingXAiStopReason(response: EffectAcpSchema.PromptResponse): boolean {
· ──────────────────┬──────────────────
· ╰── 'promptResponseHasMissingXAiStopReason' is declared here
1621 │ const meta = response._meta;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[packages/provider-opencode/src/server/adapter.ts:3755:7]
3754 │
3755 │ const layer: Layer.Layer<ProviderAdapter.ProviderAdapterV2, never, OpenCodeAdapterV2DriverEnv> =
· ──┬──
· ╰── 'layer' is declared here
3756 │ Layer.effect(
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'revokeActiveMcpThread' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/mcp/McpSessionRegistry.ts:218:7]
217 │
218 │ const revokeActiveMcpThread = (threadId: ThreadId): Effect.Effect<void> =>
· ──────────┬──────────
· ╰── 'revokeActiveMcpThread' is declared here
219 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeThread(threadId) : Effect.void;
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Variable 'revokeAllActiveMcpCredentials' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/mcp/McpSessionRegistry.ts:221:7]
220 │
221 │ const revokeAllActiveMcpCredentials = (): Effect.Effect<void> =>
· ──────────────┬──────────────
· ╰── 'revokeAllActiveMcpCredentials' is declared here
222 │ activeMcpSessionRegistry ? activeMcpSessionRegistry.revokeAll : Effect.void;
╰────
help: Consider removing this declaration.
⚠ 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
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[scripts/lib/cli-external-packages.test.ts:114:11]
113 │ const declared = {
114 │ ...(manifest.dependencies ?? {}),
· ────────────────────────────────
115 │ ...(manifest.optionalDependencies ?? {}),
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[scripts/lib/cli-external-packages.test.ts:115:11]
114 │ ...(manifest.dependencies ?? {}),
115 │ ...(manifest.optionalDependencies ?? {}),
· ────────────────────────────────────────
116 │ ...(manifest.peerDependencies ?? {}),
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ unicorn(no-useless-fallback-in-spread): Empty fallbacks in spreads are unnecessary
╭─[scripts/lib/cli-external-packages.test.ts:116:11]
115 │ ...(manifest.optionalDependencies ?? {}),
116 │ ...(manifest.peerDependencies ?? {}),
· ────────────────────────────────────
117 │ };
╰────
help: Spreading falsy values in object literals won't add any unexpected properties, so it's unnecessary to add an empty object as fallback.
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/useVoiceInputController.ts:27:14]
26 │ const latestInput = useRef(input);
27 │ latestInput.current = input;
· ─────┬─────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
28 │ const mounted = useRef(true);
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:122:38]
121 │ const audioLevelsRef = useRef(Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0));
122 │ const audioLevels = useSharedValue(audioLevelsRef.current);
· ───────────┬──────────
· ╰── Cannot access ref value during render
123 │ const sessionRef = useRef<VoiceInputSession | null>(null);
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:8]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:7]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:31]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ─────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:126:30]
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
· ──────────┬─────────
· ╰── Cannot access ref value during render
127 │ const recorder = createLazyVoiceRecorder({
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:127:46]
126 │ if (!sessionRef.current || !recorderRef.current) {
127 │ ╭─▶ const recorder = createLazyVoiceRecorder({
128 │ │ create: () => new AudioModule.AudioRecorder(VOICE_RECORDING_OPTIONS),
129 │ │ onStatus: (status: RecordingStatus) => {
130 │ │ sessionRef.current?.controller.handleRecorderStatus({
131 │ │ isFinished: status.isFinished,
132 │ │ hasError: status.hasError || status.mediaServicesDidReset === true,
133 │ │ error: status.error,
134 │ │ url: status.url,
135 │ │ });
136 │ │ },
137 │ │ // Read when recording starts so preference changes do not re-render every composer.
138 │ │ selectInput: (inputs) => {
139 │ │ const preferences = registry.get(mobilePreferencesAtom);
140 │ │ if (!AsyncResult.isSuccess(preferences)) return null;
141 │ │ const known = microphoneOrder(preferences.value.microphones);
142 │ │ const order = rememberMicrophones(known, inputs);
143 │ │ if (order !== known) {
144 │ │ registry.set(updateMobilePreferencesAtom, {
145 │ │ transform: (current) => ({
146 │ │ microphones: rememberMicrophones(microphoneOrder(current.microphones), inputs),
147 │ │ }),
148 │ │ });
149 │ │ }
150 │ │ return preferredMicrophoneInput(inputs, order);
151 │ │ },
152 │ ├─▶ });
· ╰──── Passing a ref to a function may read its value during render
153 │ recorderRef.current = recorder;
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:153:16]
152 │ });
153 │ recorderRef.current = recorder;
· ─────┬─────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
154 │ sessionRef.current = new VoiceInputSession({
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:154:48]
153 │ recorderRef.current = recorder;
154 │ ╭─▶ sessionRef.current = new VoiceInputSession({
155 │ │ recorder,
156 │ │ getTranscriber: getLocalVoiceTranscriber,
157 │ │ requestPermission: async () => {
158 │ │ const permission = await requestRecordingPermissionsAsync();
159 │ │ return { granted: permission.granted, canAskAgain: permission.canAskAgain };
160 │ │ },
161 │ │ configureRecording: configureVoiceRecordingAudio,
162 │ │ releaseRecording: releaseVoiceRecordingAudio,
163 │ │ deleteRecording: (uri) => new File(uri).delete(),
164 │ │ onStateChange: (nextState) =>
165 │ │ setState({
166 │ │ state: nextState,
167 │ │ ownerKey: sessionRef.current?.ownerKey ?? null,
168 │ │ label: sessionRef.current?.label ?? null,
169 │ │ }),
170 │ ├─▶ });
· ╰──── Cannot access ref value during render
171 │ }
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:154:15]
153 │ recorderRef.current = recorder;
154 │ sessionRef.current = new VoiceInputSession({
· ─────┬────────┬───
· │ ╰── Cannot update ref value during render
· ╰── This value is a ref
155 │ recorder,
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:185:7]
184 │ return () => subscription.remove();
185 │ }, [controller]);
· ─────┬────
· ╰── Cannot access ref value during render
186 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:185:6]
184 │ return () => subscription.remove();
185 │ }, [controller]);
· ──────┬─────
· ╰── Cannot access ref value during render
186 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:192:6]
191 │ },
192 │ [controller, recorder],
· ─────┬────
· ╰── Cannot access ref value during render
193 │ );
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:175:20]
174 │ const controller = session.controller;
175 │ const recorder = recorderRef.current;
· ─────────┬─────────
· ╰── Cannot access ref value during render
176 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:192:5]
191 │ },
192 │ [controller, recorder],
· ───────────┬──────────
· ╰── Cannot access ref value during render
193 │ );
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:246:20]
245 │ return () => clearInterval(intervalId);
246 │ }, [audioLevels, controller, recorder, state.phase]);
· ─────┬────
· ╰── Cannot access ref value during render
247 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:246:6]
245 │ return () => clearInterval(intervalId);
246 │ }, [audioLevels, controller, recorder, state.phase]);
· ────────────────────────┬───────────────────────
· ╰── Cannot access ref value during render
247 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:261:5]
260 │ setOwnerFocused,
261 │ session,
· ───┬───
· ╰── Cannot access ref value during render
262 │ stop,
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:251:10]
250 │
251 │ ╭─▶ return {
252 │ │ isAvailable: getLocalVoiceTranscriber() !== null || getNativeShowcaseScene() !== null,
253 │ │ state,
254 │ │ audioLevels,
255 │ │ elapsedSeconds,
256 │ │ isBusy: voiceInputBlocksSubmission(state),
257 │ │ ownerKey,
258 │ │ label,
259 │ │ focusedOwners,
260 │ │ setOwnerFocused,
261 │ │ session,
262 │ │ stop,
263 │ │ cancel,
264 │ ├─▶ };
· ╰──── Cannot access ref value during render
265 │ }
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:212:7]
121 │ const audioLevelsRef = useRef(Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0));
122 │ const audioLevels = useSharedValue(audioLevelsRef.current);
· ─────┬─────
· ╰── `audioLevels` originates here
123 │ const sessionRef = useRef<VoiceInputSession | null>(null);
124 │ const recorderRef = useRef<LazyVoiceRecorder<RecorderState> | null>(null);
125 │
126 │ if (!sessionRef.current || !recorderRef.current) {
127 │ const recorder = createLazyVoiceRecorder({
128 │ create: () => new AudioModule.AudioRecorder(VOICE_RECORDING_OPTIONS),
129 │ onStatus: (status: RecordingStatus) => {
130 │ sessionRef.current?.controller.handleRecorderStatus({
131 │ isFinished: status.isFinished,
132 │ hasError: status.hasError || status.mediaServicesDidReset === true,
133 │ error: status.error,
134 │ url: status.url,
135 │ });
136 │ },
137 │ // Read when recording starts so preference changes do not re-render every composer.
138 │ selectInput: (inputs) => {
139 │ const preferences = registry.get(mobilePreferencesAtom);
140 │ if (!AsyncResult.isSuccess(preferences)) return null;
141 │ const known = microphoneOrder(preferences.value.microphones);
142 │ const order = rememberMicrophones(known, inputs);
143 │ if (order !== known) {
144 │ registry.set(updateMobilePreferencesAtom, {
145 │ transform: (current) => ({
146 │ microphones: rememberMicrophones(microphoneOrder(current.microphones), inputs),
147 │ }),
148 │ });
149 │ }
150 │ return preferredMicrophoneInput(inputs, order);
151 │ },
152 │ });
153 │ recorderRef.current = recorder;
154 │ sessionRef.current = new VoiceInputSession({
155 │ recorder,
156 │ getTranscriber: getLocalVoiceTranscriber,
157 │ requestPermission: async () => {
158 │ const permission = await requestRecordingPermissionsAsync();
159 │ return { granted: permission.granted, canAskAgain: permission.canAskAgain };
160 │ },
161 │ configureRecording: configureVoiceRecordingAudio,
162 │ releaseRecording: releaseVoiceRecordingAudio,
163 │ deleteRecording: (uri) => new File(uri).delete(),
164 │ onStateChange: (nextState) =>
165 │ setState({
166 │ state: nextState,
167 │ ownerKey: sessionRef.current?.ownerKey ?? null,
168 │ label: sessionRef.current?.label ?? null,
169 │ }),
170 │ });
171 │ }
172 │
173 │ const session = sessionRef.current;
174 │ const controller = session.controller;
175 │ const recorder = recorderRef.current;
176 │
177 │ useEffect(() => {
178 │ const subscription = AppState.addEventListener("change", (nextState) => {
179 │ // iOS reports `inactive` while its permission dialog is open. Only the
180 │ // real background state cancels preparation; recorder status handles
181 │ // calls and route interruptions during capture.
182 │ if (nextState === "background") controller.appMovedToBackground();
183 │ });
184 │ return () => subscription.remove();
185 │ }, [controller]);
186 │
187 │ useEffect(
188 │ () => () => {
189 │ controller.dispose();
190 │ recorder.release();
191 │ },
192 │ [controller, recorder],
193 │ );
194 │
195 │ useEffect(() => {
196 │ if (state.phase !== "recording") return;
197 │
198 │ const tag = `voice-input:${keepAwakeId}:${++keepAwakeSessionRef.current}`;
199 │ const activation = activateKeepAwakeAsync(tag);
200 │ void activation.catch(() => {});
201 │ return () => {
202 │ // Release after activation settles, even if the recording ends immediately.
203 │ void activation.then(() => deactivateKeepAwake(tag)).catch(() => {});
204 │ };
205 │ }, [keepAwakeId, state.phase]);
206 │
207 │ useEffect(() => {
208 │ if (state.phase !== "preparing" && state.phase !== "recording") return;
209 │
210 │ if (audioLevelsRef.current.some((level) => level !== 0)) {
211 │ audioLevelsRef.current = Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0);
212 │ audioLevels.value = audioLevelsRef.current;
· ─────┬─────
· ╰── `audioLevels` cannot be modified
213 │ }
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): Cannot modify local variables after render completes
╭─[apps/mobile/src/features/voice-input/VoiceInputProvider.tsx:212:7]
206 │
207 │ useEffect(() => {
· ───┬───
· ╰── This function may (indirectly) reassign or modify `audioLevels` after render
208 │ if (state.phase !== "preparing" && state.phase !== "recording") return;
209 │
210 │ if (audioLevelsRef.current.some((level) => level !== 0)) {
211 │ audioLevelsRef.current = Array<number>(VOICE_WAVEFORM_SAMPLE_COUNT).fill(0);
212 │ audioLevels.value = audioLevelsRef.current;
· ─────┬─────
· ╰── This modifies `audioLevels`
213 │ }
╰────
help: This argument is a function which may reassign or mutate `audioLevels` after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ 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
⚠ eslint(no-new): Do not use 'new' for side effects.
╭─[apps/server/src/mcp/McpToolAccess.test.ts:168:3]
167 │ // @ts-expect-error a declaration constructed directly
168 │ new McpToolAccess.Declaration(unchecked);
· ─────────────────────────────
169 │ // @ts-expect-error a handlers layer built outside McpToolAccess
╰────
help: Assign the result of 'new' to a variable or compare it to a reference.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:93:5]
90 │ }) {
91 │ const rotation = useSharedValue(props.hidden ? 1 : 0);
· ────┬───
· ╰── `rotation` originates here
92 │ useLayoutEffect(() => {
93 │ rotation.value = withTiming(props.hidden ? 1 : 0, TOOLBAR_FLIP_TIMING);
· ────┬───
· ╰── `rotation` cannot be modified
94 │ }, [props.hidden, rotation]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:269:5]
266 │ const variant = props.variant ?? "plain";
267 │ const loadingVisibility = useSharedValue(props.loading ? 1 : 0);
· ────────┬────────
· ╰── `loadingVisibility` originates here
268 │ useLayoutEffect(() => {
269 │ loadingVisibility.value = withTiming(props.loading ? 1 : 0, DICTATION_TIMING);
· ────────┬────────
· ╰── `loadingVisibility` cannot be modified
270 │ }, [loadingVisibility, props.loading]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/voice-input/ComposerDictationControl.tsx:328:5]
325 │ }) {
326 │ const recordingVisibility = useSharedValue(props.phase === "recording" ? 1 : 0);
· ─────────┬─────────
· ╰── `recordingVisibility` originates here
327 │ useLayoutEffect(() => {
328 │ recordingVisibility.value = withTiming(props.phase === "recording" ? 1 : 0, DICTATION_TIMING);
· ─────────┬─────────
· ╰── `recordingVisibility` cannot be modified
329 │ }, [props.phase, recordingVisibility]);
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/diffs/nativeReviewDiffSurface.ts:277:39]
276 │
277 │ ╭─▶ return createElement(RawNativeView, {
278 │ │ ...nativeProps,
279 │ │ refreshEnabled: props.onPullToRefresh !== undefined,
280 │ │ ref: nativeRef,
281 │ ├─▶ });
· ╰──── Passing a ref to a function may read its value during render
282 │ }
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[packages/provider-grok/src/server/adapter.ts:408:7]
407 │
408 │ const layer: Layer.Layer<
· ──┬──
· ╰── 'layer' is declared here
409 │ ProviderAdapter.ProviderAdapterV2,
╰────
help: Consider removing this declaration.
⚠ 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.
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownSync(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[apps/server/src/auth/RpcAuthorization.ts:236:17]
235 │ const requiredScopesForSettingsUpdate = (payload: unknown) => {
236 │ const input = Schema.decodeUnknownSync(SettingsUpdate)(payload);
· ────────────────────────
237 │ const scopes = requiredScopesForServerSettingsPatch(input.patch);
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownSync(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[apps/server/src/auth/RpcAuthorization.ts:255:26]
254 │ if (method === WS_METHODS.assetsCreateUrl) {
255 │ const { resource } = Schema.decodeUnknownSync(AssetCreateUrlInput)(payload);
· ────────────────────────
256 │ return [
╰────
⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
╭─[apps/web/src/components/pullRequest/PullRequestListFilters.tsx:387:19]
386 │ onFilters,
387 │ authorOptions = [],
· ──
388 │ labelOptions = [],
╰────
help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
⚠ react(no-object-type-as-default-prop): Do not use an array literal as default prop value. Use a stable reference instead.
╭─[apps/web/src/components/pullRequest/PullRequestListFilters.tsx:388:18]
387 │ authorOptions = [],
388 │ labelOptions = [],
· ──
389 │ host,
╰────
help: Default values are re-created on every render and break referential equality, causing unnecessary re-renders. Move the value out of the component or memoize it.
⚠ react(memo-dependencies): Found extra memoization dependencies
╭─[apps/mobile/src/features/keyboard/HardwareKeyboardCommandProvider.tsx:116:34]
115 │ return [...commands];
116 │ }, [activeThreadRef, pathname, registrationVersion, navigation]);
· ─────────┬─────────
· ╰── Unnecessary dependency `registrationVersion`
117 │
╰────
help: Extra dependencies can cause a value to update more often than it should, resulting in performance problems such as excessive renders or effects firing too often
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ eslint(no-unused-vars): Variable 'layer' is declared but never used. Unused variables should start with a '_'.
╭─[apps/server/src/orchestration-v2/ThreadPullRequestService.ts:413:7]
412 │
413 │ const layer = Layer.effect(ThreadPullRequestServiceV2, make);
· ──┬──
· ╰── 'layer' is declared here
╰────
help: Consider removing this declaration.
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/effect-acp/src/protocol.test.ts:500:31]
499 │
500 │ const response = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
501 │ Schema.fromJsonString(JsonRpcErrorResponse),
╰────
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:643:5]
638 │
639 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
640 │ if (pendingLaunchEntry.key === launchTargetKey) {
641 │ return;
642 │ }
643 │ setPendingLaunchEntry({
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
644 │ key: launchTargetKey,
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:653:5]
648 │
649 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
650 │ if (initialAttachGridEntry.key === launchTargetKey) {
651 │ return;
652 │ }
653 │ setInitialAttachGridEntry({
· ────────────┬────────────
· ╰── Avoid calling setState() directly within an effect
654 │ key: launchTargetKey,
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:746:7]
743 │
744 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
745 │ if (!routeEnvironmentId || !routeThreadId) {
746 │ setLastGridSize({
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
747 │ cols: DEFAULT_TERMINAL_COLS,
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:538:24]
537 │ });
538 │ }, [terminal.buffer, terminal.buffer.length, terminalKey]);
· ───────────┬──────────
· ╰── Overly precise dependency `terminal.buffer.length`, use `terminal.buffer` instead
539 │ const cwd = terminal.summary?.cwd ?? selectedThreadProject?.workspaceRoot ?? null;
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:709:7]
708 │ sentInitialInputKeyRef.current = null;
709 │ }, [terminalKey]);
· ─────┬─────
· ╰── Unnecessary dependency `terminalKey`
710 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:800:52]
799 │ };
800 │ }, [canOperateTerminal, isRunning, pasteSession, terminal.lifecycleVersion, terminalKey]);
· ────────────┬──────────── ─────┬─────
· │ ╰── Unnecessary dependency `terminalKey`
· ╰── Unnecessary dependency `terminal.lifecycleVersion`
801 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(refs): Cannot access refs during render
╭─[apps/mobile/src/features/terminal/ThreadTerminalRouteScreen.tsx:793:24]
792 │ }
793 │ const pasteSession = pasteSessionRef.current;
· ───────────┬───────────
· ╰── Cannot access ref value during render
794 │
╰────
help: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/refs
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/client.ts:1269:11]
1268 │ extNotificationHandlers.set(CLIENT_METHODS.mcp_message, (params) =>
1269 │ Schema.decodeUnknownEffect(AcpSchemaV2.MessageMcpNotification)(params).pipe(
· ──────────────────────────
1270 │ Effect.mapError(() => AcpError.AcpRequestError.invalidParams()),
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/schema.test.ts:18:12]
17 │ const command = { name: "plan", description: "Make a plan", input: { hint: "Task" } };
18 │ expect(Schema.is(V1.AvailableCommand)(command)).toBe(true);
· ─────────
19 │ expect(
╰────
⚠ t3code(no-inline-schema-compile): Hoist Schema.is(...) to module scope: the compiled function is rebuilt on every call. Move it to a module-level const.
╭─[packages/effect-acp/src/schema.test.ts:20:7]
19 │ expect(
20 │ Schema.is(V2.AvailableCommand)({ ...command, input: { type: "text", hint: "Task" } }),
· ─────────
21 │ ).toBe(true);
╰────
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx:814:17]
813 │ <div
814 │ key={`${index}:${check.name}:${check.url ?? ""}`}
· ─────────────────────────────────────────────────
815 │ className="group flex items-center gap-2 rounded-md pr-1 hover:bg-accent/60"
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ t3code(no-inline-schema-compile): Hoist Schema.decodeUnknownEffect(...) to module scope: both the inline schema literal and the compiled function are rebuilt on every call. Move the compiled function to a module-level const.
╭─[packages/effect-acp/src/errors.test.ts:129:28]
128 │ const secret = "acp-summary-secret";
129 │ const cause = yield* Schema.decodeUnknownEffect(
· ──────────────────────────
130 │ Schema.Struct({
╰────
⚠ react(static-components): Cannot create components during render
╭─[apps/mobile/src/features/terminal/NativeTerminalSurface.tsx:234:10]
196 │ const { onInput, onResize } = props;
197 │ const NativeTerminalSurfaceView = resolveNativeTerminalSurfaceView();
· ────────────────┬───────────────
· ╰── The component is created during render here
198 │ const hasNativeSurface = Boolean(NativeTerminalSurfaceView);
199 │
200 │ useEffect(() => {
201 │ terminalDebugLog("native:surface", {
202 │ terminalKey: props.terminalKey,
203 │ native: hasNativeSurface,
204 │ hardwareKeyRevision: getNativeTerminalHardwareKeyRevision(),
205 │ bufferLen: props.buffer.length,
206 │ isRunning: props.isRunning,
207 │ });
208 │ }, [hasNativeSurface, props.buffer.length, props.isRunning, props.terminalKey]);
209 │ const handleNativeInput = useCallback(
210 │ (event: NativeSyntheticEvent<TerminalInputEvent>) => {
211 │ if (!props.isRunning || props.readOnly) {
212 │ return;
213 │ }
214 │ terminalDebugLog("native:onInput", {
215 │ codes: Array.from(event.nativeEvent.data, (char) => char.codePointAt(0)),
216 │ });
217 │ onInput(event.nativeEvent.data);
218 │ },
219 │ [onInput, props.isRunning, props.readOnly],
220 │ );
221 │ const handleNativeResize = useCallback(
222 │ (event: NativeSyntheticEvent<TerminalResizeEvent>) => {
223 │ onResize({
224 │ cols: event.nativeEvent.cols,
225 │ rows: event.nativeEvent.rows,
226 │ });
227 │ },
228 │ [onResize],
229 │ );
230 │
231 │ if (NativeTerminalSurfaceView) {
232 │ return (
233 │ <View style={props.style}>
234 │ <NativeTerminalSurfaceView
· ────────────┬────────────
· ╰── This component is created during render
235 │ appearanceScheme={themeAppearance}
╰────
help: Components created during render will reset their state each time they are created. Declare components outside of render
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/terminal/terminalLaunchContext.ts:117:5]
112 │ const [entry, setEntry] = useState(() => ({ key: input.targetKey, location: candidate }));
113 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
114 │ if (entry.key === input.targetKey && (entry.location !== null || candidate === null)) {
115 │ return;
116 │ }
117 │ setEntry({ key: input.targetKey, location: candidate });
· ────┬───
· ╰── Avoid calling setState() directly within an effect
118 │ }, [candidate, entry.key, entry.location, input.targetKey]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(no-array-index-key): Usage of Array index in keys is not allowed
╭─[apps/mobile/src/features/terminal/TerminalContextSheet.tsx:72:15]
71 │ <Pressable
72 │ key={index}
· ───────────
73 │ accessibilityRole="button"
╰────
help: Use a unique data-dependent key to avoid unnecessary rerenders
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/threads/use-worktree-setup.ts:30:40]
28 │ const snapshot = resolveWorktreeSetupSnapshot(input.threadId, query.data, live);
29 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
30 │ if (snapshot && snapshot !== live) setHeld({ key, snapshot });
· ───┬───
· ╰── Avoid calling setState() directly within an effect
31 │ }, [key, live, snapshot]);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-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.
⚠ 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
⚠ react(exhaustive-effect-dependencies): Found extra effect dependencies
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:215:7]
214 │ }
215 │ }, [wrappedRender]);
· ──────┬──────
· ╰── Unnecessary dependency `wrappedRender`
216 │
╰────
help: Extra dependencies can cause an effect to fire more often than it should, resulting in performance problems such as excessive renders and side effects
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:817:35]
816 │ >
817 │ <AdaptiveWorkspaceContext value={contextValue}>
· ────────────────────
818 │ <NativeWorkspaceInspectorContext
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(jsx-no-constructed-context-values): The Context `value` prop should not be constructed.
╭─[apps/mobile/src/features/layout/AdaptiveWorkspaceLayout.tsx:832:42]
831 │ >
832 │ <AdaptiveWorkspaceContext.Provider value={contextValue}>
· ────────────────────
833 │ <WindowHingeContext value={windowHinge}>
╰────
help: Wrap the `value` prop in useMemo() or useCallback(), or use a constant value to prevent unnecessary re-renders.
Alternatively, move the value outside the render function if it doesn't depend on props or state.
⚠ react(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
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:566:7]
565 │ let afterSequence = created[0]!.sequence;
566 │ ╭─▶ for (let index = 1; index <= 32; index += 1) {
567 │ │ const nextEvent = {
568 │ │ id: EventId.make(`event:foundation-stream-race:${index}`),
569 │ │ type: "thread.metadata-updated" as const,
570 │ │ threadId,
571 │ │ providerInstanceId,
572 │ │ occurredAt: now,
573 │ │ payload: { ...thread, title: `Race update ${index}` },
574 │ │ } satisfies OrchestrationV2DomainEvent;
575 │ │ const reader = yield* eventSink
576 │ │ .stream({ threadId, afterSequence })
577 │ │ .pipe(Stream.runHead, Effect.forkChild);
578 │ │ yield* Effect.yieldNow;
579 │ │ const written = yield* eventSink.write({ events: [nextEvent] });
580 │ │ const received = yield* Fiber.join(reader);
581 │ │ if (Option.isNone(received)) {
582 │ │ return yield* Effect.die("The event stream ended before delivering the live event.");
583 │ │ }
584 │ │ assert.equal(received.value.sequence, written[0]?.sequence);
585 │ │ assert.equal(received.value.event.id, nextEvent.id);
586 │ │ afterSequence = received.value.sequence;
587 │ ╰─▶ }
588 │ }),
╰────
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/server/src/orchestration-v2/FoundationPersistence.test.ts:2327:9]
2326 │ let settled = false;
2327 │ ╭─▶ while (!settled) {
2328 │ │ settled = (yield* outbox.listByCommandId(commandId)).every(
2329 │ │ (effect) => effect.status === "succeeded",
2330 │ │ );
2331 │ │ if (!settled) yield* Effect.yieldNow;
2332 │ ╰─▶ }
2333 │ }).pipe(Effect.provide(layerWorker), Effect.scoped);
╰────
⚠ 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.
⚠ react(immutability): This value cannot be modified
╭─[apps/mobile/src/features/connection/ConnectionStatusDot.tsx:58:7]
53 │ function usePulseAnimation(pulse: boolean) {
54 │ const pulseProgress = useSharedValue(0);
· ──────┬──────
· ╰── `pulseProgress` originates here
55 │
56 │ useEffect(() => {
57 │ if (pulse) {
58 │ pulseProgress.value = withRepeat(
· ──────┬──────
· ╰── `pulseProgress` cannot be modified
59 │ withTiming(1, {
╰────
help: Modifying a value returned from a hook is not allowed. Consider moving the modification into the hook where the value is constructed
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/immutability
⚠ react(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/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
⚠ unicorn(prefer-set-has): should be a `Set`, and use `.has()` to check existence or non-existence.
╭─[apps/web/src/components/pullRequest/pullRequestList.logic.ts:187:9]
186 │ ): boolean {
187 │ const labels = entry.labels.map((label) => label.name.trim().toLowerCase());
· ─────────────────────────────────────────────────────────────────────
188 │ const holds = (label: string) => labels.includes(label.trim().toLowerCase());
╰────
help: Switch to `Set`
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:79:5]
76 │
77 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
78 │ const { host, code } = parsePairingUrl(connectionPairingUrl);
79 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
80 │ setCodeInput(code);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:89:5]
82 │
83 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
84 │ if (routePairingUrl.length === 0) {
85 │ return;
86 │ }
87 │
88 │ const { host, code } = parsePairingUrl(routePairingUrl);
89 │ setHostInput(host);
· ──────┬─────
· ╰── Avoid calling setState() directly within an effect
90 │ setCodeInput(code);
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx:95:7]
92 │
93 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
94 │ if (pairingConnectionError) {
95 │ setIsSubmitting(false);
· ───────┬───────
· ╰── Avoid calling setState() directly within an effect
96 │ }
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ 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.
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:123:7]
118 │
119 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
120 │ if (orientationSettled) return;
121 │ const orientation = getNativeShowcaseOrientation();
122 │ if (orientation === null) {
123 │ setOrientationSettled(true);
· ──────────┬──────────
· ╰── Avoid calling setState() directly within an effect
124 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ react(set-state-in-effect): Calling setState synchronously within an effect can trigger cascading renders
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:304:7]
292 │
293 │ useEffect(() => {
· ────┬────
· ╰── This is the containing effect
294 │ if (
295 │ scene === null ||
296 │ requestedScene === null ||
297 │ scene !== requestedScene ||
298 │ !hasFixture ||
299 │ !orientationSettled ||
300 │ !themeApplied ||
301 │ (scene === "agent-activity" && !agentActivityStaged) ||
302 │ !isShowcaseNativeContentReady({ scene, themeId, renderSignal })
303 │ ) {
304 │ setReadyScene(null);
· ──────┬──────
· ╰── Avoid calling setState() directly within an effect
305 │ return;
╰────
help: Effects should synchronize React with external systems. Calling setState synchronously inside an effect starts another render and is usually unnecessary. Derive the value during render, initialize state directly, or update it from the event that caused the change. Use an effect only when synchronizing with an external system.
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect
⚠ eslint(no-unused-vars): Variable 'lastOutcome' is declared but never used. Unused variables should start with a '_'.
╭─[apps/mobile/src/features/showcase/ShowcaseCaptureCoordinator.tsx:128:9]
127 │ let cancelled = false;
128 │ let lastOutcome: string | null = null;
· ─────┬─────
· ╰── 'lastOutcome' is declared here
129 │ void retryShowcaseOperation(async () => applyNativeShowcaseOrientation(orientation), {
╰────
help: Consider removing this declaration.
⚠ react(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
⚠ 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/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
⚠ 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(prefer-set-has): should be a `Set`, and use `.has()` to check existence or non-existence.
╭─[apps/web/src/components/chat/useComposerSend.ts:985:13]
984 │ const changedBeforeDecline = draftChangedSinceSend();
985 │ ╭─▶ const pendingIdsBeforeDecline = pendingApprovalsRef.current.map(
986 │ │ (approval) => approval.requestId,
987 │ ╰─▶ );
988 │ const approvalResponding = approvalsToDecline.some((approval) =>
╰────
help: Switch to `Set`
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CustomSnoozeDialog.tsx:140:58]
139 │ {...(weekStartsOn === undefined ? {} : { weekStartsOn })}
140 │ disabled={{ before: new Date(new Date().setHours(0, 0, 0, 0)) }}
· ─────┬────
· ╰── Cannot call impure function
141 │ onSelect={(selected) => {
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
⚠ t3code(no-polling-loop-in-tests): Polling loop in a test. Spinning on `yieldNow`/`sleep` is scheduler- and load-dependent. Await the `Deferred`, `Queue.take`, `Stream` element, `drain()`, or `expect.poll` that marks the milestone.
╭─[apps/mobile/src/features/agent-awareness/remoteRegistration.test.ts:223:5]
222 │ let idlePasses = 0;
223 │ ╭─▶ for (;;) {
224 │ │ yield* Effect.promise(() => Promise.resolve());
225 │ │ const pending = backgroundRuntime.pending.shift();
226 │ │ if (!pending) {
227 │ │ idlePasses++;
228 │ │ if (idlePasses >= 3) {
229 │ │ return;
230 │ │ }
231 │ │ continue;
232 │ │ }
233 │ │ idlePasses = 0;
234 │ │ const exit = yield* Effect.exit(
235 │ │ pending.operation as Effect.Effect<unknown, unknown, ManagedRelay.ManagedRelayClient>,
236 │ │ );
237 │ │ yield* Effect.sync(() => {
238 │ │ pending.resolve(exit);
239 │ │ });
240 │ ╰─▶ }
241 │ },
╰────
⚠ eslint(no-empty-pattern): Empty array binding pattern
╭─[apps/server/src/pullRequest/PullRequestService.test.ts:1429:12]
1428 │
1429 │ for (const [] of [
· ──
1430 │ ["github", "github.com"],
╰────
help: Passing non-iterable values (null, undefined, numbers, booleans, etc.) will result in a runtime error because these values are not iterable.
⚠ eslint(no-unused-vars): Parameter '_' is declared but never used.
╭─[packages/shared/src/qrCode.ts:458:44]
457 │ ): Array<byte> {
458 │ let result: Array<byte> = divisor.map((_) => 0);
· ┬
· ╰── '_' is declared here
459 │ for (const b of data) {
╰────
help: Consider removing this parameter.
⚠ eslint(no-unused-vars): Variable 'claudeCaps' is declared but never used. Unused variables should start with a '_'.
╭─[packages/shared/src/model.test.ts:36:7]
35 │
36 │ const claudeCaps: ModelCapabilities = createModelCapabilities({
· ─────┬────
· ╰── 'claudeCaps' is declared here
37 │ optionDescriptors: [
╰────
help: Consider removing this declaration.
⚠ 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.
⚠ 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");
╰────
⚠ unicorn(prefer-string-starts-ends-with): Prefer String#startsWith over a regex with a caret.
╭─[apps/server/src/vcs/GitVcsDriverCore.ts:509:11]
508 │ GIT_DIAGNOSTIC_LINE_PATTERN.test(line) ||
509 │ (!/^remote:/.test(line) && SSH_TRANSPORT_REFUSAL_PATTERN.test(line)),
· ───────────────
510 │ )
╰────
help: Replace `/^remote:/.test(line)` with `line.startsWith('remote:')`.
⚠ eslint(no-unused-vars): Identifier 'HookForwarder' is imported but never used.
╭─[infra/relay/src/http/Api.ts:69:13]
68 │ import * as EnvironmentLinks from "../environments/EnvironmentLinks.ts";
69 │ import * as HookForwarder from "../hooks/HookForwarder.ts";
· ──────┬──────
· ╰── 'HookForwarder' is imported here
70 │ import * as HeldHooks from "../hooks/HeldHooks.ts";
╰────
help: Consider removing this import.
⚠ 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(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
⚠ eslint(no-unused-vars): Function 'normalizeTerminalContextSelection' is declared but never used.
╭─[apps/web/src/lib/terminalContext.ts:56:10]
55 │
56 │ function normalizeTerminalContextSelection(
· ────────────────┬────────────────
· ╰── 'normalizeTerminalContextSelection' is declared here
57 │ selection: TerminalContextSelection,
╰────
help: Consider removing this declaration.
⚠ eslint(no-unused-vars): Function 'assertUserMessagesExclude' is declared but never used.
╭─[apps/server/src/orchestration-v2/testkit/fixtures/shared.ts:1398:10]
1397 │
1398 │ function assertUserMessagesExclude(
· ────────────┬────────────
· ╰── 'assertUserMessagesExclude' is declared here
1399 │ projection: OrchestrationV2ThreadProjection,
╰────
help: Consider removing this declaration.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/web/src/lib/composerContextReferences.ts:90:40]
89 │ let cursor = prompt.length;
90 │ for (const occurrence of occurrences.reverse()) {
· ───────
91 │ let { start, end } = occurrence;
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-new-array): Do not use `new Array(singleArgument)`.
╭─[apps/web/src/terminal/ghostty/core.ts:194:19]
193 │ const count = Math.min(CHUNK_SIZE, graphemeLength - start);
194 │ const codes = new Array<number>(count);
· ────────────────────────
195 │ for (let index = 0; index < count; index += 1) {
╰────
help: It's not clear whether the argument is meant to be the length of the array or the only element. If the argument is the array's length, consider using `Array.from({ length: n })`. If the argument is the only element, use `[element]`.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:138:28]
137 │ visit(parser.parse(markdown));
138 │ for (const edit of edits.reverse())
· ───────
139 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:169:28]
168 │ visit(parser.parse(markdown));
169 │ for (const edit of edits.reverse())
· ───────
170 │ markdown = markdown.slice(0, edit.start) + edit.content + markdown.slice(edit.end);
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ unicorn(no-array-reverse): Use `Array#toReversed()` instead of `Array#reverse()`.
╭─[apps/mobile/src/lib/markdownDocument.ts:223:38]
222 │ visit(parser.parse(markdown));
223 │ for (const lineStart of lineStarts.reverse()) {
· ───────
224 │ // The header row may be a lazy line without its container markers (`>` or list indent),
╰────
help: `Array#reverse()` mutates the original array. Use `Array#toReversed()` to return a new reversed array without modifying the original.
⚠ react(purity): Cannot call impure function during render
╭─[apps/web/src/components/CommandPalette.tsx:1996:20]
1995 │ title: inferProjectTitleFromPath(destinationPath),
1996 │ createdAt: new Date().toISOString(),
· ─────┬────
· ╰── Cannot call impure function
1997 │ remoteUrl: addProjectCloneFlow.remoteUrl,
╰────
help: `Date` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component re-renders
note: React Compiler skipped optimizing this component or hook. Additional guidance: https://react.dev/reference/eslint-plugin-react-hooks/lints/purity
Found 0 errors and 362 warnings in 5400 files (5.7s, 8 threads)
Post job cleanup.
Cache hit occurred on the primary key electron-Linux-X64-854e11ddd491bd4f350eebb67a74265df119376a3984c8e153cfe5fc8ced6309, not saving cache.
Post job cleanup.
##[start-action display=Cache full pnpm store;id=__08625919-59f3-45d0-89fc-0ed337f0e1d3.__actions_cache]
Post job cleanup.
[command]/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /home/runner/_work/t3code/t3code --files-from manifest.txt --use-compress-program zstdmt
Sent 994310451 of 994310451 (100.0%), 2017.5 MBs/sec
Cache saved with key: pnpm-full-v1-Linux-X64-3cb0b4d7cff93dc8fe33f2ea73cac71ca25a36270fcb648b9b4a9320151012ef
##[end-action id=__08625919-59f3-45d0-89fc-0ed337f0e1d3.__actions_cache;outcome=success;conclusion=success;duration_ms=4825]
##[start-action display=Cache Vite+;id=__08625919-59f3-45d0-89fc-0ed337f0e1d3.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=__08625919-59f3-45d0-89fc-0ed337f0e1d3.vp_cache;outcome=success;conclusion=success;duration_ms=75]
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/dd17dbf2-7c73-472f-a5f8-c32e08f70e94' 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: 201
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 516
BLACKSMITH_CHECK_RUN_ID: 120670937783
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