Visdom display abnormally: blank blue screen or messy layout.

[cai-linjin]

Bug Description I am using visdom in a remote headless machine, and I use port forwarding to visit visdom. I map my local machine's 8098 port to the remote's 8097. I've done this several times and it works well. However, I rent a new machine and reinstall visdom recently, and visdom cease to function. Visdom cannot display nomally.

Reproduction Steps Enter steps to reproduce the behavior:

1. Install visdom in the remote machine(Ubuntu 18.04), map 8097 to the remote's 8098
2. Config SSH port forwarding
3. Visit localhost:8098

Screenshots When I visit http://localhost:8098/, the display is as follows: As we can see, the layout is quite messy. Even I try to display some text through visdom.text, nothing appears. and if I visit http://127.0.0.1:8098/, I get a blue blank screen like this:

Server logs: For any issues, please include the server logs. These are printed directly to stdout on the machine running visdom (python -m visdom.server).

root@C.518834:~$ python -m visdom.server /opt/conda/lib/python3.7/site-packages/visdom/server.py:39: DeprecationWarning: zmq.eventloop.ioloop is deprecated in pyzmq 17. pyzmq now works with default tornado and asyncio eventloops. ioloop.install() # Needs to happen before any tornado imports! Checking for scripts. Downloading scripts, this may take a little while It's Alive! INFO:root:Application Started You can navigate to http://localhost:8097 INFO:tornado.access:304 GET / (127.0.0.1) 22.54ms INFO:tornado.access:304 GET /static/fonts/glyphicons-halflings-regular.woff2 (127.0.0.1) 2.23ms INFO:tornado.access:101 GET /socket (127.0.0.1) 1.16ms INFO:root:Opened new socket from ip: 127.0.0.1 INFO:tornado.access:200 GET /favicon.png (127.0.0.1) 20.49ms INFO:tornado.access:200 POST /env/main (127.0.0.1) 1.73ms INFO:tornado.access:200 POST /env/main (127.0.0.1) 9.66ms INFO:tornado.access:304 GET /extensions/MathMenu.js?V=2.7.1 (127.0.0.1) 19.57ms INFO:tornado.access:304 GET /extensions/MathZoom.js?V=2.7.1 (127.0.0.1) 23.99ms INFO:tornado.access:200 GET / (127.0.0.1) 20.23ms INFO:tornado.access:200 GET /favicon.png (127.0.0.1) 20.21ms INFO:tornado.access:304 GET /extensions/MathMenu.js?V=2.7.1 (127.0.0.1) 19.77ms INFO:tornado.access:304 GET /extensions/MathZoom.js?V=2.7.1 (127.0.0.1) 24.67ms

[cai-linjin]

Also, in the first case(localhost:8098), the browser gives a "File failed to load: /extensions/MathZoom.js" message.

[300LiterPropofol]

Hi, did you solve this issue? I have a similar issue after changing to a new virtual environment. Not only the screen is blank, when I am using self.vis = visdom.Visdom(env='new-env', use_incoming_socket=False, **kwargs) to create a new environment label, it doesn't show either. Basically it seems nothing is transmitted to the visdom server, it just keeps blank.

[HopePersist]

the same issue

[duxingren14]

the same issue.

[Shubhams-nd]

+1

[JackUrb]

Please check the JavaScript console in your browser - this kind of issue occurs when visdom cannot serve the JavaScript resources required for showing visualizations.

[jaredyam]

@JackUrb, I also got the blank blue screen, here are my Chrome console logs (since the Python server didn't throw any errors):

Uncaught SyntaxError: Unexpected token '<' ... layout_bin_packer.js ...:1
                                                                         ...main.js?v=...:95
Failed to decode downloaded font: http://localhost:8097/static/fonts/...woff2
Failed to decode downloaded font: http://localhost:8097/static/fonts/...woff
Failed to decode downloaded font: http://localhost:8097/static/fonts/...ttf

Uncaught ReferenceError: Bin is not defined (main.js...:48)

Do these logs make any sense?

[ath34-tech]

did someone manage to solve this issue? I am seeing blue screen whenever I am trying to contribute to UI, if you check line 58 of https://github.com/fossasia/visdom/blob/master/py/visdom/static/index.html then you will notice it is importing https://github.com/fossasia/visdom/blob/master/py/visdom/static/js/main.js not https://github.com/fossasia/visdom/blob/master/js/main.js.

On changing path file, still this issue is not resolving.

[JackUrb]

If this is happening after a build, it's possible that your build failed for some reason. If you rerun, and check the console closely, are there any messages about errors at all?

[ath34-tech]

same logs as @jaredyam , keep in mind that i got this error when I change main.js path, from py/visdom/static/js/main.js to /js/main.js

[JackUrb]

I'm referring to build errors when you're running the process to generate the bundle, not errors when trying to load it

[ath34-tech]

Sorry for being late! Here is what I got on running npm run build :

                      Asset      Size  Chunks                    Chunk Names
py/visdom/static/js/main.js  1.55 MiB       0  [emitted]  [big]  main
Entrypoint main [big] = py/visdom/static/js/main.js
  [9] ./node_modules/d3-selection/src/index.js + 4 modules 2.19 KiB {0} [built]
      |    5 modules
 [48] ./js/Pane.js 9.15 KiB {0} [built]
 [54] ./js/EventSystem.js 2.18 KiB {0} [built]
[150] multi ./js/main.js 28 bytes {0} [built]
[151] ./js/main.js 59.9 KiB {0} [built]
[307] ./js/PropertiesPane.js 12.7 KiB {0} [built]
[308] ./js/TextPane.js 7.66 KiB {0} [built]
[309] ./js/ImagePane.js 17.6 KiB {0} [built]
[310] ./js/PlotPane.js 9.05 KiB {0} [built]
[311] ./js/EmbeddingsPane.js 29 KiB {0} [built]
[314] ./js/lasso.js 3.48 KiB {0} [built]
[315] ./js/Width.js 7.83 KiB {0} [built]
[316] ./node_modules/d3-zoom/src/index.js + 49 modules 66.8 KiB {0} [built]
      |    50 modules
[317] ./node_modules/rc-tree-select/es/index.js + 32 modules 220 KiB {0} [built]
      |    33 modules
[318] ./node_modules/react-resize-detector/lib/esm/index.js + 19 modules 34.8 KiB {0} [built]
      |    20 modules
    + 334 hidden modules

WARNING in ./node_modules/encoding/lib/iconv-loader.js 9:12-34
Critical dependency: the request of a dependency is an expression
 @ ./node_modules/encoding/lib/encoding.js
 @ ./node_modules/fetch/lib/fetch.js
 @ ./js/main.js
 @ multi ./js/main.js

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  py/visdom/static/js/main.js (1.55 MiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  main (1.55 MiB)
      py/visdom/static/js/main.js

WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

[JackUrb]

Hm it seems the file was successfully emitted, so I'm not sure why you've changed the path - the file was emitted to py/visdom/static/js/main.js, not /js/main.js.

[ath34-tech]

Hey i solved my problem by running npm audit fix