Closed doomedramen closed 10 years ago
I'm afraid I still can't reproduce this.
The following track configuration works for me in both 0.12.4 and the latest master branch:
{
"name": "qwerty.asdf",
"tier_type": "memstore",
"payload": "vcf",
"uri": "http://www.biodalliance.org/datasets/tests/qwerty.asdf.vcf"
}
(look around chr2:26791287 to see some features). I've also tried adding the same file via the UI, both as a URL -- in which case it generates a config identical to the above -- or from a local file, both of which work fine.
I've tested in recent versions of Chrome, Firefox, and Safari.
Is there any chance of getting an exact sequence of steps (preferably including a test file) which reproduces this?
Also, are those the actual file-names you tested with?
Closing because this turned out to be a server-configuration issue.
file names should not have them in anyway but I just wanted to let you know that dalliance fails to load vcf files (only file type I have tested this with) if there is a '.' anywhere in the name except in the place you would expect it:
qwerty.asdf.vcf = fail qwerty_asdf.vcf = fine
This happens when suppling the file source in the browser config