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
The behaviour on v1.0.0 is different from the above. There if the redis container is restarted (or just stopped), the visualisation rails process crashes.
The difference between v1.0.0 and main is the upgrade from Rails 7.0.8 to 7.1.3.
Regarding behaviour on main: it appears that the issue is that the rails process doesn't correctly re-establish a connection to the redis server. The result is that the redis server is unable to send the subscription confirmation from the browser client to the rails server.
Although it can do so when a second tab is opened. FSR!
If the redis container is restarted the live updates to the interactive rack view fails to initialise properly. To recreate:
This has been observed on current
main
(f8fd5d6) and also on the branch for #148 .The text was updated successfully, but these errors were encountered: