-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem higlass-ingest #21
Comments
Hi Samuel, One of the dependencies was updated and now returns a string rather than bytes. I'll issue a new release later this evening or tomorrow. In the meantime there's two things you can do:
Let me know if those don't work. |
Dear Peter,
Yes it worked! Thanks! Let me know when you made the new release :)
…On Feb 20 2019, at 8:46 pm, Peter Kerpedjiev ***@***.***> wrote:
Hi Samuel,
One of the dependencies was updated and now returns a string rather than bytes. I'll issue a new release later this evening or tomorrow.
In the meantime there's two things you can do:
Install slugid==1.0.7
Change line 170 of higlass_manage.py and remove the .decode('utf8') call.
Let me know if those don't work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#21 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARoG2bZ-QcydnLmIsmxZTzGSlogx3YZUks5vPaYugaJpZM4bFxvp).
|
Bump :) |
I really need to build that release. I refactored a ton of stuff in higlass-manage but haven't released it yet. This weekend I should have some time to get it out. |
Hi, I had the same issue as OP. I've taken your advice with the following:
I'm no longer getting the error message upon higlass-manage ingest. However, upon higlass-manage browse, i'm taken to an empty higlass browser. Any ideas?
Thanks! Will |
@golobor I just issued a new release (v0.6.0), would you mind giving it a try when you get a chance? @GDSCSussex Hi Will, it sounds like everything is working.
|
@pkerpedjiev Oh dear, I see now! Thanks for your reply. |
Hi,
I have a problem setting up a new instance of Higlass. I installed higlass-manage in the following way:
I can start Higlass:
$ higlass-manage start -t ~/HiGlass/tmp -d ~/HiGlass/data -m ~/HiGlass/media -p 8181 --no-public-data -n test
but then i do not manage to ingest any data:
It works with the higlass docker so I guess I did something wrong somewhere...
Many thanks,
Samuel
The text was updated successfully, but these errors were encountered: