New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[processor/deltatocumulative]: timer-based expiry #31625
Conversation
@RichieSams please take a look :) |
aggr streams.Aggregator[data.Number] | ||
exp *streams.Expiry[data.Number] | ||
aggr streams.Aggregator[data.Number] | ||
stale *staleness.Staleness[data.Number] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor: You could name this say, nums
in preparation for having multiple. (IE for histograms, etc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's do that when its needed. I'd like to experiment with the type system more if we can't just drop the datapoint narrowing on the aggregator altogether
Added a minor naming comment. Otherwise LGTM :) |
Thank you, @sh0rez! |
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #31488 was recently merged and has broken `build-and-test` for all builds due to a lint failure. It looks like two PRs were worked on in parallel, the aforementioned one, as well as #31625. #31625 renamed `exp` to `stale`, but the most recently merged PR was referencing the original `exp` variable. This is an unreleased component, and is simply fixing a bug, so I don't think this should have a changelog.
**Description:** Moves from complex preemptive expiry to a plain 1 minute timer **Link to tracking Issue:** open-telemetry#31615 (comment) Resolves open-telemetry#31615
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> open-telemetry#31488 was recently merged and has broken `build-and-test` for all builds due to a lint failure. It looks like two PRs were worked on in parallel, the aforementioned one, as well as open-telemetry#31625. open-telemetry#31625 renamed `exp` to `stale`, but the most recently merged PR was referencing the original `exp` variable. This is an unreleased component, and is simply fixing a bug, so I don't think this should have a changelog.
**Description:** Moves from complex preemptive expiry to a plain 1 minute timer **Link to tracking Issue:** open-telemetry#31615 (comment) Resolves open-telemetry#31615
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> open-telemetry#31488 was recently merged and has broken `build-and-test` for all builds due to a lint failure. It looks like two PRs were worked on in parallel, the aforementioned one, as well as open-telemetry#31625. open-telemetry#31625 renamed `exp` to `stale`, but the most recently merged PR was referencing the original `exp` variable. This is an unreleased component, and is simply fixing a bug, so I don't think this should have a changelog.
Description: Moves from complex preemptive expiry to a plain 1 minute timer
Link to tracking Issue: #31615 (comment)
Resolves #31615