You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
The text was updated successfully, but these errors were encountered:
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.
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
Unexpected behavior while reproducing the docs:
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:
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?)
The text was updated successfully, but these errors were encountered: