Skip to content
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

Fix detailed_trace! #16452

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Fix detailed_trace! #16452

merged 1 commit into from
Nov 20, 2024

Conversation

cart
Copy link
Member

@cart cart commented Nov 20, 2024

Alternative to #16450

Objective

detailed_trace! in its current form does not work (and breaks CI)

Solution

Fix detailed_trace by checking for the feature properly, adding it to the correct crates, and removing it from the incorrect crates

@cart cart added C-Bug An unexpected or incorrect behavior A-Utils Utility functions and types labels Nov 20, 2024
@cart cart added this to the 0.15 milestone Nov 20, 2024
@mockersf
Copy link
Member

as mentioned in #16450, I think a better solution is to remove the macro and the logs that are using it

@alice-i-cecile alice-i-cecile added the S-Needs-Review Needs reviewer attention (from anyone!) to move forward label Nov 20, 2024
@cart
Copy link
Member Author

cart commented Nov 20, 2024

I responded there

Copy link
Member

@alice-i-cecile alice-i-cecile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer this as a "for-now" solution: I think that evaluating this further is warranted, but for now I'd really like to be able to merge things again.

@cart
Copy link
Member Author

cart commented Nov 20, 2024

Merging now in the interest of unblocking main. If we decide removing is the move for 0.15, we can do that later

@cart cart added this pull request to the merge queue Nov 20, 2024
Merged via the queue into bevyengine:main with commit deda3f2 Nov 20, 2024
35 of 37 checks passed
mockersf pushed a commit that referenced this pull request Nov 22, 2024
Alternative to #16450 

# Objective

detailed_trace! in its current form does not work  (and breaks CI)

## Solution

Fix detailed_trace by checking for the feature properly, adding it to
the correct crates, and removing it from the incorrect crates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Utils Utility functions and types C-Bug An unexpected or incorrect behavior S-Needs-Review Needs reviewer attention (from anyone!) to move forward
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants