Literal Eval to Eval (Algorand)#4885
Open
mdulin2 wants to merge 1 commit into
Open
Conversation
mdulin2
requested review from
SEJeff,
bemic,
djb15,
evan-gray,
johnsaigle,
kcsongor,
panoel and
pleasew8t
as code owners
June 29, 2026 21:32
mdulin2
force-pushed
the
remove-eval-algorand
branch
from
June 29, 2026 22:04
7defdd7 to
8e7a06f
Compare
djb15
approved these changes
Jun 30, 2026
bemic
approved these changes
Jul 1, 2026
johnsaigle
force-pushed
the
remove-eval-algorand
branch
from
July 3, 2026 10:53
8e7a06f to
06de448
Compare
johnsaigle
force-pushed
the
remove-eval-algorand
branch
from
July 17, 2026 15:34
06de448 to
385d0a7
Compare
Contributor
Author
|
The Sui build process seems to be broken. This only touched the Algorand tests, so I hope we can just ignore that test failure and merge this. |
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
3 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.
The Python
eval()is a known bad sink for code execution bugs. Although there's no security impact with this currently, we're proactively changing theeval()toliteral_eval()to prevent this from ever becoming an issue.