Arvados: Issueshttps://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422015-06-05T20:56:01ZArvados
Redmine Tapestry - Idea #6257 (In Progress): Add public facing database dump, cron job and Arvados uploadhttps://dev.arvados.org/issues/62572015-06-05T20:56:01ZAbram Connellyabram.connelly@gmail.com
<p>There is code to do a dump of the public facing data. Merge it into Tapestry, create a cron job to automatically run on a daily basis and have it upload to an Arvados project.</p> GET-Evidence - Bug #6143 (New): Add 'nofollow' to download links for reporthttps://dev.arvados.org/issues/61432015-05-22T21:29:54ZAbram Connellyabram.connelly@gmail.com
<p>Web crawlers hammer the keep servers asking for the data files from links that appear in the reports. Add 'nofollow' on relevant links from the report page.</p> GET-Evidence - Bug #5883 (New): migrate to updated oauthhttps://dev.arvados.org/issues/58832015-05-01T18:31:33ZAbram Connellyabram.connelly@gmail.com
<p>There is a warning on that says OAuth2 is going away. We need to migrate the authentication on GET-Evidence to make sure login is still possible.</p> GET-Evidence - Feature #5873 (New): GET-Evidence pipeline code should be publichttps://dev.arvados.org/issues/58732015-04-30T22:55:20ZAbram Connellyabram.connelly@gmail.com
<p>The GET-Evidence pipeline should be put under a public git repository.</p>
<p>Currently the GET-Evidence repository is under my (Abram Connelly) private Arvados git repository. This should probably remain but some hooks should be added somewhere so that the repository is pushed to a public Curoverse repository.</p> GET-Evidence - Bug #5872 (In Progress): 23andMe report pipeline is brokenhttps://dev.arvados.org/issues/58722015-04-30T22:52:53ZAbram Connellyabram.connelly@gmail.com
<p>When participants upload their 23andMe data, this kicks off a pipeline run through Arvados (now) through the same code path that the dataset submission goes through from Tapestry. The pipeline is failing to correctly generate reports for 23andMe data.</p>
<p>Porting the pipeline over to Arvados, the format for the input was changed and that's why the pipelines are failing on 23andMe data. I think the best thing to do going forward is to be more liberal about what input collection is specified so that 23andMe reports along with older reports can be run (or re-run) without having to worry about updating to the new format.</p>
<p>The old format just specifies a portable data hash. The new format expects <PDH>/<filename>.</p> Lightning - Idea #5001 (New): Create a API interface to the public tile library including a "beacon"https://dev.arvados.org/issues/50012015-01-16T18:29:36ZSarah Guthriesallyeguthrie@gmail.comLightning - Idea #4827 (New): Automatic Deployment Implementationhttps://dev.arvados.org/issues/48272014-12-15T22:59:30ZSarah Guthriesallyeguthrie@gmail.com
<p>Goal: have an automatic process to run tests and setup Lightning that is run when a commit is pushed to master</p>
Steps:
<ol>
<li>Research how to structure the git repository</li>
<li>Research/communicate with Ward how to set up automatic deployment</li>
<li>Start writing tests and deploying</li>
</ol>