search

galaxyproject / galaxy

Data intensive science for everyone.
https://galaxyproject.org
Other
1.4k stars 1.01k forks source link

Reports: clicking on individual jobs in reports generates "failed to connect" #15966

Open hexylena opened 1 year ago

hexylena commented 1 year ago

It works fine (lettting me see tables of information, failed jobs, etc.) But as soon as I click on a single job, it fails to connect:

Screenshot_2023-04-20_10-47-32

because it's connecting to 'localhost' rather than the proper hostname (gat-7) https://gat-7.eu.galaxy.training/reports/

hujambo-dunia commented 1 year ago

Thanks @davelopez for your assistance looking into getting the Reports Admin configuration file loading.

davelopez commented 1 year ago

We discussed this in the backend meeting and decided that the reports app is in very low maintenance mode, so this will have little priority and probably won't be fixed soon.

hexylena commented 1 year ago

so reports will be unusable for the foreseeable future then, ok. Should we disable the training material? add a big warning box?

we see people accessing it semi regularly, and admins tend to still like setting it up because the grafana stack doesn't do all the same things and is significantly more complex.

davelopez commented 1 year ago

Please understand this is a matter of capacity and priorities, it is still open source, so if someone really needs this fixed a PR is very welcome :pray:

hexylena commented 1 year ago

oh, of course, I understand. Just wondering how y'all would prefer we handle it on the training side, since that's the primary entrypoint for folks into trying to use reports.

If this is a "time will not be allocated for this, but PRs are welcome" situation then we should hide the material or mark it deprecated. However if it's a "We plan to fix this at some point in the future (but PRs welcome in the meantime)" situation, then maybe we just add a warning box or so, so admins know it's still considered a supported galaxy component, just temporarily having issues.

mvdbeek commented 1 year ago

It should still work fine without proxy prefix, so a subdomain is a more robust solution (true for Galaxy as well ... but there it's worth spending the effort to fix it) .