Skip to content

fix(web): panel button keeps its counts until the tab that shows them… #1019

fix(web): panel button keeps its counts until the tab that shows them…

fix(web): panel button keeps its counts until the tab that shows them… #1019

Triggered via push September 3, 2026 05:44
Status Success
Total duration 7m 7s
Artifacts

ci.yml

on: push
Format, Lint, Typecheck, Test, Build
7m 3s
Format, Lint, Typecheck, Test, Build
Browser Test
3m 56s
Browser Test
Release Smoke
1m 6s
Release Smoke
Deploy app.threadlines.dev  /  deploy
Deploy app.threadlines.dev / deploy
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
unicorn(no-array-reverse): scripts/audit-marketing-media-corners.ts#L122
scripts/audit-marketing-media-corners.ts:122:75: Use `Array#toReversed()` instead of `Array#reverse()`.
eslint(no-unused-vars): apps/web/src/components/chat/rightPanelLauncherState.ts#L27
apps/web/src/components/chat/rightPanelLauncherState.ts:27:15: Type 'ThreadBackgroundRunItem' is imported but never used.
eslint(no-unused-vars): apps/server/src/cli/config.test.ts#L712
apps/server/src/cli/config.test.ts:712:13: Variable 'derivedPaths' is declared but never used. Unused variables should start with a '_'.
react(set-state-in-effect): apps/web/src/components/chat/ComposerPendingDrawingContexts.tsx#L75
apps/web/src/components/chat/ComposerPendingDrawingContexts.tsx:75:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): apps/web/src/components/chat/sessionStartupNotice.tsx#L60
apps/web/src/components/chat/sessionStartupNotice.tsx:60:5: Calling setState synchronously within an effect can trigger cascading renders
react(exhaustive-effect-dependencies): apps/web/src/components/chat/sessionStartupNotice.tsx#L61
apps/web/src/components/chat/sessionStartupNotice.tsx:61:7: Found extra effect dependencies
react(set-state-in-effect): apps/web/src/components/chat/FilePreviewDialog.tsx#L47
apps/web/src/components/chat/FilePreviewDialog.tsx:47:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): apps/web/src/components/chat/ExpandedImageDialog.tsx#L20
apps/web/src/components/chat/ExpandedImageDialog.tsx:20:5: Calling setState synchronously within an effect can trigger cascading renders
react(no-deriving-state-in-effects): apps/web/src/components/chat/ExpandedImageDialog.tsx#L20
apps/web/src/components/chat/ExpandedImageDialog.tsx:20:5: Values derived from props and state should be calculated during render, not in an effect
eslint(no-unused-vars): apps/web/src/components/chat/AgentsPanel.browser.tsx#L82
apps/web/src/components/chat/AgentsPanel.browser.tsx:82:7: Variable 'TERMINAL_RUN' is declared but never used. Unused variables should start with a '_'.