Fix literal from addresses in ETHTx tasks - #23717
Open
ChrisWozniak wants to merge 1 commit into
Open
Conversation
product-security-plaid-production
Bot
requested review from
DylanTinianov,
Krish-vemula,
Unheilbar,
amit-momin,
bolekk,
dhaidashenko,
ilija42,
pavel-raykov,
prashantkumar1982,
silaslenihan and
yashnevatia
September 11, 2026 03:31
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
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.
Fixes #21768
Requires
Supports
Summary
ethtxtask'sfromparameter.frombehavior.Testing
./tools/test/.bin/test --ai-output -v -count=1 -run '^TestETHTxTask$' ./core/services/pipelineRisk assessment
Low. The change is limited to
ETHTxTaskparameter resolution and is covered by the focused task suite.Review focus
Please verify that
literalAddressSlicerecognizes only valid literal addresses and falls through to the existing JSON/variable resolvers for all other inputs.