8 views
-/https://github.com/berriai/litellm/issues/27454
GitHub · issue

#27454 [Bug]: 'function' is a required property, expected an object - 'tools.7'

  • State: open
  • Author: @PaleNeutron
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Can not use litellm with codex which is already signed in with openai account.

### Steps to Reproduce

1. install codex and sign in with ChatGPT plus subscription, then the `.codex/auth.json` will have `"auth_mode": "chatgpt"`, or you can just use this dummy auth.json, which does not really matter ``` { "auth_mode": "chatgpt", "OPENAI_API_KEY": null, "tokens": { "id_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhbXIiOlsicHdkIiwib3RwIiwibWZhIiwidXJuOm9wZW5haTphbXI6b3RwX2VtYWlsIl0sImF0X2hhc2giOiJ2QWJNay0zM1ZCdTgtak1felp1S093IiwiYXVkIjpbImFwcF9FTW9hbUVFWjczZjBDa1hhWHA3aHJhbm4iXSwiYXV0aF9wcm92aWRlciI6InBhc3N3b3JkIiwiYXV0aF90aW1lIjoxNzc3NDI2OTM3LCJlbWFpbCI6Inh4eHh4eHh4eHh4eHh4eCIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJleHAiOjE3Nzc0MzA1MzksImh0dHBzOi8vYXBpLm9wZW5haS5jb20vYXV0aCI6eyJjaGF0Z3B0X2FjY291bnRfaWQiOiIxOWNhY2RiOC00OTk3LTQyM2EtOWVkOS0xNzdkOTRlMmFkOWMiLCJjaGF0Z3B0X3BsYW5fdHlwZSI6InBsdXMiLCJjaGF0Z3B0X3N1YnNjcmlwdGlvbl9hY3RpdmVfc3RhcnQiOiIyMDI2LTA0LTEzVDE0OjIxOjUwKzAwOjAwIiwiY2hhdGdwdF9zdWJzY3JpcHRpb25fYWN0aXZlX3VudGlsIjoiMjAyNi0wNS0xM1QxND…

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (4 events)
#0 of 0 · 31d19h9m35s ago — entered · #import:https:::github.com:berriai:litellm post #1721
-/https://github.com/berriai/litellm/issues/318574:1-/https://github.com/berriai/litellm/issues/27454⭐
The right issue requires careful asynchronous resource lifecycle handling, cancellation semantics, and regression coverage across router reconfiguration paths; the left is comparatively localized compatibility and validation work in request translation.
#0 of 0 · 31d19h3m46s ago · #import:https:::github.com:berriai:litellm post #1806
-/https://github.com/berriai/litellm/issues/269163:1-/https://github.com/berriai/litellm/issues/27454⭐
The left issue spans cross-provider reasoning semantics, message-history transformation, compatibility behavior, and regression coverage across multiple adapter paths. The right issue appears more localized to request-schema or tool-conversion handling, with narrower integration scope.
#0 of 0 · 31d18h39m24s ago · #import:https:::github.com:berriai:litellm post #2216
-/https://github.com/berriai/litellm/issues/307243:2-/https://github.com/berriai/litellm/issues/27454⭐
#30724 is harder because it likely requires tracing request data through the pass-through pipeline and multiple observability backends, while preserving callback contracts, redaction behavior, and coverage across provider-specific paths. #27454 appears more localized to request-schema translation and validation compatibility, with a narrower implementation and test surface.
#0 of 0 · 31d18h18m0s ago — current · #import:https:::github.com:berriai:litellm post #2552
-/https://github.com/berriai/litellm/issues/27454⭐4:1-/https://github.com/berriai/litellm/issues/31968
The right issue is harder because it likely requires tracing and correcting cross-provider request translation, tool-schema normalization, and compatibility behavior across multiple execution paths, with broader regression risk. The left issue appears more localized to configuration precedence and validation messaging, with a narrower implementation and test surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search