fix: getPDPService always returns a pdpOffering #324
+15
−56
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.
Reviewer @rvagg
See also FilOzone/filecoin-services#295
Neither of these issues were caught before because we currently catch all exceptions in SPRegistryService.getPDPService, a bad policy.
I don't remove the catch-all because there are more problems after this; for example,
'should select a random provider when no providerId specified'
will fail when trying to create the data set.Changes