Loading local tilesets: issue with enabling proxy; docs section on enabling proxy

[agalitsyna]

Unexpected behavior while reproducing the docs:

• Section of the docs is not running when working on a remote computer: http://docs-python.higlass.io/getting_started.html#numpy-matrix
• Missing required argument for LocalTileset: datatype="matrix"
• Plugin tracks produces "unknown track types" error: http://docs-python.higlass.io/getting_started.html#plugin-tracks

Potential solutions and my elaboration on why I cannot make it work for now:

• [ ] Introduce the disclaimer for people working with higlass-python remotely. Ideally, that shall go into two places in the documentation: https://docs-python.higlass.io/getting_started.html#example and http://docs-python.higlass.io/getting_started.html#serving-local-data

  The code string to be explained is:

  import higlass as hg
  hg.server.enable_proxy()
  

• [ ] With outsourcing the provider to servir, it's very hard to track how the proxy port number is being used.

  Most likely it's being corrupted somewhere on the way, and here is the problem that I got:

  However, there are also tests of the server that seem to run okay on GitHub: https://github.com/higlass/higlass-python/blob/main/test/test_server.py So that might be some type of problem with dependencies versions that are not pinned correctly (but what dependencies shall be checked in the first place?)

[manzt]

Thanks for opening this issue. I no longer have access to blob, which is where I was testing this remote functionality previously (specifically, enable_proxy). I'm spending today trying to simulate a remote environment locally (with Docker) and hopefully will have a better sense of what is going on.

[alexbarrera]

Hi all-- having a similar issue here. Does anyone have an update on this? I can piggy back with more details, but curious if this perhaps has been addressed but not commented on. Thanks a lot