mirror of
https://github.com/Glitchy-Sheep/boosty-downloader.git
synced 2026-10-14 21:33:23 +00:00
[PR #106] [CLOSED] Expose message on download errors #114
Labels
No labels
api-drift
bug
ci
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Glitchy-Sheep/boosty-downloader#114
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/106
Author: @KairosOps
Created: 6/20/2026
Status: ❌ Closed
Base:
main← Head:codex/handle-download-error-message📝 Commits (1)
ab95a59fix: expose download error messages📊 Changes
2 files changed (+28 additions, -0 deletions)
View changed files
📝
boosty_downloader/src/infrastructure/file_downloader.py(+1 -0)➕
test/unit/file_downloader/download_errors_test.py(+27 -0)📄 Description
Fixes #105.
The crash happens because DownloadSinglePostUseCase._safely_process_chunk() logs and wraps lower-level download failures with e.message, but the DownloadError base class never assigned the message attribute it declares. DownloadUnexpectedStatusError therefore has a useful str(e), but no e.message, so the error handler raises an AttributeError while trying to report the original download failure.
This sets self.message in DownloadError.init, which keeps the existing application-level handling intact for all current DownloadError subclasses instead of patching one call site. I added unit coverage for the base error and DownloadUnexpectedStatusError so the attribute stays in sync with the exception text.
Checked locally:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.