How to explain the end_time is less than start_time in 2018 trace's batch_task?
Open
- Dominant language
- Jupyter Notebook
- Stars
- 2.2k
- Forks
- 482
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that in the batch_task table, some records' end_time is 0. Is it normal, or if I misunderstood it?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the 2018 trace's batch_task table and the records where end_time is 0. Determine whether the value is expected or indicates an incomplete task, then document the meaning of end_time and why it can be less than start_time.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100