isActive is unreliable
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
`isActive` is completely unreliable for long-running streams. This stream shows as idle despite the fact it's been running for nearly 24 hours. The `lastSeen` field is up-to-date, though, implying that we could use that to determine when a stream is active.
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 stream status entry point where `isActive` and `lastSeen` are populated. Reproduce the long-running stream case described in the issue, compare both fields, and add regression coverage showing that an active stream is not reported as idle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100