-
Notifications
You must be signed in to change notification settings - Fork 3
fix(api): job search status refresh #421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Gitdowski
wants to merge
5
commits into
main
Choose a base branch
from
fix-api-job-search-status-refresh
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0d22ccc
docs(api): clarify search_jobs snapshot status and tag-and semantics
Gitdowski b6bdb57
fix(api): refresh running job statuses in search_jobs by default
Gitdowski dd5c2e7
docs(mcp): clarify status-check workflow and remove polling implication
Gitdowski 6e500a2
fix(api): enforce statuses filter after search_jobs status refresh
Gitdowski 98db8df
fix: test refresh running job status during search
Gitdowski File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm yeah, this can get expensive if there are many jobs in the query (and many of them to be refreshed)
I think in terms of pattern we should move away entirely on doing these implicit updates on user read requests and have a background task take care of it.
Here is a brief summary of the proposal. You could start to use this as a basis for a new PR or I could work on it next week
Move ingestion out of the request path.
GET /jobs/{id}becomes a pureSELECT; a single background process is the only writer of job state and the only component aware of both executorlib and the DB.add_done_callback()for lower latency.cache_directoryfor completed*_o.h5outputs, keyed bycache_key.SUBMITTED → RUNNING → FINISHED → INGESTING → INGESTED(+ failure states). Separating "executor finished" from "results in DB" is what fixes the wrong-status queries.[SKIP LOCKED](https://www.postgresql.org/docs/current/sql-select.html#SQL-FOR-UPDATE-SHARE), idempotent upserts, retry limit.pg_advisory_lock(otherwise it runs once per uvicorn worker).Trade-off: status is stale by at most one poll interval — correct-but-delayed instead of fast-but-wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we scratch this PR, or do you want to approve/merge this in the meantime?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can merge it if you want, we just need to make sure to remove this logic again since it can potentially stall the process for quite a while