logging regression: fix loglines/findCaller introspection #68042
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.
What does this PR do?
python 3.8 changed the way it was inferring loglines from the callstack; the stacklevel was exposed as a way around this to tell logging to ignore an arbitrary level of frames ontop of the 1 it knows about.
I tried writing a test but for whatever reason caplog / salt-test-factories doesn't exhibit the same behavior as directly running via CLI. this should be easily reproducible though.
Previous Behavior
note the 289
New Behavior
correct log lines
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes