-
Notifications
You must be signed in to change notification settings - Fork 6
fully exhaust query map #144
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.
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
Merged
thewhaleking
merged 4 commits into
staging
from
feat/thewhaleking/fully-exhaust-query-map
Jun 30, 2025
+114
−21
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if one of the
self.rpc_request
s raises an error? For example, due to a short, temporary bad connection? Or a broken data structure?You don't want to use
return_exceptions=True
for the gather and then filter the result? or use try except with logging in case of error?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I'd rather not. The problem with returning exceptions is that we would have one of three options at that point:
By not returning the exception, we're implicitly choosing option 2. Option 1 would be fine if we trusted people to correctly examine logs before moving on. However, in the case where most of this will not be watched before being used, we cannot rely on someone to say "okay, this is incomplete data, what now must I do with it?", and also the fact that this only occurs when using
fully_exhaust=True
, which is stated to only be used if you want all (read: not partial) data. Therefore, I think this is the best option.Option 3 doesn't make sense, because those calls are already retried if the exception is due to a websocket timeout, and if not can be caught be something else (such as with
RetryAsyncSubstrate
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In other words, we only consider the case where ALL results are successful or we get an error. Right?