Repository navigation
fix(core): report generate body timeouts correctly (carries #165) - #187
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Memory benchmarkCompared base
Interpretation: No metric shows a clear Base-to-PR difference beyond its measured run-to-run variation. Extension overhead above pi baseline
Values are medians of 6 alternating, paired runs. The value after Environment: pi
|
|
CI status at head The public Provider API currently advertises 96 models, including this new model. This PR changes neither |
d991056 to
54ab00f
Compare
|
Pricing blocker resolved: #188 has landed on main as |
54ab00f to
baa552e
Compare
Carries the stalled-response-body timeout fix from #165 by @patlux (
cef7402f9f382e9b30252d29178efaf49392cc75). This is independent of the OAuth carry in #186 and the remaining fix groups in #165; it does not close #165.Changes
The source and regression-test changes are identical to patlux's original commit. Only the CHANGELOG entry is adapted to current main, with explicit credit and scope. The commit includes a co-author trailer.
Scope
This fixes the extension-owned generate transport only. It does not change native Provider API retries, add mid-stream transport switching, or implement the breaking removal of generate proposed in #164.
Validation
Based on main
999b690:npm test: PASS, including project typecheck and real Pi/OMP against loopback mocks.npm run format:checkandgit diff --check: PASS.No paid API calls or production credentials used. The editor LSP reported unresolved Node types in the temporary worktree; the project TypeScript compiler completed successfully with the existing dependencies.