Images not always loading (item view)

DHBern / herbarium-frontend

This is a static catalogue of resoursces belonging to the Herbarium des Botanischen Gartens der Universität Bern

https://dhbern.github.io/herbarium-frontend/

0 stars 0 forks source link

Images not always loading (item view) #5

Closed pdaengeli closed 1 month ago

pdaengeli commented 1 month ago

Loading the item views from the data table on https://herbarium-bernense.ch works and successfully displays the IIIF images.

Loading the item view directly (or reloading the successfully loaded view) in some cases fails to show the image.

This might not be the full picture, but loading Sheets items works for me, whereas BERN doesn't:

https://herbarium-bernense.ch/item/Sheet-0036777 :white_check_mark:
https://herbarium-bernense.ch/item/Sheet-0040000 :white_check_mark:
https://herbarium-bernense.ch/item/BERN-0068087 :red_circle:
https://herbarium-bernense.ch/item/BERN-0068087 loaded from data table :white_check_mark:
https://herbarium-bernense.ch/item/BERN-0066969 :red_circle:
https://herbarium-bernense.ch/item/BERN-0066969 loaded from data table :white_check_mark:

I get the very generic NS_ERROR_FAILURE

Tested only in Firefox/Librewolf but on two different computers in different networks.

Can you reproduce this?

flicksolutions commented 1 month ago

I just saw this issue (didn't see it because I wasn't mentioned or assigned) This is actually an interesting one! Can reproduce it.

flicksolutions commented 1 month ago

interestingly, on all the images that don't load, the same iiif-path is requested! I must have messed something up... Let's hope it's small :-)

pdaengeli commented 1 month ago

(didn't see it because I wasn't mentioned or assigned)

Is that due to your notification settings? Generally, the repo owner/maintainer should get notified of new issues without mention or assignment.

flicksolutions commented 1 month ago

yes: grafik

I'll be watching this repo from now on.

It's good practice to always assign someone to the issue anyways. ;-)

pdaengeli commented 1 month ago

It's good practice to always assign someone to the issue anyways. ;-)

I tend to agree within a team, but not in general. Users opening issues often lack knowledge about competency/responsibility/availability of maintainers/contributors.

flicksolutions commented 1 month ago

This seems to be solved after a package update and rebuild... I have no Idea what the reason was... Can you confirm @pdaengeli ?

pdaengeli commented 1 month ago

Looks good on my end.

Pity we don't have any uptime testing in place where we could monitor successful loading of a test image (besides general availability of the site).

Did I mention our vague plan to run e.g. kuma as a DSL/DH service? But that's for another day.