Repository navigation
fix(web): keep dashboard on published swissd APIs - #57
Merged
Merged
Conversation
Read the existing run log directly instead of probing the unmerged timeline prototype. Preserve unknown history and capped-response handling, and require one published API request in regression tests. Server-side aggregation and serving metrics remain separate backend work. Refs #55
This was referenced Oct 12, 2026
imneov
marked this pull request as ready for review
October 12, 2026 17:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does and why
Keep the current Console dashboard independent of unmerged swissd work.
The deployment activity reader previously tried
/api/runs/timelinebefore falling back to the published run log. The timeline endpoint is only an unmerged local backend prototype, so probing it violated the agreed delivery boundary: implement the Console dashboard using existing backend capabilities first, then review future backend metrics separately.This patch:
/api/runs?limit=500endpoint and aggregates the returned audit records on the client.No swissd changes, restart, or unreleased endpoint are required for this Console patch. Full server-side aggregation and runtime serving metrics remain separate work.
Which issue(s) this PR fixes
Refs #55 and modelsphere/swiss#19 for the agreed frontend/backend delivery boundary.
Corrects the optional unmerged endpoint probe introduced in the dashboard implementation, #54. It does not implement or close either serving-metrics issue.
How it was tested
npm run typecheck: passed for Console and Swiss standalone configurations.npm test: 31 files, 272 tests passed.npm run build: passed; the existing large-chunk warning remains.Checks
npm run typecheck && npm test && npm run buildinweb/Notes for reviewers
Start with
web/src/modules/inferences/dashboard-api.tsand its regression tests. The existing 500-row limit means high-volume or long histories may still be incomplete; the UI explicitly reports that limitation instead of inventing a complete curve.The local swissd timeline prototype is intentionally not submitted or consumed by this PR. This draft is for user review and should not be merged automatically.
Release note