Repository navigation
chore: merge 4.18.1 into master - #3572
Conversation
* fix: recover a workspace that starts without a network (#3560) When the app starts before the network or a VPN is up, the server's service worker holds the first navigation open and never answers it. Electron then reports no failure, so the workspace stays gray and does not recover when the connection comes back. The main process now probes the server when a main-frame navigation has no response after 3 seconds. A network error shows the failure view at once. A navigation that is still held while the server answers loads again one time. After a network failure, the main process probes every 2 seconds and loads the page as soon as the server answers. A server that refuses connections gets a longer interval, up to 30 seconds, with jitter. The failure view also reloads on the OS online event, and main-frame load failures are now logged. (cherry picked from commit edb3d06) * chore: bump version to 4.18.1
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
WalkthroughThe change adds stalled-navigation detection and server reachability probing for server views. It also retries failed server panes when the window comes online and updates the package and macOS bundle versions. ChangesServer view recovery
Release version metadata
Priority: ⬇️ Low Estimated code review effort: 4 (Complex) | ~45 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant WebContents
participant watchStuckNavigation
participant probeServer
participant ServerView as serverView/index.ts
WebContents->>watchStuckNavigation: navigation and loading events
watchStuckNavigation->>probeServer: probe server reachability
probeServer->>WebContents: issue HEAD request through guest session
probeServer-->>watchStuckNavigation: return probe result
watchStuckNavigation->>ServerView: report stuck, held, or recovered navigation
ServerView->>WebContents: reload server URL when reachable
Suggested labels: Merge Risk: ⚪ Minimal · up to No actionable issue was established that would block this release merge. Refused-connection recovery remains unverified. Pre-merge checks |
|
Merge the 4.18.1 patch release into
master, so thatmasterholds the latest stable release.This is the first merge under the rule in #3571.
release/4.18.xis 4.18.0 plus the 4.18.1 release commit (#3561), so the merge has no conflicts.Merge with a true merge commit (
gh pr merge --merge). Do not squash.Summary by CodeRabbit