fix: improve dump failure reporting and logging#45
Merged
deadman96385 merged 3 commits intoAndroidDumps:masterfrom Apr 4, 2026
Merged
fix: improve dump failure reporting and logging#45deadman96385 merged 3 commits intoAndroidDumps:masterfrom
deadman96385 merged 3 commits intoAndroidDumps:masterfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR improves failure reporting for firmware dump jobs by sourcing the failed step from error_context, capturing the last successful step from progress history, and attaching a sanitized failure log as a queued document for retryable delivery via the message queue.
Changes:
- Add a new queued
DOCUMENTmessage type and asend_document()API to deliver failure logs through the Redis-backed message queue. - Build and attach a plain-text failure log including progress history and sanitized traceback data, and improve “failed at” step selection using
error_context. - Redact URL credentials and query parameters for logged URLs, and tolerate malformed progress percentage values when generating the log output.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
dumpyarabot/message_queue.py |
Adds document-queue support (MessageType.DOCUMENT), expands QueuedMessage schema, and processes queued document deliveries. |
dumpyarabot/arq_jobs.py |
Builds/sends failure logs, improves failure step selection, and adds URL sanitization for log output. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
Issues FoundCritical (P0/P1)
|
60fe25a to
c70d603
Compare
- report the failed step from error_context instead of stale progress state - record the previous successful step from progress history - attach a failure log with progress history and sanitized traceback data - queue document delivery through the message queue for retry handling - redact URL credentials and query params in failure logs - tolerate malformed progress percentages when building log output
- add recovery.img to boot image processing in the Python extractor - unpack recovery ramdisks in the rewrite-native path - extract recovery device trees for parity with other boot image handlers
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
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.
ae07974removes emoji usage from Telegram messages so user-facing output is plain text4b5f525carries PR extract_and_push.sh: Extract recovery.img #42 recovery.img extraction into the rewrite for recovery ramdisk/device-tree parity