yatisht / usher

Ultrafast Sample Placement on Existing Trees
MIT License
122 stars 41 forks source link

Web USHeR -- dropdown to monkeypox not working #277

Closed sidneymbell closed 1 year ago

sidneymbell commented 2 years ago

Reverts the value to 'SARS-CoV-2' immediately after selection. If you'll point me in the right direction I'm happy to help fix this one if you'd like :)

Chrome Version 105.0.5195.125 (Official Build) (x86_64)

AngieHinrichs commented 2 years ago

Oh, that's not good! Thanks for letting us know, I'll take a look.

AngieHinrichs commented 2 years ago

As a temporary workaround -- our test server doesn't have this problem: https://genome-test.gi.ucsc.edu/cgi-bin/hgPhyloPlace

AngieHinrichs commented 2 years ago

It looks like there might have been a temporary problem with our "assembly hub" for monkeypox. If you go to My Data -> Track Hubs in the top blue bar menu (or https://genome.ucsc.edu/cgi-bin/hgHubConnect), are there any error messages in red for "Monkeypox virus (MPXV-M5312_HM12_Rivers 2022)"? If so, can you click the "Retry hub" button and then try https://genome.ucsc.edu/cgi-bin/hgPhyloPlace again?

sidneymbell commented 2 years ago

No error messages on the hubs page, and the dropdown is working now. Just ran the example mpx data and it works :) Thanks for investigating!

On Wed, Sep 28, 2022 at 5:26 PM Angie Hinrichs @.***> wrote:

It looks like there might have been a temporary problem with our "assembly hub" for monkeypox. If you go to My Data -> Track Hubs in the top blue bar menu (or https://genome.ucsc.edu/cgi-bin/hgHubConnect), are there any error messages in red for "Monkeypox virus (MPXV-M5312_HM12_Rivers 2022)"? If so, can you click the "Retry hub" button and then try https://genome.ucsc.edu/cgi-bin/hgPhyloPlace again?

— Reply to this email directly, view it on GitHub https://github.com/yatisht/usher/issues/277#issuecomment-1261598222, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADAIYX6F5MAE7E7NFTL53CDWATOZ5ANCNFSM6AAAAAAQYIHP2I . You are receiving this because you authored the thread.Message ID: @.***>