Conversation
mj52951
requested review from
MakMuftic,
mpetrun5,
mpetrunic and
tcar121293
as code owners
|
Go Test coverage is 53.1 %\ ✨ ✨ ✨ |
mpetrun5
previously approved these changes
Apr 2, 2026
|
Go Test coverage is 53.1 %\ ✨ ✨ ✨ |
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
2 participants
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.
In case of different decimals for input and output token, we need to properly scale input amount. Fixes made for across and lifi, similar edge case errors exist on mayan and rhinestone but didn't bother resolving them as they're not used.
Please double check could this break something else or are there more cases of this that I might've missed.
Description
Related Issue Or Context
Closes: #
How Has This Been Tested? Testing details.
Types of changes
Checklist: