Loyal-Young opened a new pull request, #6419:
URL: https://github.com/apache/rocketmq-dashboard/pull/6419

   ### Which Issue(s) This PR Fixes
   
   Fixes #6411
   
   ### Brief Description
   
   An assistant run can stop or fail after a tool starts but before its result 
arrives. The transcript currently continues to show that tool as Running, 
including an animated progress bar, even when replaying a terminal run.
   
   Pass the run status into tool rendering and show a neutral, localized “No 
result” state for unfinished tools on terminal runs. Preserve the recorded tool 
data and any results that did arrive; a terminal run alone does not establish 
whether the tool succeeded or failed.
   
   ### How Did You Test This Change?
   
   From `web`:
   
   - `node node_modules/vitest/vitest.mjs run 
src/pages/ai/components/__tests__/AssistantBubble.test.tsx 
src/pages/ai/components/__tests__/ToolBlock.test.tsx --pool=threads 
--maxWorkers=1`: 39 tests passed. The three new terminal-status regressions 
failed before the fix.
   - ESLint and Prettier on the four changed frontend files: passed.
   - `node node_modules/typescript/bin/tsc -p tsconfig.app.json --noEmit 
--pretty false --composite false --incremental false`: passed.
   - `git diff --check`: passed.
   
   No browser end-to-end test was run. Backend architecture checks are not 
affected by this frontend-only change.
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits
   - [x] Tests added for non-trivial changes, test names end in `Test`
   - [x] New UI text has both Chinese and English entries
   - [x] No backend architecture changes or new source files
   - [x] In-app status/help text describes the changed behavior
   
   ### AI Assistance
   
   AI assistance was used to inspect the run/tool rendering paths, draft the 
fix and regression tests, and run local checks. The verification results above 
describe the checks actually executed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to