influxdata / influxdata/kapacitor
eval on 0 by division crush Kapacitor
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hi,
We found that in case you have an eval node in which, for any situation, en up with a division by 0 (x / 0) kapacitor suffers and crush.
Wouldn't be possible to manage that kind of situations without this behaviour? Giving maybe a 0, null, NA... would be "better" than the current state?
Contributor guide
Research direction
Start by reproducing the crash with a Kapacitor eval node that evaluates x / 0, then trace the eval-node handling for division by zero. The issue does not specify whether the result should be 0, null, or NA, so confirm the intended non-crashing behavior and add coverage demonstrating that the chosen result no longer crashes Kapacitor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100