Skip to content

Reload the executions after fetching results (#110) - #152

Merged
mosoriob merged 2 commits into
developfrom
fix/results-refresh-after-publish
Aug 30, 2026
Merged

mosoriob merged 2 commits into
developfrom
fix/results-refresh-after-publish

Conversation

@mosoriob

Copy link
Copy Markdown
Contributor

Closes the last piece of #110.

What was wrong

Registration writes the execution_result rows server-side. The results table renders
the executions held in MintThread's state, and handlePublishResults refetched only
GetThreadExecution — the pipeline and its counters, not the execution rows that
carry results.

So a successful fetch left the table reading — No results available — until the user
pressed Reload. That is #110's own symptom, still present on the first click.

The fix

MintResults reloads the current page of executions after a successful publish, through
the same onFetchRuns path the Reload button already uses. A failed publish reloads
nothing.

Verification

Live against TACC, thread jx8ibyilmsmg1pvt, model SUBSIDE Allocation Specification:

  • POST /v1/problemStatements/.../subtasks/jx8ibyilmsmg1pvt/outputs → 200
    Outputs registered successfully, one execution_result row written.
  • The registered row was then deleted to restore the "before" state, and one click on
    Fetch results rendered the output with no Reload.

933 tests green. The new assertion was checked to fail against the old code.

🤖 Generated with Claude Code

https://claude.ai/code/session_014wrbumQztWyA6uKoKbHohc

Maximiliano Osorio added 2 commits August 29, 2026 20:39
Picks up 1771200018000_response_variable_standard_variable_fk and the metadata
move of the four array relationships onto modelcatalog_standard_variable, merged
as mintproject/graphql_engine#15. Also picks up the cascade migration (#14),
which the pointer had not yet caught up with.
Registration writes the execution_result rows server-side, but the results
table renders the executions held in MintThread's state, and
handlePublishResults only refetches GetThreadExecution -- the pipeline and
its counters, not the execution rows that carry the results.

So a successful fetch left the table reading "No results available" until
the user pressed Reload. That is #110's own symptom, still present on the
first click.

MintResults now reloads the current page of executions after a successful
publish, through the same onFetchRuns path the Reload button uses. A failed
publish still reloads nothing.

Verified live against TACC on thread jx8ibyilmsmg1pvt: the registered row
was deleted to restore the "before" state, and one click on Fetch results
rendered the output with no Reload.
@vercel

vercel Bot commented Aug 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
monorepo Building Building Preview Aug 30, 2026 1:36am

This branch was successfully deployed

1 active deployment
Preview — 6585ef16 Deployed Aug 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant