cron job DESIDIFF
Open
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Get DESIDIFF jobs running using the database method of tracking what has been done.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the DESIDIFF cron-job entry point and the existing job-tracking code or database schema. Determine how completed work is currently recorded before deciding where the database-based tracking belongs. Done means DESIDIFF jobs run and reliably avoid repeating work that the database records as completed.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100