Fail gracefully on IGV attempts to open invalid SODAR URLs

[mikkonie]

Something I noticed when testing IGV integration for SODAR v1.0.0-WIP in staging.

After opening a session file, IGV performs another request to SODAR using the session serving URL, followed by the genome ID. This of course fails as this is not a valid URL. Example in IGV log:

INFO [Feb 20,2025 13:04] [GenomeManager] Loading genome: https://sodar-staging.bihealth.org/samplesheets/study/germline/render/igv/b37_1kg
SEVERE [Feb 20,2025 13:04] [MessageUtils] Error loading genome: b37_1kg
SEVERE [Feb 20,2025 13:04] [MessageUtils] org.broad.igv.exceptions.HttpResponseException: Internal Server Error

I'm not sure what is happening here. I did get an error message when starting up IGV about not being able to load the genome, so I suppose these are somehow related?

IGV experts, feel free to chime in. What should be done about this on the SODAR side?

Does this also happen in SODAR v0.15.1 if certain conditions are met? If so, which conditions?

At the very least, we should probably return with a more graceful error than a dump of the 500 error HTML. Since these requests always hit the same study app views, that would be doable.

I tested this with IGV v2.19.1, with b37_1kg as the genome.

[mikkonie]

I can confirm this also happens to me on v0.15.1 running in production at the time of writing. I'm guessing it's related to how I've (mis)configured IGV.

This is also related to #1795, as I also see those errors when this happens.

[mikkonie]

Thanks to @Nicolai-vKuegelgen for helping me out with this. I simply need to choose the genome manually first, then all works.

Nevertheless, we should implement a graceful 404 error instead of a 500 internal failure, if IGV calls the server with an invalid URL. This should also enable us to close #1795.

It's not super urgent, so I'm tagging this for v1.1.