vercel[bot]
commented
1 week ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| live-visual-editing-next | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-astro | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-next | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-next-with-i18n | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-nuxt | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-page-builder-demo | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-remix | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-studio | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
| visual-editing-svelte | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 14, 2024 5:45pm |
Currently, comlink's node state machine will only handle syn handshake events when in an
idlestate. In some situations, the controller or some of the channels it maintains may detect a loss of connection and transition to ahandshakingstate, the disconnect event emitted at this point may then fail to reach the relevant node(s), and thus the node will remain in aconnectedstate, as the nodes themselves only blindly respond to heartbeat events.This PR adds a change so that the node state machine will always transition to its internal
handshakingstate when receiving a syn handshake event, regardless of the state it is currently in. This should greatly improve the success rate of attempt reconnects. For example you may have noticed in our test environments that the connection is often lost after a HMR, this should no longer be the case.It also drops the default expected response timeout to 3s from 10s for requests for all requests that expect a response except for those initiated with
.fetch(which remains at 10s).