This only happens after deploying. Clicking on the test-dataset of human_sten_May29 results in:
Failed to load resource: the server responded with a status of 500 (INTERNAL SERVER ERROR)
It tries and fails to load http://loom.linnarssonlab.org/loom/hg19_sUCSC__midbrain__human_sten_May29/fileinfo.json. However, if we follow this link explicitly, we get the json-file as expected. Furthermore, if after doing so we go back to the same page, the error is gone.
So something's fishy on the server side; this might also happen with newly created datasets so it's probably worth digging into for that reason alone.
Ok, I guess it was just me being too impatient plus a freak coincidence of the JSON file being regenerated exactly when I explicitly followed the link three deployments in a row.
This only happens after deploying. Clicking on the test-dataset of
human_sten_May29
results in:It tries and fails to load
http://loom.linnarssonlab.org/loom/hg19_sUCSC__midbrain__human_sten_May29/fileinfo.json
. However, if we follow this link explicitly, we get the json-file as expected. Furthermore, if after doing so we go back to the same page, the error is gone.So something's fishy on the server side; this might also happen with newly created datasets so it's probably worth digging into for that reason alone.