Javascript error on filtering data base

nomad-coe / nomad

NOMAD lets you manage and share your materials science data in a way that makes it truly useful to you, your group, and the community.

https://nomad-lab.eu

Apache License 2.0

77 stars 16 forks source link

Javascript error on filtering data base #109

Closed p-bro closed 3 months ago

p-bro commented 3 months ago

Hi,

I'm running into a persistent JavaScript error when trying to browse the data base. On https://nomad-lab.eu/prod/v1/gui/search/entries, after selecting Method->DFT I select GGA in the Jacob's Ladder part. This loads the page https://nomad-lab.eu/prod/v1/gui/search/entries?results.method.simulation.dft.xc_functional_type=GGA which immediately crashes with the following error message:

Something went wrong in this part of the app (Javascript error). Please close all NOMAD tabs and try again. Let us know, if this error keeps happening.

Please, write to support@nomad-lab.eu, or open an issue on our github project.

Happened on both Chrome and Firefox.

Pepe-Marquez commented 3 months ago

Hi @p-bro, thanks for reaching out. Which browser are you using? It seems to work for me in Chrome. Can you try a hard-refresh (Crtl+Shift+R)?

p-bro commented 3 months ago

I tried accessing the link https://nomad-lab.eu/prod/v1/gui/search/entries?results.method.simulation.dft.xc_functional_type=GGA using three browsers (all on Mac OS Ventura 13.6.7):

Safari: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.6 Safari/605.1.15
Firefox: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:128.0) Gecko/20100101 Firefox/128.0
Chrome: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36

It also fails on Chrome on my mobile (Android). The symptoms are the same: I extremely briefly shows the page then flicks to the JavaScript error page. A hard reload didn't change anything, and the Safari session was a brand new browser session after a system reboot.

Pepe-Marquez commented 3 months ago

We will investigate. I figured out that I could reproduce the error if I was not logged in. If you want to have a look at the data while we put a fix, you can do it but just registering a NOMAD account and being logged.

With my NOMAD user being logged seems to work. @blueraft, @lauri-codes. Any hints on why this works only when logged in?

blueraft commented 3 months ago

This happened for me yesterday and I created an issue on Gitlab but it worked again today so I closed it. I wonder if there are some problematic entries that is causing this issue.

p-bro commented 3 months ago

I can confirm that it works once I'm logged in. I did have an account, but I could not be bothered to log in :)

Pepe-Marquez commented 3 months ago

Thanks for reporting @p-bro, it is really on our side. We are looking at it. We will keep you posted.

lauri-codes commented 3 months ago

We are aware of the issue and working on a fix. The temporary fix is to simply login, after which the queries work. I will update here once it is properly fixed.

lauri-codes commented 3 months ago

The fix has now been applied to our staging server: https://nomad-lab.eu/prod/v1/staging/gui/search/entries. This version holds the same data as our production one, but just has the newest version of the software.

We hope to fix this in the production deployment as well soon.

lauri-codes commented 3 months ago

The issue should now be solved. Please reopen if you still encounter this problem.