fix: sorting #17
Merged
fix: sorting #17
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
souhaillM
approved these changes
Sep 20, 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.
The Graph has a default limit of 100 events per query. Yesterday someone sent +100 events (since then around +1000 if queried right) within one disbursement window (2-5 minutes).
The Lightbridge until yesterday only sorted disbursements programmatically after the query, meaning the next deposit can and in fact was cut off from the query result. This resulted into the lightbridge disbursements to fail (as by design).
This fixes it by increasing the query window to the max 1,000 events per query + sorting on the query directly to avoid such issues.