Commit bf6cd22
committed
fix: revert span limit check from user-facing DDTrace\start_span APIs
DDTrace\start_span() and DDTrace\start_trace_span() are user-facing
APIs that intentionally bypass the span limit — the limit applies to
auto-instrumentation (hooks) only. Guarding these APIs with
ddtrace_tracer_is_limited() broke:
- testTracerFlushedWhenSpanLimitExceeded: the test explicitly verifies
that user-created spans work even when DD_TRACE_SPANS_LIMIT is hit.
- Guzzle integration tests: isolateTracer() uses start_trace_span()
internally to create isolated trace contexts; when closed_spans_count
accumulated past the limit across PHPUnit tests, no new stack was
created and all spans in the isolated test were lost.
The curl multi code paths in handlers_curl.c and handlers_curl_php7.c
remain fixed (the actual OOM culprit reported in APMS-18744).1 parent e2a7782 commit bf6cd22
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3214 | 3214 | | |
3215 | 3215 | | |
3216 | 3216 | | |
3217 | | - | |
| 3217 | + | |
3218 | 3218 | | |
3219 | 3219 | | |
3220 | 3220 | | |
| |||
3224 | 3224 | | |
3225 | 3225 | | |
3226 | 3226 | | |
3227 | | - | |
| 3227 | + | |
3228 | 3228 | | |
3229 | 3229 | | |
3230 | 3230 | | |
| |||
3238 | 3238 | | |
3239 | 3239 | | |
3240 | 3240 | | |
3241 | | - | |
| 3241 | + | |
3242 | 3242 | | |
3243 | 3243 | | |
3244 | 3244 | | |
| |||
0 commit comments