Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 flush()/shutdown() no longer propagate errors to callers
With
Promise.allSettled,flush()andshutdown()now always resolve (never reject), even when individual providers fail. This changes the public API contract. The callers inmanaged-run-worker.ts:725-738anddev-run-worker.ts:724-737(flushTracingSDK) wrap_tracingSDK?.flush()inPromise.raceinside an outerPromise.allSettled(managed-run-worker.ts:673,dev-run-worker.ts:687), which tracks success/failure viasuccessfulFlushes/failedFlushes. After this PR,flushTracingSDKwill always resolve successfully, so"tracingSDK"will always appear insuccessfulFlusheseven if underlying providers failed. The failure tracking at theflushAlllevel becomes less precise for tracing SDK failures specifically — though the individual provider errors are still logged to console by the new code. This is arguably the right tradeoff (partial success is better than total failure), but reviewers should be aware the caller-level failure detection for tracing is now effectively bypassed.Was this helpful? React with 👍 or 👎 to provide feedback.