fix(web): add delete confirmation modal and fit table to viewport #186
Annotations
4 errors and 1 warning
|
|
|
apps/web/src/features/session/ConversationOutput.test.tsx#L79
TestingLibraryElementError: Unable to find an element with the text: API retry (attempt 1/3). This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.
Ignored nodes: comments, script, style
<body>
<div>
<div
class="flex flex-col h-full bg-bg"
data-testid="conversation-output"
>
<div
aria-label="Session output"
aria-live="polite"
class="flex-1 overflow-y-auto overflow-x-hidden px-6 py-4"
role="log"
>
<div
class="py-1"
>
<span
class="text-xs font-mono text-dim"
>
//
API retry (attempt 1/3)
</span>
</div>
<span
class="inline-block w-2 h-4 bg-accent animate-pulse mt-2"
data-testid="conversation-cursor"
/>
</div>
</div>
</div>
</body>
❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19
❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38
❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17
❯ getByText node_modules/@testing-library/dom/dist/query-helpers.js:95:19
❯ src/features/session/ConversationOutput.test.tsx:79:19
|
|
apps/web/src/features/session/ConversationOutput.test.tsx#L33
TestingLibraryElementError: Unable to find an element with the text: No output yet.. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.
Ignored nodes: comments, script, style
<body>
<div>
<div
class="flex flex-col h-full bg-bg"
data-testid="conversation-output"
>
<div
aria-label="Session output"
aria-live="polite"
class="flex-1 overflow-y-auto overflow-x-hidden px-6 py-4"
role="log"
>
<p
class="text-dim text-sm font-mono"
>
// no output yet
</p>
</div>
</div>
</div>
</body>
❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19
❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38
❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17
❯ getByText node_modules/@testing-library/dom/dist/query-helpers.js:95:19
❯ src/features/session/ConversationOutput.test.tsx:33:19
|
|
apps/web/src/features/session/ContainerSession.test.tsx#L203
TestingLibraryElementError: Unable to find an element by: [data-testid="session-status"]
Ignored nodes: comments, script, style
<body>
<div>
<div
class="h-screen bg-bg text-ink flex flex-col"
data-testid="container-session"
>
<div
class="h-14 flex items-center px-4 gap-3 shrink-0 border-b border-rule bg-bg2"
>
<button
class="text-dim text-sm hover:text-ink2 transition-colors cursor-pointer font-mono"
data-testid="back-button"
>
←
Back
</button>
<span
class="text-dim2"
>
│
</span>
<span
class="text-ink text-sm font-sans"
>
acme/helprs
</span>
<span
class="text-dim font-mono text-xs"
>
#
42
</span>
<span
class="inline-flex items-center gap-1 px-2 py-0.5 rounded-default border font-mono text-[11px] font-medium leading-tight border-accent/30 text-accent bg-accent-dim/20 "
>
challenge-me
</span>
<div
class="ml-auto flex items-center gap-3"
>
<span
class="inline-flex items-center gap-1 px-2 py-0.5 rounded-default border font-mono text-[11px] font-medium leading-tight border-ok/30 text-ok bg-ok/10 "
>
running
</span>
<button
class="inline-flex items-center justify-center gap-2 px-4 py-2 rounded-button font-mono text-sm font-medium transition-all cursor-pointer disabled:opacity-40 disabled:cursor-not-allowed text-danger bg-danger/8 border border-danger/35 hover:bg-danger/15 active:bg-danger/20 "
data-testid="stop-button"
>
Stop
</button>
</div>
</div>
<div
class="flex-1 min-h-0 flex"
>
<div
class="flex-1 min-w-0 flex flex-col"
>
<div
class="flex-1 min-h-0"
>
<div
class="flex flex-col h-full bg-bg"
data-testid="conversation-output"
>
<div
aria-label="Session output"
aria-live="polite"
class="flex-1 overflow-y-auto overflow-x-hidden px-6 py-4"
role="log"
>
<div
class="py-1"
>
<span
class="text-xs font-mono text-dim"
>
//
Starting challenge-me for acme/helprs#42...
</span>
</div>
<span
class="inline-block w-2 h-4 bg-accent animate-pulse mt-2"
data-testid="conversation-cursor"
/>
</div>
</div>
</div>
<div
class="shrink-0 px-4 py-3 flex items-center gap-3 border-t border-rule bg-bg2"
>
<span
class="text-accent font-mono text-sm select-none"
>
❯
</span>
<input
class="flex-1 bg-transparent text-ink text-sm font-sans outline-none placeholder:text-dim2 disabled:opacity-50"
data-testid="message-input"
placeholder="Type your answer..."
type="text"
value=""
/>
<button
class="inline-flex items-center justify-center gap-2 px-4 py-2 rounded-button font-mono text-sm font-medium transition-all cursor-pointer disabled:opacity-40 disabled:cursor-not-allowed bg-accent text-bg font-semibold shadow-glow-accent hover:brightness-110 active:brightness-90 "
data-testid="send-button"
disabled=""
>
Send
</button>
</div>
</div>
<div
class="w-[260px] shrink-0 border-l border-rule bg-bg2 overflow-y-auto"
>
<div
class="p-4 space-y-6"
>
<section>
|
|
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
The logs for this run have expired and are no longer available.
Loading