Skip to content

Avoid printing exception stack traces for errors coming from the upstream #340

@adubovik

Description

@adubovik

Stack traces should be reserved for unexpected exceptions within the adapter itself, whereas any status code from the upstream is expected (including 429, 503, etc.).

Otherwise, fairly mundane upstream errors like 429/400 flood the console logs with identical stack traces originating from the openai SDK.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions