cache takes too long #413

New issue

Open

opened 2026-02-25 23:34:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:34:10 +03:00

Owner

Originally created by @DesarrolloAntonio on GitHub (May 21, 2024).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/918

Data

Shiori version: 1.6.3

Describe the bug / actual behavior

I have an Android app that interacts with Shiori's API. When I attempt to update a bookmark archive, the request takes an excessively long time, often several minutes when is a large bookmark.

Endpoint:
PUT http://192.168.1.68:18080/api/v1/bookmarks/cache

{
   "create_archive": true,
   "create_ebook": true,
   "ids": [37],
   "keep_metadata": true,
   "skip_exist": false
}

Initially, the timeout in android app was set to 30 seconds. I increased it to 50 seconds, but there are still bookmarks that I cannot update because the request times out.

It seems that the timeout issue is related to the length of the bookmark. Here is an example of large bookmark that causes this issue.
large bookmark

Expected behavior

The server should return the bookmark information promptly while creating the archive in the background.

To Reproduce

Steps to reproduce the behavior:

Add large bookmark
Update archive

Originally created by @DesarrolloAntonio on GitHub (May 21, 2024). Original GitHub issue: https://github.com/go-shiori/shiori/issues/918 ## Data - **Shiori version**: 1.6.3 ## Describe the bug / actual behavior I have an Android app that interacts with Shiori's API. When I attempt to update a bookmark archive, the request takes an excessively long time, often several minutes when is a large bookmark. Endpoint: **PUT http://192.168.1.68:18080/api/v1/bookmarks/cache** ``` { "create_archive": true, "create_ebook": true, "ids": [37], "keep_metadata": true, "skip_exist": false } ``` Initially, the timeout in android app was set to 30 seconds. I increased it to 50 seconds, but there are still bookmarks that I cannot update because the request times out. It seems that the timeout issue is related to the length of the bookmark. Here is an example of large bookmark that causes this issue. [large bookmark](https://levelup.gitconnected.com/how-i-built-a-social-network-in-4-years-as-a-solo-developer-4af70fb2d4c8 ) ## Expected behavior The server should return the bookmark information promptly while creating the archive in the background. ## To Reproduce Steps to reproduce the behavior: 1. Add large bookmark 2. Update archive

kerem added the

type:bug

label

2026-02-25 23:34:10 +03:00

kerem commented

2026-02-25 23:34:11 +03:00

Author

Owner

@fmartingr commented on GitHub (May 25, 2024):

Yeah, currently the data download task is a sync process. We could just launch this in background but right now we don't have means of telling the user what's the status of a background job. I'm currently working in something for that but is far from ready and it have other implications due to the nature of the bookmarks being available to all users at the moment.

@fmartingr commented on GitHub (May 25, 2024): Yeah, currently the data download task is a sync process. We could just launch this in background but right now we don't have means of telling the user what's the status of a background job. I'm currently working in something for that but is far from ready and it have other implications due to the nature of the bookmarks being available to all users at the moment.

kerem commented

2026-02-25 23:34:11 +03:00

Author

Owner

@fmartingr commented on GitHub (May 28, 2024):

Reopening for future reference.

@fmartingr commented on GitHub (May 28, 2024): Reopening for future reference.

kerem referenced this issue

2026-02-25 23:34:49 +03:00

[PR #413] [MERGED] fix: bookmark content download #588