Dashboard card loses information after HTMX refresh #197

Open
opened 2026-02-09 13:24:19 +00:00 by mprihoda · 3 comments
mprihoda commented 2026-02-09 13:24:19 +00:00 (Migrated from github.com)

Problem

After an HTMX polling refresh, the worktree card loses some information that was present on the initial page load — notably the git worktree state. The card appears to use a different (or incomplete) rendering path for the refreshed content compared to the initial render.

Expected Behavior

The card should display identical information before and after refresh. All data visible on initial load (including git worktree state) must also appear in the HTMX-refreshed fragment.

Investigation Needed

  • Compare the initial full-page card rendering with the HTMX partial response
  • Ensure the same view component is used for both paths
  • Verify all data (git status, review state, progress, PR info) is passed to the renderer in both cases
## Problem After an HTMX polling refresh, the worktree card loses some information that was present on the initial page load — notably the git worktree state. The card appears to use a different (or incomplete) rendering path for the refreshed content compared to the initial render. ## Expected Behavior The card should display identical information before and after refresh. All data visible on initial load (including git worktree state) must also appear in the HTMX-refreshed fragment. ## Investigation Needed - Compare the initial full-page card rendering with the HTMX partial response - Ensure the same view component is used for both paths - Verify all data (git status, review state, progress, PR info) is passed to the renderer in both cases
Member

Intake: agent-ready
Workflow: diagnostic
Reason: all gates passed
Analysis: project-management/issues/IW-197/analysis.md on branch IW-197

Intake: agent-ready Workflow: diagnostic Reason: all gates passed Analysis: project-management/issues/IW-197/analysis.md on branch IW-197
Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin does not compile against the iw-cli core on this branch, so no phase started

iw-cli main changed the tracker port to return TrackerError (#778, #780). The installed kanon plugin still expects String in lib/batch/ForgeCatchUp.scala. This blocks every implement run in iw-cli, not only this issue. Update the kanon plugin to the TrackerError port, then release this issue to agent-ready again. There was no batch-implement.log; these are the last lines of the command output:

[error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7
[error] Found:    Either[iw.core.model.TrackerError, Option[batch.ForgeState]]
[error] Required: Either[String, Option[batch.ForgeState]]
Compilation failed
Implement: needs-human Reason: batch-implement exit 1 — the kanon plugin does not compile against the iw-cli core on this branch, so no phase started iw-cli `main` changed the tracker port to return `TrackerError` (#778, #780). The installed kanon plugin still expects `String` in `lib/batch/ForgeCatchUp.scala`. This blocks every implement run in iw-cli, not only this issue. Update the kanon plugin to the `TrackerError` port, then release this issue to `agent-ready` again. There was no `batch-implement.log`; these are the last lines of the command output: ``` [error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7 [error] Found: Either[iw.core.model.TrackerError, Option[batch.ForgeState]] [error] Required: Either[String, Option[batch.ForgeState]] Compilation failed ```
Member

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/iw-cli#197
No description provided.