search

gbif / metabarcoding-data-toolkit-ui

Frontend for the eDNA tool
5 stars 1 forks source link

Fix error upon pressing "Create Darwin Core Archive" #113

Closed tobiasgf closed 2 weeks ago

tobiasgf commented 4 months ago

Processing example dataset 1

With minimal metadata:

image

And proceeding to "Export", pressing "Create Darwin Core" gives this error (tested a couple of times by me, and also reported by a user)

image
timrobertson100 commented 4 months ago

I tried it and it worked in the tool and I was able to push it to the UAT environment.

MattBlissett commented 4 months ago

Do the accounts need permissions in the Registry? i.e. organization namespace scope or similar.

tobiasgf commented 4 months ago

I tried it and it worked in the tool and I was able to push it to the UAT environment.

My tests fail already at the "Create DWC" step, not "push to UAT"

timrobertson100 commented 4 months ago

I have added both INVITED_TESTER and then REGISTRY_ADMIN to tobiasgf user and he reported the same even after logging out and then in again.

However, Tobias gave me his password, and I was able to run the whole thing resulting in this dataset using tobias's account.

I wonder if another tab open or so has got in the way. This seems like it might be a browser specific issue to me, not a server side one

tobiasgf commented 4 months ago

UPDATE: I am able to process all the way in Safari, but Chrome consistently fails. So it is something in my Chrome (@timrobertson100: "I suspect this is role permissions, and some caching on your chrome") I will try to investigate softly without wiping my chrome completely, and losing possibility to identify the cause.

It seems that I am being logged out of the tool at the "Export Page" when pressing the "Create DWC" button. On first pressing of "Create....", it gives the error in the screenshot above. If I refresh the page after the error shows up, my username is replaced by "login" (i.e. I am logged out). If I then login (still at the "Export page"), and then press "Create ...", it creates a DwCA that I can push to UAT. Tried this successfully from fresh upload three times now.

thomasstjerne commented 2 weeks ago

Closing this, please re-open if it occurs again. Isabel had a similar issue which related to cached responses that ignored auth headers. I fixed that with updated cache control headers.