Ensure retrying a run attributes requested_by to the retriggering user, not the original requester
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
When a run is retried with the same inputs, requested_by should reflect whoever triggered the retry, not be copied from the original run.
Note: services/hackbot-ui/app/api/runs/[runId]/retrigger/route.ts already appears to do this correctly for UI-triggered retries. Audit any other retry path (for example, an automatic or webhook-driven retry) to make sure the same rule holds there too.
Contributor 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.
Research direction
Start with services/hackbot-ui/app/api/runs/[runId]/retrigger/route.ts, then search the repository for other run-retry or retrigger entry points, including automatic and webhook-driven paths. Check how each path determines requested_by and add or update focused tests where those paths are covered. Done means every retry records the user who triggered that retry rather than the original requester.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100