Skip to content
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

Fetch failed, checking IndexedDB cache #160

Open
NaomiBreslin opened this issue Jun 8, 2018 · 2 comments
Open

Fetch failed, checking IndexedDB cache #160

NaomiBreslin opened this issue Jun 8, 2018 · 2 comments

Comments

@NaomiBreslin
Copy link

I am having issues with the loom viewer and cannot seem to find any solutions online to fix it.
I have all of my loom files in the directory 'loom-datasets' which is created by loom viewer upon its first launch, but when the tool is launched it fails to read the files in the directory.
It states:
Fetch failed, checking IndexedDB cache
(If you see this while running the viewer locally, the loom-viewer probably failed to find any loom files in the loom datasets folder)

The only warning I can see when I launch loom from the terminal is:
loom_server.py:321: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. Please monkey-patch earlier. See gevent/gevent#1016
gevent.monkey.patch_all()

I was wondering if this may be the cause of the issue?
I have tried putting the loom files in a sub directory and changing the loom path but still no luck.

@JobLeonard
Copy link
Contributor

Hey Naomi, I don't see that error when I run loom, so you probably have something different in your Python set-up than me. Can you say a bit more about what version of Python you have, and how it's installed?

@NaomiBreslin
Copy link
Author

NaomiBreslin commented Jun 9, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants