fix: tighten logspark floor to >=0.10.2#147
Merged
Merged
Conversation
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.
Problem
LogSpark
0.10.2(released 2026-06-10) fixes stacklevel derivation from the logger class MRO. Without it, log lines emitted throughWrenchLogger(which inheritsSparkLogger) can report the wrong file/function/line — showing WrenchCL internals instead of the actual calling code.WrenchCL was pinned at
logspark>=0.10.1, which technically allows0.10.2, but Docker layer caching means services built before the release will stay on0.10.1until forced. This PR raises the floor to>=0.10.2so the next WrenchCL version enforces the fix.Change
pyproject.toml:logspark>=0.10.1→logspark>=0.10.2End-user impact
Log lines across all 9 pipeline services will correctly report the application code location (file, function, line) rather than WrenchCL wrapper internals. Improves debuggability of production failures.