Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(telemetry): reject non-positive maxExportBatchSize at plugin load

Browse Source 
Review finding, pinned red-first: the SDK accepts
processor.maxExportBatchSize <= 0 (or fractional), but its shutdown
drain then splices empty batches without consuming the queue —
disposing telemetry hangs forever whenever records are queued. The
constructor now rejects a non-positive-integer batch size before
building the SDK processor, per the misconfiguration-fails-loud rule;
everything else in the processor block remains the SDK's verbatim
passthrough.
This commit is contained in:
kingwl
2026-07-27 20:11:30 +08:00
parent a72436105b
commit bf76c52d76
5 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
packages/telemetry/session-telemetry-otel/README.i18n.yaml
View File

@@ -2,5 +2,5 @@
# side as of the last confirmed-consistent state. Both languages carry equal authority;
# after editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write
README.md: 6ead0ec7b7053551676b482dd4c905c8cd7cc1fe
README.zh.md: 852242bfc4ac719660f31935167d2f4fa0f58f2e
README.md: e345449033b066103fb14e546e8d9909d68fe696
README.zh.md: 6cad58ebc1ad9bab6dc722fcf0d702f500891d32