Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2.5
-
Epic Link:
-
Sprint:Fall 3 2021 Sep 13 - Sep 24, Fall 4 2021 Sep 27 - Oct 8, Spring 4 2022 Feb 14 - Feb 25, Spring 5 2022 Feb 28 - Mar 11, Spring 6 2022 Mar 14 - Mar 25, Spring 7 2022 Mar 28 - Apr 8, Summer 1 2022 May 23
Description
The goal of this issue is to identify unknown bugs or usability issues in the current implementation of the track hub facade interface and back end.
Check at least one genome (ideally all of them) for each track hub.
Also, make note of any odd behavior in the genome and species menus. (These are populated from "species" and "synonyms" and "contents" endpoints and are therefore vulnerable to bugs in those endpoints.)
Attachments
Issue Links
Activity
The main issue seems to be related to IGBF-2964 and IGBF-3001. After doing some further investigation, I have noted the following:
Sample trackhub, for viewing SSL certificate in chrome: https://cgl.gi.ucsc.edu/data/cactus/363-avian-2020-hub/Antrostomus_carolinensis/
- Current validation as implemented here is not robust. Unexpected last element in certDomainComponents.
- expected: gov
- actual: gov, O=National Library of Medicine, L=Bethesda, ST=Maryland, C=US
- Alternative name in IGB is different from chrome
- IGB uses v2 of X.509, chrome uses v3. It could be that IGB is requesting outdated cert files form server by using v2 instead of v3
UPDATE IGB to use v3 - update dependency? Java version? java version 1.8.0_181 currently used in IGB
Attaching spreadsheet of defective quickload urls downloaded from spreadsheet created by Omkar Marne.
The newer Java update included in the new MacOS installer might correct the possible problem with IGB using v2 instead of v3 of something?
Re-opening this issue so that we can test it.
To test, try opening track hub from previous comment, quoting:
Sample trackhub, for viewing SSL certificate in chrome: https://cgl.gi.ucsc.edu/data/cactus/363-avian-2020-hub/Antrostomus_carolinensis/
Testing on Mac OS 11.6.5 with IGB zulu. My overall testing strategy was to add the track hubs as a new data source and attempt to load the genome and data.
I tested the track hub referenced in previous comments (https://translate.bioviz.org/api/?hubUrl=https://cgl.gi.ucsc.edu/data/cactus/363-avian-2020-hub/hub.txt&filePath=/) in IGB zulu and I was able to load data for Antrostomus carolinensis > b10kgenes > bigGenePred > Bird_10K_genes with no issues in the logs. However, when I tested this same file in IGB 9.1.8 release it also worked.
Upon testing other trackhubs mentioned to have issues in previous comments I ran into varying issues.
Attempting to load data from the track hub https://translate.bioviz.org/api/?hubUrl=https://data.broadinstitute.org/vgb/dog/dog/hub.txt&filePath=/ resulted in a null pointer exception in the BigBedSymLoader class.
Attempting to load data from the track hub https://translate.bioviz.org/api/?hubUrl=https://ftp.ncbi.nlm.nih.gov/snp/population_frequency/TrackHub/20200227123210/hub.txt&filePath=/ resulted in a URL not reachable, status code = -1 error.
Attempting to load data from the track hub https://translate.bioviz.org/api/?hubUrl=https://s3-us-west-2.amazonaws.com/croc-paper-hub/hub.txt&filePath=/ resulted in a URL not reachable, status code = 403 error.
Attempting to load data from the track hub https://translate.bioviz.org/api/?hubUrl=http://augustus.uni-greifswald.de/hubs/pisaster/hub.txt&filePath=/ resulted in an invalid URL or annots.xml not found error.
Attempting to load data from the track hub https://translate.bioviz.org/api/?hubUrl=https://data.cyverse.org/dav-anon/iplant/home/samksmith/steguina_track-hub/steguina/hub.txt&filePath=/ worked with no issues.
It is unclear to me what the issue was with the Antrostomus carolinensis genome data, as I was able to load the sequence and data. Without specific testing instructions for this genome I am unable to replicate and test the issue as it appears to work on both Zulu and release versions of IGB.
Regarding the other errors, there seems to be a myriad of errors occurring that are preventing data from loading from different track hubs, as outlined above. These public track hubs assume that the data are valid and the track hub hosting site configured correctly. Unfortunately I think this may not be the case as it appears some of the files may be corrupt, locked, or in general unreachable. It may be difficult and/or time consuming to track down why each of these data files fails to load in IGB.
Closing ticket.
Additional tickets may be needed to further investigate issues identified in this ticket.
Omkar Marne asks for clarification regarding "odd behavior":
How to test:
During testing, check the Species and Genome Version menus. Ensure that you see the species and genome versions of the Quickload there. The Genome Versions should be listed using the IGB name, not the UCSC name. If you notice the UCSC name instead, make a note of it. This is because IGB listing the UCSC name instead of the IGB name indicates that we would need to update our synonyms infrastructure.