-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - Fix bevy_ecs::schedule::executor_parallel::system span management #2905
Conversation
Or at least bevy_ecs::schedule::executor_parallel::system Fixes bevyengine#2904
This has the concrete benefit that you can now write a log filter |
Would this be fixed by #2423 , or is it another span that didn't have its parent? If they are the same fix, yours is much simpler 👍 |
@mockersf these do seem to be the same issue! And yeah, I was glad to see that I could grab the TLS context so easily rather than having to thread the context through manually behind the cfg. |
bors r+ |
) # Objective - Fixes #2904 (see for context) ## Solution - Simply hoist span creation out of the threaded task - Confirmed to solve the issue locally Now all events have the full span parent tree up through `bevy_ecs::schedule::stage` all the way to `bevy_app::app::bevy_app` (and its parents in bevy-consumer code, if any).
Objective
Solution
Now all events have the full span parent tree up through
bevy_ecs::schedule::stage
all the way tobevy_app::app::bevy_app
(and its parents in bevy-consumer code, if any).