Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

huge 30s network timeouts on LCP LSD requests (Internet Archive) #2841

Open
danielweck opened this issue Mar 4, 2025 · 4 comments
Open

huge 30s network timeouts on LCP LSD requests (Internet Archive) #2841

danielweck opened this issue Mar 4, 2025 · 4 comments

Comments

@danielweck
Copy link
Member

https://lcp-lsd.prod.archive.org/licenses/93ce8eb1-5a88-4366-8119-5c345430c36e/status

@danielweck
Copy link
Member Author

danielweck commented Mar 4, 2025

broken UX: when opening a publication to read, when opening the "publication info dialog"...

Image

@danielweck
Copy link
Member Author

The encrypted EPUB download endpoint is fine https://archive.org/download/permutationcity0000egan/permutationcity0000egan_lcp.epub
(no LCP license, just raw encrypted data)

@danielweck
Copy link
Member Author

Same in web browser:

Image

@danielweck
Copy link
Member Author

@panaC I wonder if it would be possible to decrease the general HTTP timeout from 30s to 5-10s (MAX!) for LCP-LSD network requests?
If not, at the very least, we need a GUI "egg timer" / spinner while the user waits. In the top-right corner there is sometimes a circular loading indicator for other operations, which in my opinion is a bit too discrete, especially after waiting for 2 seconds ... maybe the spinner should grow bigger / more visible as time passes, for example during a large DAISY book import.

The LCP Status Document async/await promise does not trigger any visual "please wait" indicator, so the Thorium GUI looks stuck / frozen, feels like an application crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant