fix(dashboard): retrying an older chat answer reruns the latest one
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 72/100
Research direction
Start in registry_source/lib/src/dashboard/dashboard_demo_chat.dart and read _retry(), which restarts with the current _prompt and _scenario and keepMessage: true, then find where the Retry action is wired to each answer. Reproduce by sending two messages, letting both finish, and retrying the first reply. Done when retrying an older answer regenerates that reply and the latest answer is left unchanged. The issue also points to a generated copy under packages/fortal_site, so check whether it needs the same change.
Written by the indexing model from the issue text.
Description
In the dashboard demo's Agent chat (all presets; source registry_source/lib/src/dashboard/dashboard_demo_chat.dart), every answer, including earlier ones, offers Retry answer. Its callback is _retry(), which restarts with the current _prompt and _scenario and keepMessage: true.
Steps: send two messages and let both answers finish, then click Retry answer on the first reply.
Expected: the first reply is regenerated.
Actual: the latest answer is rerun and replaced; the selected reply does not change.
Fix options: bind each retry to its own turn (prompt and scenario), or show the retry action only on the latest answer.
Found by Codex review on btwld/mix-website#6, where the Fortal site embeds this dashboard (generated copy at packages/fortal_site/lib/ui/recipes/dashboard/dashboard_demo_chat.dart).
- Dominant language
- Dart
- Stars
- 24
- Forks
- 5
- Avg merge
- 15h 29m
- Merged PRs (30d)
- 144
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from btwld/remix
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day