Auto-migration timing
Open
Nobody has claimed this yet.
Enhancement
Post-it
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
The task performing phase migration is scheduled every 300 seconds:
That can be confusing
- If feasible, we should trigger the phase migration check at the moment a phase starts. This way we do not wait, and do not run the tests every 300 seconds on the site worker.
- Otherwise, let's add a warning such as: "The migration may start up to x seconds after the beginning of the phase" near the option.
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 src/settings/base.py at line 225 and trace the task that performs phase migration and its 300-second schedule. Check how phase starts and the site worker are represented before deciding whether to trigger the check at phase start or add the proposed warning; done means one of those two behaviors is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100