Shopify / dashing

The exceptionally handsome dashboard framework in Ruby and Coffeescript.
http://shopify.github.com/dashing/
MIT License
10.97k stars 1.18k forks source link

Events not getting updated with Firefox #210

Open maakuth opened 11 years ago

maakuth commented 11 years ago

I'm hosting Dashing with Ubuntu 12.04 with nginx 1.4.2, Ruby 2.0.0 and Passenger 4.0.14. It works fine otherwise, but the widgets don't update with Firefox, although they do with Chrome. Firefox console shows messages "Connection opened" and milliseconds after that, "Connection error". Checking /events with curl shows that it gets updated correctly, which is also evident as Chrome is displaying updates normally.

I've tried adding these lines to nginx configuration, as someone suggested they could help the server sent events work:

proxy_set_header Connection '';
proxy_http_version 1.1;
chunked_transfer_encoding off;

But it doesn't help. I'm afraid this is some stupid issue, as I'm very much of a newbie when it comes to Ruby development as well as hosting. Thanks for Dashing though, it is very cool a framework.

buzali commented 11 years ago

I am experiencing the same issue, but with all browsers. Were you able to solve this?

cefigueiredo commented 10 years ago

Any news here? I'm getting the same trouble! But on a default thin server, on ruby 2.0.0 and 2.1.2, dashing 1.3.4

Yeah! The dashboard has started! application.js:19500
Connection opened 
Event
Connection error 
Event {clipboardData: undefined, path: NodeList[0], cancelBubble: false, returnValue: true, srcElement: EventSource…}
Connection opened 
Event {clipboardData: undefined, path: NodeList[0], cancelBubble: false, returnValue: true, srcElement: EventSource…}
nguyenchiencong commented 9 years ago

Same trouble here. +1

ghost commented 9 years ago

CentOS 6.6, Ruby 1.9.3, RubyGems 1.8.29, Puma 2.11.3, and Dashing 1.3.4.

Any word on this? I am also experiencing these same issues on Firefox ESR 38.0.1 and Chrome 43.0.2357.132.

Firefox console: "Connection opened" open { target: EventSource, isTrusted: true, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp: 1436919726507814, originalTarget: EventSource, explicitOriginalTarget: EventSource, NONE: 0 } application.js:15007:11

"Connection error" error { target: EventSource, isTrusted: true, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp: 1436919726546253, originalTarget: EventSource, explicitOriginalTarget: EventSource, NONE: 0 }

Chrome console: Connection opened Eventbubbles: falsecancelBubble: falsecancelable: falsecurrentTarget: EventSourcedefaultPrevented: falseeventPhase: 0path: Array[0]returnValue: truesrcElement: EventSourcetarget: EventSourcetimeStamp: 1436920393514type: "open"__proto__: Event application.js:15011

Connection error Eventbubbles: falsecancelBubble: falsecancelable: falsecurrentTarget: EventSourcedefaultPrevented: falseeventPhase: 0path: Array[0]returnValue: truesrcElement: EventSourcetarget: EventSourcetimeStamp: 1436920393529type: "error"__proto__: Event

adiabuk commented 8 years ago

+1 I'm occasionally seeing this too - any updates? Once it starts nothing gets updated and the onData/ready functions in the widgets don't appear to be getting executed anymore.