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

[bot] OpenAI Decisions API (`client.decisions.create()`) not instrumented

Geschlossen
  • Stimmt etwas nicht?
#2,618 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
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
nodejs, typescript
Bereich
ai, backend

Rechercherichtung

Start with js/src/auto-instrumentations/configs/openai.ts, which shows how the existing Responses and Embeddings resources are instrumented, then check js/src/wrappers/oai.ts for the manual proxy. Add a Decisions entry and a plugin channel under js/src/instrumentation/plugins/, and raise the openai devDependency in js/package.json to at least 7.30.0. Done means client.decisions.create() emits a span in a recorded test.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

OpenAI's Node SDK added a standalone Decisions API (client.decisions.create(), endpoint POST /v1/decisions) in [email protected] (changelog: "add standalone Decisions support"). It runs the dedicated gpt-6-luna model (added in [email protected], "add GPT-6 Sol and Luna model identifiers") to turn text/image input into typed, structured answers — a generative model-execution call distinct from Chat Completions/Responses, not a CRUD or admin endpoint. Development is active and ongoing: the latest openai release (7.33.0, 2026-10-14) adds "organization Decisions usage reporting" and documentation clarifications for decision creation. This repo has zero instrumentation for this surface — no config entry, no channel, no wrapper — so calls to client.decisions.create() produce no Braintrust spans at all.

What instrumentation is missing

  • client.decisions.create({ model: "gpt-6-luna", input, decision }) — POST /v1/decisions. Accepts text/image input plus a typed decision schema (choices/score/boolean-style questions) and returns a structured, typed answer instead of free-form prose.

No coverage in any instrumentation layer:

  • js/src/auto-instrumentations/configs/openai.ts — instruments Images.*, Audio.* (speech/transcriptions/translations), Chat.Completions.create/parse/stream, Embeddings.create, Moderations.create, and Responses.create/stream/parse/compact. No entry for a Decisions resource.
  • js/src/instrumentation/plugins/ — no openai-decisions-style channel or plugin file.
  • js/src/wrappers/oai.ts — manual wrapper proxies the resources above only; no decisions property handling.

A case-insensitive repo-wide search for decisions under js/src/ returns no genuine matches (the only two hits are an unrelated test description string and an unrelated code comment, neither referencing this API).

Braintrust docs status

not_found — https://www.braintrust.dev/docs/integrations/ai-providers/openai lists the OpenAI methods Braintrust auto-traces for TypeScript (chat completions, embeddings, moderation, Responses API, batch API, Agents API, images, audio) and does not mention a Decisions API, decisions.create, or gpt-6-luna anywhere.

Upstream references

Local files inspected

  • js/src/auto-instrumentations/configs/openai.ts — full file read; no Decisions entry
  • js/src/wrappers/oai.ts — no decisions proxy handling
  • Repo-wide case-insensitive grep for decisions under js/src/ — no relevant matches
  • js/package.json — openai devDependency pinned at 6.25.0 (below the >=7.30.0 floor needed for this surface), confirming it is a genuinely new capability relative to this repo's current test/record setup rather than something already exercised
Vorherrschende Sprache
TypeScript
Sterne
29
Forks
16
Ø Merge
1 T. 20 Std.
Gemergte PRs (30 T.)
70

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.