Cannot plot a histogram with several observations

[mbenguig]

Bug Description
Tested with the latest version 0.2.4

Reproduction Steps
This works (histogram can be observed from the visdom server portal):

data = np.random.normal(0, 1, size=1000)
trace1 = go.Histogram(x = data, nbinsx = 50)
f0 = make_subplots()
f0.add_trace(trace1)

This does not work (the visdom server portal is empty .... cannot see any figure):

data = np.random.normal(0, 1, size=10000)
trace1 = go.Histogram(x = data, nbinsx = 50)
f0 = make_subplots()
f0.add_trace(trace1)

It seems it clearly depends on the number observations ('size' param)

Thxx

[mbenguig]

Dear Visdom team ... Any news about this critical issue ?

[JackUrb]

If the portal is entirely empty, can you check the server or client logs? I don't know why this would be breaking.

[mbenguig]

Thanks a lot for your replies. After having set the following variable VISDOM_LOGGING_LEVEL=DEBUG, the logs i am getting are:

INFO:root:Application Started
INFO:tornado.access:200 POST /env/main (172.17.0.1) 0.78ms
INFO:tornado.access:101 GET /vis_socket (172.17.0.1) 0.64ms
INFO:root:Opened visdom socket from ip: 172.17.0.1
INFO:tornado.access:200 POST /win_exists (172.17.0.1) 1.25ms
INFO:tornado.access:200 POST /win_exists (172.17.0.1) 1.19ms
INFO:tornado.access:200 POST /events (172.17.0.1) 5.08ms
INFO:tornado.access:200 GET / (172.17.0.1) 22.68ms
INFO:tornado.access:200 GET /static/css/bootstrap.min.css?v=ec3bb52a00e176a7181d454dffaea219 (172.17.0.1) 10.08ms
INFO:tornado.access:200 GET /static/css/react-resizable-styles.css?v=9f91a8dbf4d8f7ef1399e625660405f4 (172.17.0.1) 2.00ms
INFO:tornado.access:200 GET /static/css/react-grid-layout-styles.css?v=7dc8934d2f9ac5303b8f0bb1148152a0 (172.17.0.1) 2.25ms
INFO:tornado.access:200 GET /static/css/style.css?v=fb4729780f2360ef5d3dba13f8ff2873 (172.17.0.1) 1.37ms
INFO:tornado.access:200 GET /static/js/jquery.min.js?v=e071abda8fe61194711cfc2ab99fe104 (172.17.0.1) 2.04ms
INFO:tornado.access:200 GET /static/js/bootstrap.min.js?v=5869c96cc8f19086aee625d670d741f9 (172.17.0.1) 1.81ms
INFO:tornado.access:200 GET /static/js/react-react.min.js?v=bca103da5b5404d93783ccf73e0e9d1e (172.17.0.1) 1.85ms
INFO:tornado.access:200 GET /static/js/layout_bin_packer.js?v=6c46683ed70fbb1443caf3531243836d (172.17.0.1) 1.41ms
INFO:tornado.access:200 GET /static/js/react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3 (172.17.0.1) 2.23ms
INFO:tornado.access:200 GET /static/js/mathjax/2.7.5/MathJax.js?v=c32a502b8b4a6bd6bad8ddb1b59e9e72 (172.17.0.1) 1.77ms
INFO:tornado.access:200 GET /static/js/plotly-plotly.min.js?v=1f15d7ed9dd856a12c0469be4eede0cf (172.17.0.1) 19.70ms
INFO:tornado.access:200 GET /static/js/mathjax/2.7.5/config/TeX-AMS-MML_HTMLorMML.js?v=151537e3588ab41ce0782ae07386ff5b (172.17.0.1) 2.58ms
INFO:tornado.access:200 GET /static/js/main.js?v=6c8a353abc101b0e2c1cf327726f1caa (172.17.0.1) 10.63ms
INFO:tornado.access:200 GET /static/fonts/glyphicons-halflings-regular.woff2 (172.17.0.1) 1.47ms
INFO:tornado.access:101 GET /socket (172.17.0.1) 1.45ms
INFO:root:Opened new socket from ip: 172.17.0.1
INFO:tornado.access:200 GET /favicon.png (172.17.0.1) 24.03ms
INFO:tornado.access:200 POST /env/main (172.17.0.1) 10.54ms
INFO:tornado.access:200 POST /env/main (172.17.0.1) 1.04ms

So no issue .... any suggestion ?
++

[JackUrb]

Try the client logs (within your browser window), this points to it not being a server issue

[mbenguig]

I do not have any issue, neither at python level (at the histogram building level), nor at the visdom web browser level.
Sorry ;)

[JackUrb]

If you don't have any logs in your web client I cannot debug, as I cannot reproduce

[mbenguig]

Unfortunately, i do not have any issue in client logs ... but in my first message, i ve isolated the issue in few instructions... Did you try to test it on your side ?