You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run export GI_PERSIST= && grunt or export GI_PERSIST=sqlite && grunt dev, with enough files in ./data to make a server restart slow enough, i.e. at least slower than a frontend rebuild. The issue won't show up otherwise.
Visit http://localhost:3000
Make a trivial change in a shared file, e.g. remove a character in a comment in ./shared/functions.js
Expected behavior:
The app should display a "Trying to reconnect..." banner for a while, then reload normally without that banner nor errors in the console.
Actual behavior:
The app quickly reloads, but starts displaying a "Trying to reconnect..." banner for a while, then the banner disappears but the page is unable to finish loading (the page load indicator stays cross-shaped). There are connection errors and reconnection attempt messages in the console:
Solution
Make sure to only reload the browser when the backend is fully ready to accept connections and serve assets.
The text was updated successfully, but these errors were encountered:
Problem
Steps to reproduce:
export GI_PERSIST= && grunt
orexport GI_PERSIST=sqlite && grunt dev
, with enough files in./data
to make a server restart slow enough, i.e. at least slower than a frontend rebuild. The issue won't show up otherwise.http://localhost:3000
./shared/functions.js
Expected behavior:
The app should display a "Trying to reconnect..." banner for a while, then reload normally without that banner nor errors in the console.
Actual behavior:
The app quickly reloads, but starts displaying a "Trying to reconnect..." banner for a while, then the banner disappears but the page is unable to finish loading (the page load indicator stays cross-shaped). There are connection errors and reconnection attempt messages in the console:
Solution
Make sure to only reload the browser when the backend is fully ready to accept connections and serve assets.
The text was updated successfully, but these errors were encountered: