fix: handle potential concurrent system contracts insertion #378
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
1 task
API E2E Test Results207 tests 207 ✅ 19s ⏱️ Results for commit 6885e91. ♻️ This comment has been updated with latest results. |
Unit Test Results 4 files 264 suites 12m 20s ⏱️ Results for commit 6885e91. ♻️ This comment has been updated with latest results. |
|
Visit the preview URL for this PR: |
vasyl-ivanchuk
approved these changes
Jan 22, 2025
|
🎉 This PR is included in version 2.60.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
If indexer finds a contract deployment event for a system contract at the same time as system contracts service inserts it - there will be a collision. It can very likely happen especially after these events are added on the blockchain side for initial deployments of system contracts.