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
{{ message }}
Repository navigation
Commit 6088f40
Browse filesBrowse the repository at this point in the historyBrowse files
fix(api): forward discovery cancellation into the Kimi catalog fetch
CodeRabbit pre-merge checks (Linked Issues error + Regression
Evidence warning):
- KimiCodeHandler.fetchModels now forwards cancellation (explicit
model-cache signal, else the caller signal carried on
options.signal) to getKimiCodeModels, so a cancellation during
handler-driven discovery aborts the in-flight discovery HTTP
request instead of only stopping the caller's wait (Issue #404).
Pinned by two new handler tests plus the model-catalog-adapters
case flipped to forwardsSignal.
- The discovery-retry test now asserts getModels receives the
caller signal (previously only call counts were checked).
- base-openai-compatible-provider and zai: added rejected-Promise
request-creation cases (mockRejectedValueOnce(new
APIUserAbortError())) - the awaited create() rejects with that
shape in practice, and the sync-throw-only tests passed even with
the await removed. Negative controls: reverting the signal
forwarding, dropping the signal from prepareRequest, and removing
each await each fail exactly one test.
The Lifecycle Resource Cleanup warning's OAuth-refresh half
(resolveAccessToken -> postForm threading) lives in
src/integrations/kimi-code/oauth.ts, outside this unit's diff;
registered in the PR body as a follow-up.
0 commit comments