Conversation
…o-github-actions ci: include docker image artifacts in release assets
…allbacks, and update documentation for `config.json` best practices.
…, enhancing `MessagesPrepare` to support additional content types and tool call formatting.
…l sieve and standalone parser.
… and refine tool call and OpenAI handler logic.
…ckages including SSE, Claude, Auth, Account, Config, Deepseek, Admin, and Util.
…he same chunk as a tool call.
…ken-only synthetic IDs across API, UI, and documentation.
…nd enhance tool call extraction logic.
…s, and improved OpenAI/Claude adapter handling for responses, embeddings, and tool calls.
…for OpenAI and Claude, enhance tool call streaming, and improve caller identification.
… dedicated utility functions.
…d make `wide_input_strict_output` configurable.
…n streamed responses and add a test for it.
…onses when structured tool calls are present.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d21aedac83
ℹ️ 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".
| ) | ||
|
|
||
| func (h *Handler) Embeddings(w http.ResponseWriter, r *http.Request) { | ||
| a, err := h.Auth.Determine(r) |
There was a problem hiding this comment.
Embeddings authenticates with h.Auth.Determine, which acquires from the managed account pool and can return ErrNoAccount (429) when chat traffic saturates the pool, but this handler never uses the acquired account/token afterward because embeddings are generated locally. As written, managed-key embeddings requests can be rejected under pool pressure even though no DeepSeek account is required; caller-only auth should be used here to prevent unnecessary availability loss.
Useful? React with 👍 / 👎.
| default: | ||
| s := strings.TrimSpace(fmt.Sprintf("%v", iv)) | ||
| if s != "" { | ||
| out = append(out, s) | ||
| } |
There was a problem hiding this comment.
In extractEmbeddingInputs, the []any branch stringifies scalar elements in the default case, so a token-array payload like "input": [101, 102, 103] is interpreted as three separate inputs instead of one token sequence. That returns the wrong number of embeddings and breaks compatibility for the documented token-array input shape.
Useful? React with 👍 / 👎.
1 participant
继续优化使用链路