Fixes #2159 -- Do not HTML-escape traces in the cache and profiling panel#2164
Merged
tim-schilling merged 1 commit intodjango-commons:mainfrom Jul 22, 2025
Merged
Conversation
Member
Author
|
It's really annoying. The tests pass both with and without the I have traced the code through the data serialization and it seems to me that the traces are properly serialized. So, I don't understand why the test doesn't show the problem... |
…nd profiling panel The panel data has to be explicitly reloaded from the store to hit this case. The new ``reload_stats`` utility helps with this.
Member
Author
|
I have found the problem. The panel data has to be forcibly reloaded from the store before rendering, otherwise the |
tim-schilling
approved these changes
Jul 22, 2025
Member
tim-schilling
left a comment
There was a problem hiding this comment.
Thank you for tracking this one down!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The panel data has to be explicitly reloaded from the store to hit this case. The new
reload_statsutility helps with this.Fixes #2159
Checklist:
docs/changes.rst.