Refactored supplier-related handlers and logic #65
Conversation
This file contains hidden or 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
- Removed unused supplier handlers and related code (e.g., `_handleOldEventSupplierSlashed`). - Consolidated supplier processing into `indexSupplier`. - Exported internal utility methods (`parseAttribute`, `getAttributes`, etc.) for broader use. - Deprecated event/message handling for suppliers now processed via `indexSupplier`. - Enhanced modularity for supplier-related functions.
… stake and adding error handling for missing data.
Alann27
force-pushed
the
feature/update-index-suppliers
branch
from
158d505 to
a0933fa
Compare
jorgecuesta
approved these changes
Nov 28, 2025
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.
Summary
Recreated index supplier logic to handle the messages and events that updates suppliers in parallel:
_handleOldEventSupplierSlashed).indexSupplier.parseAttribute,getAttributes, etc.) for broader use.indexSupplier.Issue
Our previous logic was indexing every supplier update sequentially, one by one. This caused node runners updating their suppliers' stakes (i.e., updating their services) to take an extremely long time, causing the indexer to get stuck on that block and fall out of sync.
Type of change
Select one or more:
Sanity Checklist