influxdata / influxdata/kapacitor
endless loop bug if cron expression is wrong etc 0 0/0 10 * * ? *
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
This issue has no description.
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
The issue names only a malformed cron expression and does not identify files, tests, or an entry point. Start by reproducing the expression `0 0/0 10 * * ? *` and trace the cron parsing or scheduling path; done means invalid input no longer causes an endless loop and the behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100