BokehJS loading unnecessarily?

P.S. Here’s how I’m launching the app:

bokeh serve /coronagraph/apps/coron_model.py --port 5100 --host emac.gsfc.nasa.gov:443 --host emac.gsfc.nasa.gov:8101 \

–allow-websocket-origin emac.gsfc.nasa.gov:8101 --use-xheaders &

So, the important problem seems to be the first message:

WebSocket connection to 'wss://emac.gsfc.nasa.gov:8101/coron_model/ws?bokeh-protocol-version=1.0&bokeh-session-id=JbEuOy97gBYf3MR1lSHmTYCAIR1Diq2m01JGmMhlBR8t' failed: Failed to send WebSocket frame.
  send (bokeh.min.js:1:2064)

After some googling it seems there can be various potential causes of this. Perhaps this relevant?

  javascript - WebSocket connection failed: WebSocket opening handshake was canceled - Stack Overflow

Alternatively, if you create up a simple local setup *without* SSL, does it work in that?

Bryan

···

On Apr 10, 2017, at 15:10, Carl Hostetter <[email protected]> wrote:

P.S. Here's how I'm launching the app:

bokeh serve /coronagraph/apps/coron_model.py --port 5100 --host emac.gsfc.nasa.gov:443 --host emac.gsfc.nasa.gov:8101 \
        --allow-websocket-origin emac.gsfc.nasa.gov:8101 --use-xheaders &

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/3ad92854-6e51-4d80-b16b-892d1950bac0%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

Well, now this is very interesting…

If I bring the site up in Firefox (52.0.2, 64-bit) the app works just fine: all the controls are interactive and the plot updates accordingly, and there are not error messages in the console.

All the behavior I reported earlier has been in my default browser, Safari.

Does anyone have any idea why Safari and Firefox would behave differently with regard to web sockets?

P.S. Also works properly in Chrome 56.0.2924.87, 64-bit).

All on Mac OS X 10.12.4.

AND it works fine in Safari Technology Preview Release 27 (Safari 10.2, WebKit 12604.1.15.2).

Well that's interesting but also not ideal, since there's maybe nothing we can do about it. Here are some possibly related issues online (I haven't had time to dig into them deeply):

https://bugs.webkit.org/show_bug.cgi?id=170463

Some mention a high data rate as a correlated condition, are you sending a lot of data up front, etc?

Thanks,

Bryan

···

On Apr 11, 2017, at 12:19, Carl Hostetter <[email protected]> wrote:

AND it works fine in Safari Technology Preview Release 27 (Safari 10.2, WebKit 12604.1.15.2).

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/a8906bc6-73c3-4ec0-b6c8-e1e23cf72fd1%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

Thank you, Bryan, for the links, and for all your help.

At this point, I think I can safely chalk this up to an issue/bug with the current release version of Safari. I’ll monitor the behavior in subsequent releases.

I don’t know what constitutes “a lot” of data — nor did I write the Bokeh app I’m embedding, so I can’t say for sure — but it does indeed set up some tables on launch, I estimate about 13K. So that might be triggering the web socket issue.

Again, thanks!

Carl

I wanted to update on this, it looks like the very latest release of safari Version 10.1 (12603.1.30.0.34) released a few weeks ago may have broken some things in some subset of cases. We are looking into it.

···

On Tuesday, April 11, 2017 at 1:27:36 PM UTC-5, Carl Hostetter wrote:

Thank you, Bryan, for the links, and for all your help.

At this point, I think I can safely chalk this up to an issue/bug with the current release version of Safari. I’ll monitor the behavior in subsequent releases.

I don’t know what constitutes “a lot” of data — nor did I write the Bokeh app I’m embedding, so I can’t say for sure — but it does indeed set up some tables on launch, I estimate about 13K. So that might be triggering the web socket issue.

Again, thanks!

Carl