Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[bot] Mistral OCR API (`client.ocr.process()`) not instrumented

未關閉
#1,748 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
58/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
冷清
技術堆疊
typescript

研究方向

先閱讀 js/src/wrappers/mistral.ts、js/src/auto-instrumentations/configs/mistral.ts、js/src/instrumentation/plugins/mistral-channels.ts、js/src/instrumentation/plugins/mistral-plugin.ts 與 js/src/vendor-sdk-types/mistral.ts 中現有的 Mistral 實作。比較現有 model methods 的模式,並檢查 e2e/scenarios/mistral-instrumentation/。當 wrapper、config、channel、plugin、vendor types 與 end-to-end instrumentation scenario 都涵蓋 client.ocr.process() 時,即表示完成。

由索引模型根據 Issue 內容生成。

描述

never-stale

Summary

The @mistralai/mistralai TypeScript SDK provides a stable client.ocr.process() method for document understanding using the Mistral OCR model. This repo has zero instrumentation for the OCR API surface — no channels, no plugin handler, no wrapper proxy, and no auto-instrumentation config. Users calling client.ocr.process() get no Braintrust spans.

What instrumentation is missing

  • Wrapper (js/src/wrappers/mistral.ts): Only proxies chat, embeddings, fim, and agents properties (lines 78–95). No proxy for ocr.
  • Auto-instrumentation config (js/src/auto-instrumentations/configs/mistral.ts): Only defines configs for chat, embeddings, FIM, and agents methods. No config for ocr.process.
  • Channels (js/src/instrumentation/plugins/mistral-channels.ts): No channel definition for OCR.
  • Plugin (js/src/instrumentation/plugins/mistral-plugin.ts): No handler for OCR calls.
  • Vendor types (js/src/vendor-sdk-types/mistral.ts): MistralClient only declares chat, fim, agents, and embeddings properties. No ocr property.

A grep for ocr (case-insensitive) across js/src/ returns zero matches.

Why this is a concrete gap

Mistral OCR is a dedicated model execution API — it sends document/image input to a model and receives generated structured text output (markdown with bounding boxes, extracted images, and page metadata). This is directly comparable to how generateContent works for Google GenAI. It uses a specific model (mistral-ocr-2503-completion) and returns token-like processing results. It is not a CRUD or management endpoint.

Braintrust docs status

not_found — The Braintrust Mistral integration page at https://www.braintrust.dev/docs/integrations/ai-providers/mistral documents chat completions only. OCR is not mentioned.

Upstream references

Precedent in this repo

This repo instruments 8 other Mistral SDK methods across 4 API categories (chat, embeddings, FIM, agents). OCR is a comparable model execution surface. Additionally, Google GenAI's generateContent (which processes multimodal input and returns structured text) is instrumented with the same depth.

Local files inspected

  • js/src/wrappers/mistral.ts
  • js/src/auto-instrumentations/configs/mistral.ts
  • js/src/instrumentation/plugins/mistral-channels.ts
  • js/src/instrumentation/plugins/mistral-plugin.ts
  • js/src/vendor-sdk-types/mistral.ts
  • e2e/scenarios/mistral-instrumentation/
主要語言
TypeScript
星號
29
分支
16
平均合併
1 天 15 小時
30 天內合併 PR
69

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

braintrustdata/braintrust-sdk-javascript 的其他 Issue

查看 braintrustdata/braintrust-sdk-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。