Fix an erroneous logging format string and pylint pragma #1630
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
This pull request fixes an incorrect logging format string and a pylint pragma that incorrectly disables its warning it.
I noticed this issue when using TorchServe's profiling mechanism via the
ENABLE_TORCH_PROFILER=1
environment variable, which resulted in surprising non-fatal stack traces. For example:Type of change
Feature/Issue validation/testing
It's a one-line change that can be understood in isolation.