You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Clicking 'Fetch Metadata' for a book hangs the application, necessitating container restart.
To Reproduce
Steps to reproduce the behavior:
Open the application
Select any book
Click 'Edit Metadata'
Click 'Fetch Metadata'
'Fetch Metadata' window appears, and hangs on 'Loading' and eventually says 'Serch Error'
Application no longer responsive on browser refresh or in another tab (container restart required)
Expected behavior
The metadata is fetched and offered to the user.
Screenshots
Nothing informative appears in the 'Fetch Metadata' windows, so I won't screenshot that.
Configuration(please complete the following information):
OS: Docker Compose
Hardware: x86 N100 machine, 16GB RAM
Version :latest tag
Additional context
Neither the calibre-web logs (on DEBUG level), nor the container logs themselves show anything relevant/out of ordinary, which is why I'm not attaching them.
Presents similarly to janeczku/calibre-web#2562, but in this case as best as I can tell, the API is not down (and it doesn't even let me unselect APIs as the users in that issue suggest).
The text was updated successfully, but these errors were encountered:
Describe the bug
Clicking 'Fetch Metadata' for a book hangs the application, necessitating container restart.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The metadata is fetched and offered to the user.
Screenshots
Nothing informative appears in the 'Fetch Metadata' windows, so I won't screenshot that.
Configuration(please complete the following information):
Additional context
Neither the calibre-web logs (on DEBUG level), nor the container logs themselves show anything relevant/out of ordinary, which is why I'm not attaching them.
Presents similarly to janeczku/calibre-web#2562, but in this case as best as I can tell, the API is not down (and it doesn't even let me unselect APIs as the users in that issue suggest).
The text was updated successfully, but these errors were encountered: