Otel execution failure on the span - #319
Conversation
detsys.execution_failure was a PostHog event. It carried detsys.exit_code, which the span already carries, and it fired at the same moment the span ended. The exec ignores the return code, thus nothing throws, thus the span stayed unset while the step failed. recordSpanError now puts the error status on the span, and Honeycomb can therefore count a failed update as a failure. We send nothing to PostHog now, so the event goes.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Essentials Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Essentials Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughThe non-zero Nix exit path now records an error on the span and passes an ChangesSpan error reporting
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to Failed Nix executions now mark their telemetry spans as errors while retaining failure logging and exit-code context. No current merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
91364a2 to
9701c1a
Compare
Description
Checklist
Summary by CodeRabbit