Skip to content

Development#5

Closed
MitulShah1 wants to merge 3 commits into
mainfrom
development
Closed

Development#5
MitulShah1 wants to merge 3 commits into
mainfrom
development

Conversation

@MitulShah1

Copy link
Copy Markdown
Contributor

No description provided.

@MitulShah1 MitulShah1 closed this May 28, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 550a85dac5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread ferrolabsai/client.py
Comment on lines +360 to +361
if trace_id and "trace_id" not in data and "x_ferro_trace_id" not in data:
data["trace_id"] = trace_id

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Guard metadata injection for non-dict responses

When an endpoint returns a bare JSON array and the gateway includes x-request-id, this assignment treats the list as a dict and raises TypeError before callers can handle it. The SDK already supports list-shaped responses in places like Admin.keys.list() (data if isinstance(data, list) ...), so /admin/keys or similar list endpoints that include the standard request-id header will regress; parse the JSON as Any and only inject header metadata into dict bodies.

Useful? React with 👍 / 👎.

"""Legacy completion-style adapter — wraps chat completions with a single user message."""

model: str = Field(...)
base_url: str | None = None

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Raise Python requirement or remove 3.10 syntax

The integration still advertises requires-python = ">=3.9", but the new modules use PEP 604 annotations such as str | None, which Python 3.9 cannot parse even with from __future__ import annotations. Users on the advertised Python 3.9 will get a SyntaxError on import; either require Python >=3.10 for this package or rewrite these annotations with Optional[...]/Union[...].

Useful? React with 👍 / 👎.

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