Store started timestamp, completed timestamp, and duration in Task DB
Open
Nobody has claimed this yet.
distributed
enhancement
- Dominant language
- Python
- Stars
- 621
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Instead of just the completed timestamp.
This helps when:
- you're curious how long the scan you just started will take
- you're curious if your coworker started an analysis on a particular file yet
- there's a problem with modules taking absurdly long times to run
Contributor guide
No contributing guide indexed for this repository
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 by locating the Task DB implementation and the code that currently stores the completed timestamp. Trace how task start and completion are recorded, then identify existing tests for this persistence path. Done means the database stores started and completed timestamps plus duration, supporting progress and unusually long-running task checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100