Skip to content

fix: fix trace id in logs when using set_parent nested in a trace span #365

fix: fix trace id in logs when using set_parent nested in a trace span

fix: fix trace id in logs when using set_parent nested in a trace span #365

Triggered via pull request April 10, 2025 06:19
Status Skipped
Total duration 3s
Artifacts

benchmark.yml

on: pull_request
run benchmark
0s
run benchmark
Fit to window
Zoom out
Zoom in