fix: add explicit stacklevel to all warnings.warn() calls#1041
Open
decembercomposer697-hue wants to merge 2 commits into
Open
fix: add explicit stacklevel to all warnings.warn() calls#1041decembercomposer697-hue wants to merge 2 commits into
decembercomposer697-hue wants to merge 2 commits into
Conversation
added 2 commits
June 18, 2026 23:00
When extra media content is a file path (not base64), it was previously used as-is in the HTML, creating absolute paths that break when the report is moved. Now resolves relative to the report's parent directory.
B028: 7 warnings.warn() calls lacked explicit stacklevel, making deprecation warnings point to the warning call site instead of the caller's code.
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
1 participant
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.
7 B028 fixes: all warnings.warn() calls now have explicit stacklevel=2.
✅ 7 unit tests pass