Empty registry page - Githubissues

BioContainers / registry

Docker for Bioinformatics

http://biocontainers.pro

Apache License 2.0

20 stars 15 forks source link

Empty registry page #116

Closed junelsolis closed 2 years ago

junelsolis commented 3 years ago

Browsing to biocontainers.pro/registry shows an empty page with a spinner. After several seconds, the browser console shows the following error:

osallou commented 3 years ago

@ypriverol seems there is an issue with registry.

neoformit commented 2 years ago

I am also getting inconsistent errors at /registry. It errorred twice and worked once.

Console output:

Console log:

biocontainers.pro-1633040680754.log

Browser view:

osallou commented 2 years ago

Hi, Just did a test and worked. Are you still facing the issue?

junelsolis commented 2 years ago

Hello, thanks for the update. It kind of works...

It takes almost 1 minute with the "pulsing dot" spinner, until the empty list shows up saying "No Data". But there is a pagination control at the bottom. 🤷🏼‍♂️

If I type a search query, then a list of results shows up:

If I then emtpy the search query, then now it shows the containers in alphabetical order.

Is the default behavior supposed to be that the registry search page shows all the containers by default?
There are several console messages being output by Vue. Shouldn't this be hidden in a production environment?

osallou commented 2 years ago

Regading vuejs, yes should not appear, but not a big deal ;-) nothing private. I suppose app is somehow in dev mide vs prod mode.

Regarding listing of containers, we had other reports indeed, though when i tested it was fine. Display is a bit long, because it seems that all data are loaded instead of using full pagination mechanisms. So time for display will depend on your bandwith. This should be enhanced however for quicker results.

osallou commented 2 years ago

The search/list behavior is not linked. Async requests are done, and main request toon long time to end. While your were on search, first request finished, and this explains you finally got the results. You just did not wait long enough.

But as i said, this should be reworked as such long time to get data is not a good user experience...

pveber commented 2 years ago

For me (under Firefox/Linux and chromium), the search form remains grayed and blank, even after several hours. The browser log says there's a blocked cross-origin request.

osallou commented 2 years ago

yeap could reproduce today, seems to work "sometimes" but here facets request on containers failed @ypriverol can you look at registry web issues?

though always quite long, I created an issue to fix such delay....