Bump ezvpn native DLL to 0.0.49; show reconnect progress in the status panel - #28
Merged
Merged
Conversation
…s panel
The core's desktop reconnect loop (which ezvpn_start runs) now publishes its
progress in the status JSON: failed_attempts, next_attempt_secs, last_error.
Read those keys in ClientStatus and surface them in the detail panel: the
state reads "Reconnecting…" once an attempt has failed, and a warning InfoBar
says how many attempts failed, when the next is due ("3 failed attempts,
next in 8s", or "trying now"), and the last error, so a backoff wait (up to
60s at the cap) reads as waiting rather than stuck.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Pin
native.targetsto ezvpn v0.0.49 (scripts/bump-dll.ps1).The core's desktop reconnect loop, which
ezvpn_startruns, now publishes its progress in the status JSON (failed_attempts,next_attempt_secs,last_error). This reads those keys inClientStatusand surfaces them in the detail panel:Verified with
ci\windows\remote.ps1 cion the CI VM: build, 48 tests, self-contained publish, and MSI all pass.🤖 Generated with Claude Code