Refresh repository jobs when a background sync finishes between dashboard polls
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, python
- Domain
- frontend
Research direction
Read dashboard/src/views/RepositoryDetailView.vue, especially the job list setup around line 40 and refresh logic around line 106. Update the refresh condition to account for last_synced_at advancing even when both responses are idle, then extend the refresh test with two idle responses, a new sync timestamp, and a newly added job requiring approval. Done when the job list and approval checklist update without a page reload.
Written by the indexing model from the issue text.
Description
Likelihood is moderate on actively maintained repositories. A background sync that starts and finishes between dashboard polls can leave the job list and approval checklist stale until reload. The fix is localized to the repository detail view and its refresh test.
dashboard/src/views/RepositoryDetailView.vue:40 builds the job list and capability checklist from the repository's latest job IDs plus the cached app.jobs. The refresh at line 106 only reloads app.jobs after it observes syncing change from true to false. With a 60-second idle poll, a normal fast sync can complete entirely between two reads. The header can then show an updated job count while a new job is absent from the list and its required approval is missing from the checklist.
Refresh the job data when last_synced_at advances, including when both reads return syncing: false. Test two consecutive idle responses with a new sync timestamp and a newly added job requiring approval.
Opened by SecondShift from run 1 at 07bfa80ed42b.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 322
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from piotrekno1/second-shift
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#395 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day