-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(observability): demote reliable_chat all_exhausted aggregate as ProviderConfigRejection (Sentry TAURI-RUST-4JS) #2797
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
Merged
senamakel
merged 2 commits into
tinyhumansai:main
from
CodeGhost21:fix/observability-reliable-aggregate-user-config
May 29, 2026
+107
−11
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Merge-conflict resolution + reviewer follow-up (PR-finisher)
This branch conflicted with
mainhere becausemainindependently landed the TAURI-RUST-1V sibling fix, which added"may not be available on your provider"(plus a TAURI-RUST-35"does not support tools"block) to this same PHRASES list — at the exact append site this PR targets.Resolved as the union of both sides: kept this PR's OPENHUMAN-TAURI-4JS
"reliability.model_fallbacks"anchor and main's"may not be available on your provider". Both phrases co-occur only informat_failure_aggregate's no-configured-fallbacks branch, so they're mutually consistent (redundant belt-and-braces,.any()short-circuits) and neither fires on the configured-fallbacks branch — the negative testdoes_not_classify_reliable_aggregate_with_configured_fallbacksstill pins that boundary and passes. Merged the two comment blocks into one and documented the redundancy.Re: your merge-order question about #2786 — moot now.
mainalready carries the body-level siblings, and the classifier short-circuits on first match, so there is no double-counting regardless of which landed first.Re: your nit (emit-site vs body-pattern anchor separator) — the merged comment block now groups both emit-site anchors together and calls out that they're config-path/sentence anchors rather than upstream body patterns, which covers the spirit of the suggestion without a hard separator.
All 14
config_rejectiontests pass;cargo fmt, tauricargo check, and the full pre-push suite are green.