fix: retry AI tagging without logprobs when the provider rejects it - #148
Merged
Conversation
Fixes #143: Gemini (both its OpenAI-compat endpoint and its native API via a proxy) returns 400 for the logprobs/top_logprobs params the tags call always sent, so the tags request failed every retry while the separate, logprobs-free description call succeeded - silently leaving items with a description but no tags and no visible error. On a 400 whose body mentions "logprobs", retry the same attempt with it disabled instead of consuming the retry budget; the logprobs-based confidence score is simply skipped for that endpoint.
Anyesh
force-pushed
the
fix/issue-143-gemini-logprobs
branch
from
July 25, 2026 06:28
f9b5731 to
b39815d
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #143: Gemini (both its OpenAI-compat endpoint and its native API via a proxy) returns 400 for the logprobs/top_logprobs params the tags call always sent, so the tags request failed every retry while the separate, logprobs-free description call succeeded - silently leaving items with a description but no tags and no visible error.
On a 400 whose body mentions "logprobs", retry the same attempt with it disabled instead of consuming the retry budget; the logprobs-based confidence score is simply skipped for that endpoint.
Description
Related Issue
Type of Change
Checklist
Testing
Test Environment
Tests Performed
Screenshots (if applicable)
Additional Notes