8000 More validations for tracer output converting logic by aidan-kwon · Pull Request #1549 · klaytn/klaytn · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Aug 19, 2024. It is now read-only.

More validations for tracer output converting logic #1549

Merged
merged 5 commits into from
Jul 22, 2022

Conversation

aidan-kwon
Copy link
Member

Proposed changes

InternalTxTracer.result is only called by fastCallTracer now.
(fastCallTracer can be used for debug APIs or chaindatafetcher)

The tracer result parses an error string when a transaction is reverted.
Since current logic doesn't have enough validation logic about slice range or overflow/underflow, the tracer can be panic when an abnormal contract executed.

This change introduces only small parts of validation for recent invalid cases.
After v1.9.0 QA, more concrete validation will be introduced later.

Types of changes

Please put an x in the boxes related to your change.

  • Bugfix
  • New feature or enhancement
  • Others

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING GUIDELINES doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes ($ make test)
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

@aidan-kwon aidan-kwon self-assigned this Jul 22, 2022
@aidan-kwon aidan-kwon added the need to merge Need to merge for the next time label Jul 22, 2022
@jeongkyun-oh
Copy link
Contributor

How about callTracer? Should we align callTracer.js with this change?

Co-authored-by: jk-jeongkyun <45347815+jeongkyun-oh@users.noreply.github.com>
@aidan-kwon
Copy link
Member Author
aidan-kwon commented Jul 22, 2022

How about callTracer? Should we align callTracer.js with this change?

@jeongkyun-oh We should. But, not for this time. Since we are about to release v1.9.0, I don't want to put large changes. This is a kind of hot fixes for recent issues. We need to investigate more about tracers for v1.9.1.

Co-authored-by: Junghyun Colin Kim <colin.klaytn@krustuniverse.com>
@aidan-kwon aidan-kwon merged commit 64b43a6 into klaytn:dev Jul 22, 2022
@aidan-kwon aidan-kwon deleted the 220722-tracerFix branch July 22, 2022 08:58
aidan-kwon pushed a commit to aidan-kwon/klaytn that referenced this pull request Aug 1, 2022
More validations for tracer output converting logic
@blukat29 blukat29 removed the need to merge Need to merge for the next time label Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0