Conversation
Remove debug log statement for file info retrieval.
navin772
approved these changes
Mar 16, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Mar 16, 2026
## [0.34.1](v0.34.0...v0.34.1) (2026-03-16) ### Miscellaneous Chores * remove too much log ([#162](#162)) ([737895d](737895d))
|
🎉 This PR is included in version 0.34.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
2 participants
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.
I think this line logs too many logs, some could be kind of sensitive while they are at the debug level. In terms of the debug purpose, the caller can give better logs if needed.
e.g. They could print an installed app, etc., regularly. They are fine for testing devices only in publicly used areas, but this could be too sensitive for individual users.