fix(price-alert): validate finite and non-negative price floats before converting to u64 cents - #20
Open
yappermoar-boop wants to merge 1 commit into
Conversation
…e converting to u64 cents
|
Someone is attempting to deploy a commit to the Subzero Labs Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added price_resp.price.is_finite() && price_resp.price >= 0.0 validation and .min(u64::MAX as f64) clamping in venus/price-alert/src/lib.rs before casting price float to u64 cents. Previously, receiving NaN, Infinity, or negative price floats from API responses produced undefined integer conversion behavior or invalid alert triggers.