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.

Sign up for GitHub

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

Jump to bottom

Events ingested from Cadence can be out of order #197

Closed
Tracked by #126
devbugging opened this issue Apr 9, 2024 · 0 comments · Fixed by #198
Closed
Tracked by #126

Events ingested from Cadence can be out of order #197

devbugging opened this issue Apr 9, 2024 · 0 comments · Fixed by #198
Assignees
@devbugging
Labels
Feedback

Comments

@devbugging
Copy link
Contributor

It was assumed events ingested from Cadence will be in order (first block event, then transaction) but that is not the case as found in testing. We should sort the events to keep them in that order.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devbugging devbugging

Labels
Feedback
Projects
🌊 Flow 4D
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Event ingestion refactor onflow/flow-evm-gateway
1 participant
@devbugging