fix(nodebuilder/share): Pass light.Window
to shrex getter construction regardless of node type / pruning mode
#3466
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.
Since it is a network constant, shrex getter request routing should be based on the hardcoded light.Window rather than the avail window that is passed to it.
light.Window
should be used network-wide to determine which peer pool (full
orarchival
) would be most likely to serve the request.This also fixes a bug where archival nodes would not route historic EDS requests to the archival pool due to AvailabilityWindow being 0.