Enhance logging for IOError in file writing process #866
Conversation
This file contains 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
|
Were you able to identify errors for your use case with this change? |
Blankdlh
force-pushed
the
enhance-ioerror-logging
branch
from
f57571b to
53c5fe8
Compare
Sorry, some of my local code was not properly committed. I am using https://github.com/boredazfcuk/docker-icloudpd. It's not easy for me to set up the development environment. 😂 |
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.
In my use case, a large number of download tasks reported an IOError, but the files were actually downloaded successfully. Upon reviewing the source code, I found that the current error message for IOError is static. Therefore, I aim to output the real error reason to improve clarity and debugging.