{"action":"opened","issue":{"url":"https://api.github.com/repos/shashi/Escher.jl/issues/84","labels_url":"https://api.github.com/repos/shashi/Escher.jl/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/shashi/Escher.jl/issues/84/comments","events_url":"https://api.github.com/repos/shashi/Escher.jl/issues/84/events","html_url":"https://github.com/shashi/Escher.jl/issues/84","id":105880008,"number":84,"title":"Escher and websockets","user":{"login":"mdcfrancis","id":3129866,"avatar_url":"https://avatars.githubusercontent.com/u/3129866?v=3","gravatar_id":"","url":"https://api.github.com/users/mdcfrancis","html_url":"https://github.com/mdcfrancis","followers_url":"https://api.github.com/users/mdcfrancis/followers","following_url":"https://api.github.com/users/mdcfrancis/following{/other_user}","gists_url":"https://api.github.com/users/mdcfrancis/gists{/gist_id}","starred_url":"https://api.github.com/users/mdcfrancis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mdcfrancis/subscriptions","organizations_url":"https://api.github.com/users/mdcfrancis/orgs","repos_url":"https://api.github.com/users/mdcfrancis/repos","events_url":"https://api.github.com/users/mdcfrancis/events{/privacy}","received_events_url":"https://api.github.com/users/mdcfrancis/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-10T19:19:57Z","updated_at":"2015-09-10T19:19:57Z","closed_at":null,"body":"When you refresh a page from chrome it appears that Escher/Mux does not always notice the close of the websocket. Since the socket is keyed by the file name when next Escher tries to write to the socket it is in a closed state. This causes the process to bomb out, the symptom being an error from Reactive 'push! called when another signal is still updating'\r\n\r\nAny thoughts how to resolve / chase down? "}}