Repository navigation
fix(aimlapi): stop issue floods and remove sunset models - #9733
Merged
Merged
Conversation
Contributor
|
No actionable findings. |
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
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.
Summary
Corrects the issue flood introduced by #9531. The runner includes every skipped remote ID in the missing-model issue batch when
skipCreates: true, independently of the provider'smissingModelIDfilter. The earlier tests checked the provider callback but not actual issue admission through the runner.trackMissingModels: false) until its backlog is audited. Existing updates/removals continue; omitted models are report-only. Other providers are unaffected.syncProviderrunner withopenIssues: true, covering both untranslated IDs and translated new cards blocked byskipCreates. Neither is admitted to issues.gpt-5.1-codex,gpt-5.1-codex-mini, andgpt-5.2-codex: the host feed lists their shutdown date as 2026-07-23, despite retaining catalog/docs entries.Cleanup already performed
Closed 114 AI/ML API missing-model issues and 75 automatically generated follow-up PRs from the batch. No unrelated provider issues or PRs were closed. Checked that none remained open and no issue-fixer jobs were active at inspection.
Checks
bun validatepasses.bun test test/aimlapi.test.tsfrompackages/core: 20 pass.bun models:sync aimlapi --dry-run --open-issues: zero issue admissions, zero creates/updates, and exactly the three sunset removals now included in this PR.Public catalog presence and a docs endpoint returning 200 do not establish inference availability. This PR uses the host's explicit lifecycle records rather than guessing retirement from model age.