Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[bot] Mistral Batch API (`client.batch.jobs`) is not instrumented

Offen
  • Stimmt etwas nicht?
#2,685 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, typescript
Bereich
observability, tooling

Rechercherichtung

Start by reading js/src/instrumentation/plugins/mistral-interceptors.ts to see how existing Mistral channels are declared, then mistral-plugin.ts to see how they are subscribed. Compare js/src/wrappers/mistral.ts and js/src/vendor-sdk-types/mistral.ts to understand how the batch namespace is currently unwrapped and typed. Done means client.batch.jobs.create/get/list and result download produce spans consistent with the existing chat and embeddings instrumentation, with tests covering the batch lifecycle.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

typescript

Summary

Mistral's official TypeScript SDK exposes a documented Batch API (client.batch.jobs.create()/.get()/.list(), plus client.files.download() for results) for submitting large-scale async chat, embeddings, FIM, moderation, classification, OCR, and conversation jobs. This repo instruments every one of Mistral's synchronous execution surfaces but has zero coverage of the batch lifecycle — no channel, no plugin logic, no vendor type.

What's missing

  • js/src/instrumentation/plugins/mistral-plugin.ts — MistralPlugin.onEnable()/subscribeToMistralChannels() (lines 24-277) subscribes to exactly ten channels: chatComplete, chatStream, embeddingsCreate, classifiersModerate, classifiersModerateChat, classifiersClassify, classifiersClassifyChat, fimComplete, fimStream, agentsComplete, agentsStream. There is no batch-related channel anywhere in the file.
  • js/src/instrumentation/plugins/mistral-interceptors.ts — grepped for batch/Batch (case-insensitive): zero matches. No mistralChannels.batch* exists for the plugin to subscribe to in the first place.
  • js/src/vendor-sdk-types/mistral.ts — MistralClient (lines 222-229) is typed as { chat?, fim?, agents?, embeddings?, classifiers?, [key: string]: unknown }. There is no batch namespace type at all (no MistralBatch, MistralBatchJob, etc.), so even an untyped passthrough isn't modeled.
  • js/src/wrappers/mistral.ts — wrapMistral()/mistralProxy() (lines 85-108) proxies only chat, fim, agents, embeddings, classifiers. A client's batch property is returned as-is via the proxy's default branch (Reflect.get, line 104) — fully unwrapped, so client.batch.jobs.create(...) produces no span of any kind: no submission span, no status/polling span, no per-request result spans.

This means a customer submitting client.batch.jobs.create({ endpoint: "/v1/chat/completions", inputFiles: [...] }) — a fully supported, documented Mistral API call — gets no trace in Braintrust whatsoever, while the same customer's synchronous chat.complete/embeddings.create calls are fully traced with input, output, and token metrics.

Braintrust docs status

not_found. https://www.braintrust.dev/docs/providers/mistral documents only synchronous spans: "Chat completion spans (mistral.chat.complete...)", "Embedding spans (mistral.embeddings.create)", "Fill-in-the-middle completion spans", "Audio transcription spans." The page's "All call types support sync and async variants" line refers to Python's asyncio client variants, not batch jobs. No batch/async-job tracing is mentioned anywhere on the page.

Upstream sources

  • https://docs.mistral.ai/capabilities/batch/ — Batch API guide: client.batch.jobs.create() accepts input_files (file-based, up to 1,000,000 requests) or inline requests (up to 10,000); supports endpoint values /v1/embeddings, /v1/chat/completions, /v1/fim/completions, /v1/moderations, /v1/chat/moderations, /v1/ocr, /v1/classifications, /v1/conversations, /v1/audio/transcriptions; status via client.batch.jobs.get()/.list(); results retrieved via client.files.download().

Braintrust docs sources checked

Local repo files inspected

  • js/src/instrumentation/plugins/mistral-plugin.ts — subscribeToMistralChannels() (lines 24-277), full enumerated channel list
  • js/src/instrumentation/plugins/mistral-interceptors.ts — grepped for batch/Batch, zero matches
  • js/src/vendor-sdk-types/mistral.ts — MistralClient type (lines 222-229)
  • js/src/wrappers/mistral.ts — mistralProxy() (lines 85-108), proxy coverage limited to chat/fim/agents/embeddings/classifiers
Vorherrschende Sprache
TypeScript
Sterne
29
Forks
21
Ø Merge
1 T. 15 Std.
Gemergte PRs (30 T.)
76

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus braintrustdata/braintrust-sdk-javascript

Alle Issues in braintrustdata/braintrust-sdk-javascript

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.