Use correct DSN protocols in gateway #3221
Merged
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.
In a recent refactor, I used the wrong gateway node config. The protocol version is missing a
/subspace/2/
prefix, and the piece fetching protocols weren't enabled.As part of this change, I also added a fallback from the farmer cache (L2) to archival storage (L1).
In the current implementation, all the DSN connections fail:
After these fixes, it works:
Code contributor checklist: