You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Lookup failures can permanently suppress retries, default enrichment sends automated requests to public instances contrary to their hosting guidance, and zero-valued score filters cannot be reliably applied or cleared.
No open issues 🎉
4 previously missed issues
In code that hasn't changed since last review
Failed BiblioReads lookups are incorrectly saved as completed
internal/datasource/biblioreads/adapter.go:161
BiblioReads returns HTTP 404 for upstream fetch or JSON failures, which the client exposes as an ordinary error. If both searches fail this way, this branch logs the errors and then persists Enriched: true with no URL, suppressing future lookups until a forced reindex. Return the error instead so failed lookups remain pending rather than becoming saved non-matches.
Range-clear button ignores the active zero score filter
When the upper-bound select is set to “No score” (0) and the lower bound is blank, the range-clear button remains disabled: hasValue explicitly treats "0" as empty. This is now an active filter, not an unset numeric input. Treat nonempty select values as active so users can clear the unrated-only filter with this button.
Home search drops the zero-valued review score upper bound
Selecting “No score” as the upper bound in the home-page search does not apply this filter. home-search.js's collectPanelParams discards values equal to "0", so review-score-to is omitted and the server defaults it to 5; with no other criteria, submission does nothing. Update that serializer to preserve the zero-valued review-score bound.
Default public endpoints send automated requests without permission
main.go:109
The linked BiblioReads README asks direct API and automation users to host their own instance. Enabling reviews by default with public-instance fallback instead sends library-wide automated requests to those services when documents need enrichment. Require explicitly configured self-hosted endpoints, or endpoints whose operators permit automation, and update the defaults and documentation accordingly.
The reason will be displayed to describe this comment to others. Learn more.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
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.
No description provided.