Skip to content

fix(provider): classify stdout provider failures#99

Open
rohitjavvadi wants to merge 1 commit into
openclaw:mainfrom
rohitjavvadi:fix/provider-output-exit-codes
Open

fix(provider): classify stdout provider failures#99
rohitjavvadi wants to merge 1 commit into
openclaw:mainfrom
rohitjavvadi:fix/provider-output-exit-codes

Conversation

@rohitjavvadi
Copy link
Copy Markdown
Contributor

Summary

Provider subprocess failures can put their actionable error text on stdout instead of stderr. The failure message already used stderr-or-stdout, but the exit-code classifier only looked at stderr, so stdout-only auth, API-key, scope, quota, or rate-limit failures were reported as generic provider failures.

This updates the classifier to inspect both streams, keeps the existing single-message path compatible, and narrows the matching so benign generated text such as author, oauth, authority, or rate-limit policy discussion does not get treated as a provider failure category.

Verification

  • ./node_modules/.bin/vitest run src/provider.test.ts
  • ./node_modules/.bin/vitest run
  • ./node_modules/.bin/tsc -p tsconfig.json --noEmit
  • ./node_modules/.bin/oxlint . --config oxlint.json
  • ./node_modules/.bin/oxfmt --check src/provider.ts src/provider.test.ts
  • git diff --check
  • ./node_modules/.bin/tsc -p tsconfig.build.json

@rohitjavvadi rohitjavvadi requested a review from a team as a code owner May 20, 2026 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant