Skip to content

fix: reliably complete configuration with progress=1000 or progress=0 - #8627

Merged
hpk42 merged 1 commit into
mainfrom
hpk/configure-always-reports
Aug 24, 2026
Merged

fix: reliably complete configuration with progress=1000 or progress=0#8627
hpk42 merged 1 commit into
mainfrom
hpk/configure-always-reports

Conversation

@hpk42

@hpk42 hpk42 commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

this is meant to help configuration event consumers (Python, UIs) to not hang waiting for configuration outcomes.
One test case is added that fails on main.

Comment thread src/configure.rs Outdated
// An ongoing process, e.g. a backup import,
// makes configuration fail without ever contacting a relay.
let _ongoing = t.alloc_ongoing().await?;
assert!(t.configure().await.is_err());

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be better to use add_or_update_transport, otherwise the test will have to be updated when we at some point remove configure. MailPw is also deprecated.

this is meant to help configuration event consumers (Python, UIs)
to not hang waiting for configuration outcomes.
One test case is added that fails on main.
@hpk42
hpk42 force-pushed the hpk/configure-always-reports branch from fc9a8dc to 4b2dfef Compare August 24, 2026 16:43
@hpk42
hpk42 enabled auto-merge (rebase) August 24, 2026 16:44
@hpk42
hpk42 merged commit ea3ca3a into main Aug 24, 2026
54 of 55 checks passed
@hpk42
hpk42 deleted the hpk/configure-always-reports branch August 24, 2026 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants