ETA in --status is showed using offset from current time, not from the moment session file was written
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Minor problem
I run a long session. In parallel, I print its status using --status. I get ETA based on current time, i.e. ETA grows when I rerun --status after a few seconds.
So I get up to 1 minute (Save = 60) discrepancy with actual ETA for running session.
For a stopped session, ETA in --status would mean ETA if I start right now.
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 by tracing the --status handling and how the session file's write time is used to calculate ETA. Reproduce the issue by rerunning status for a running session, then verify that the ETA stays anchored to the session-file timestamp while a stopped session calculates ETA from the current time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100