This repository has been archived by the owner on Dec 20, 2023. It is now read-only.
Fixes a bug for which FEVM events weren't being stored #195
Conversation
This file contains 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
adlrocha
changed the title
dnkolegov
approved these changes
Jun 28, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Several users (including ourselves) where experiencing weird behaviors when interacting with FEVM contracts that returned a variable and/or emitted an event. For some reason, the clients were getting stuck while waiting for the transaction receipt.
The reason was that we weren't storing successfully in the ChainStore the events from FEVM contracts, so the client froze waiting for some new event related to the receipt to appear in the state. This PR fixes the problem.