Repository navigation
Show the total runs and a last page link on Activity - #9
Merged
github-actions[bot] merged 16 commits intoNov 6, 2026
Merged
Conversation
…nto feat/activity-rework
… address and ok-style filters
…lay button a hover background
…he total and jumps to any page
ddyfad
pushed a commit
that referenced
this pull request
Nov 6, 2026
* Fixed inconsistent flag scales * Fixed inconsistent flag scales * Fixed inconsistent flag scales * Fixed inconsistent flag scales
ddyfad
pushed a commit
that referenced
this pull request
Nov 6, 2026
…y map names Fixes from the 2026-11-06 audit (#9, #10, #15, #19, dot map names): - Replay checks, SJR encoding, route tracing and SJR decoding run in spawn_blocking, as map images already do: files up to 128 MB at gzip's highest level took seconds of CPU on the async workers. - Storage PUTs (viewer files up to ~256 MB) get 10 minutes and streamed downloads 30 minutes instead of the client's 30 s, which covered the whole body and cut off large or slow transfers. - The heartbeat checks its per-IP limit before it looks the key up, so over-limit senders cost no database query. Tested with a closed pool. - Map names made only of dots are refused: names end up in storage keys and URL paths. - Tests that the description and release PUTs need manage_maps, and a success test for the description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Couldn't merge into |
|
Merged into |
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.
Shows the total number of runs under the Activity table, with a link to skip straight to the last page.
Stacked on #8. The website part works with today's API. It only shows the total and the last page once the API change below is live.
API change (needs a deploy to take effect)
Previews only run
web/, so the API part has to go upstream and be deployed to beta.GET /v1/runs(api/crates/api/src/runs/recent.rs):total: runs matching the filters, across all pages.offset(default 0, must be 0 or more): runs to skip. Applied aftercursorif both are given.cursor/next_cursorwork as before.Included: tests, regenerated
api/openapi.json,web/src/api/schema.tsand.sqlxcache, and thedocs/site-api.mdline.To make it live: merge into
sourcejump/sourcejump, then deploy the API to beta (just deploy beta, seedocs/deploy.md).Website
totalfrom the API, any page loads with one request and the pager shows the full count and the last page.total(the API as deployed now), the page falls back to walking forward withcursor. Either order of merging works.Tested against a local API with sample data: every page matched the API's rows for the same offset, including with filters.