Repository navigation
fix: after a broken EDL link the installer asks for another port or cable first - #95
Merged
Merged
Conversation
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.
For overpressure/overpressure#55
A backup that stops in the middle is almost always the USB port or the cable: stackSm4shr's backups went through once the link held, and so did mine after I moved the cable to another port.
run_dumpraisesDumpError, which keeps the dump's whole output, so overpressure'scapture_backupwrites it toedl.log(fix: a garbled reply in an EDL backup counts as a lost USB link, and edl.log keeps the failure overpressure#56). With an older overpressure it works as before.docs/device-preparation.md: a stopped backup is almost always the port or the cable, a garbled reply stops it too, andedl.logkeeps the failure.Checked: the host tests against #56's branch, ruff and ty, the docs and private-data checks. Not run on a headset with this code.