Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ignore STOP debug frame #202

Merged
merged 5 commits into from
Sep 28, 2023
Merged

ignore STOP debug frame #202

merged 5 commits into from
Sep 28, 2023

Conversation

tmcgroul
Copy link
Contributor

No description provided.

@@ -398,6 +398,9 @@ function* mapDebugFrame(transactionIndex: number, debugFrameResult: rpc.DebugFra
}
}
break
case 'STOP':
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we have a possibility of

  • gaps in trace indexes/addresses
  • children with no parent

if STOP will turn out to be not the last frame in transaction or to have children.

Thus, it is better to ignore it on traversal.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my assumption was that if STOP frame is presented then it's a single frame without parents/children.
i checked several STOP frames from three networks (base, optimism, zora) and all the time it was a single frame

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i checked several STOP frames from three networks (base, optimism, zora) and all the time it was a single frame

Then, you have to make the assumption explicit by asserting it!

@eldargab eldargab merged commit d7767c7 into master Sep 28, 2023
1 check passed
@eldargab eldargab deleted the stop-trace branch September 28, 2023 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants