feat(rpc): add getTxByTxTrace api, used for ccc testing & debugging #1026
Conversation
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
…o-ethereum into omerfirmak/tx-by-tx-tracer
|
this pr does not change any imports..? why 'goimports -local github.com/scroll-tech/go-ethereum/ -w .' is not ok... |
might be the golang version of CI (encountered the same issue before). btw, what is the original motivation to increase version 1.21? |
colinlyguo
approved these changes
Sep 6, 2024
omerfirmak
approved these changes
Sep 6, 2024
lwedge99
pushed a commit
to sentioxyz/scroll-geth
that referenced
this pull request
Dec 16, 2024
…croll-tech#1026) * ++ * upgrade go lint version * lint * remove a useless "`" * Update l2geth_ci.yml --------- Co-authored-by: Ömer Faruk Irmak <omerfirmak@gmail.com> Co-authored-by: Péter Garamvölgyi <peter@scroll.io> Co-authored-by: colin <102356659+colinlyguo@users.noreply.github.com>
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.
1. Purpose or design rationale of this PR
...
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.gobeen updated?4. Breaking change label
Does this PR have the
breaking-changelabel?