getsentry / getsentry/sentry-javascript
node-integration-tests: port AI and gen_ai suites to span streaming
- 主要言語
- TypeScript
- スター
- 8.7k
- フォーク
- 1.8k
- 平均マージ
- 1日 17時間
- マージ済み PR(30日)
- 523
説明
Follow the porting recipe in the parent issue.
These suites assert on deep `gen_ai` attribute sets on child spans, so the `{ value, type }` attribute shape and the collect-across-envelopes rule matter more here than anywhere else.
## Suites
* `tracing/openai`, `tracing/openai/openai-tool-calls`, `tracing/openai/v6`, `tracing/openai/v7`
* `tracing/anthropic`
* `tracing/google-genai`, `tracing/google-genai-v2`
* `tracing/vercelai`, `tracing/vercelai/v5`, `tracing/vercelai/v6_v7`
* `tracing/langchain`, `tracing/langchain/v1`
* `tracing/langgraph`
* `aws-serverless/bedrock`
## Twins to fold back
* `tracing/vercelai/span-streaming-v4` and `tracing/vercelai/span-streaming-v6` into the matching vercelai suites
* `tracing/mcp-server-streamed` has no static original, so just drop the suffix
コントリビューションガイド
調査の方向性
Start with the parent issue's porting recipe, then inspect the listed node integration suites and their span-streaming variants. Pay particular attention to deep gen_ai attributes on child spans, the { value, type } shape, and collecting attributes across envelopes. Fold the specified Vercel AI twins into their matching suites and remove the listed suffix where applicable; the suites should cover the same streaming behavior afterward.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- node.js, typescript
- 領域
- testing-qa
- issue の種類
- リファクタリング
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 54/100