Skip to content

fix: Detect and handle watsonx.ai model provider rate limit exceptions #73

fix: Detect and handle watsonx.ai model provider rate limit exceptions

fix: Detect and handle watsonx.ai model provider rate limit exceptions #73

Triggered via pull request May 14, 2026 02:16
Status Cancelled
Total duration 31s
Artifacts

lint-backend.yml

on: pull_request
Ruff and mypy on changed files
14s
Ruff and mypy on changed files
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
ruff (B904): src/api/provider_validation.py#L594
src/api/provider_validation.py:594:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L522
src/api/provider_validation.py:522:17: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L513
src/api/provider_validation.py:513:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L421
src/api/provider_validation.py:421:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L378
src/api/provider_validation.py:378:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L338
src/api/provider_validation.py:338:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (B904): src/api/provider_validation.py#L267
src/api/provider_validation.py:267:9: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
ruff (I001): src/api/provider_validation.py#L3
src/api/provider_validation.py:3:1: I001 Import block is un-sorted or un-formatted help: Organize imports
ruff (UP045): src/api/provider_health.py#L19
src/api/provider_health.py:19:15: UP045 Use `X | None` for type annotations help: Convert to `X | None`
ruff (I001): src/api/provider_health.py#L3
src/api/provider_health.py:3:1: I001 Import block is un-sorted or un-formatted help: Organize imports
Lint Backend
The run was canceled by @autofix-ci[bot].
Ruff and mypy on changed files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Ruff and mypy on changed files
Failed to restore: Cache service responded with 400