-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(provider-index): parallelize claim lookups #121
Conversation
Codecov ReportAttention: Patch coverage is
|
- ProviderIndexService.getProviderResults now queries IPNI and legacy claims concurrently using channels. If IPNI returns a valid result, the legacy lookup is canceled, reducing unnecessary wait times. - errors from both queries are joined to provide better context when neither returns data. - tests have been updated to cover these new scenarios.
- changes permit: - runtime of cache lookup to be inferred. - runtimes of ipni & legacy fetch operations to be inferred.
494404f
to
ae21e44
Compare
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.
LGTM
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.
LGTM. It may be valuable to add a couple more tests for the cases where IPNI and/or legacy return no results and no errors.
@volmedo great idea 😄
|
via 656fa67
via ae21e44