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

[Bug] Can't mark previous as read if selected chapter is larger than 100 #909

Open
boydaihungst opened this issue Mar 25, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@boydaihungst
Copy link

boydaihungst commented Mar 25, 2024

Device information

  • Suwayomi-Server version: v1.0.0-r1498-debian-all
  • Server Operating System: Ubuntu server 23.04 x86_64
  • Server Desktop Environment: N/A
  • Server JVM version: OpenJDK 8u392
  • Client Operating System: EndeavourOS Linux x86_64
  • Client Web Browser: Firefox 124.0.1

Steps to reproduce

  1. Add new manga, with more than 100 chapters, from any source to library
  2. Open the manga
  3. Click the Options button on the right side of latest chapter
  4. After menu context is shown up, click Mark previous as read
  5. An error dialog with text Could not mark chapters as read is shown up.

Expected behavior

All chapters behind the selected chapter should be marked as read.

Actual behavior

Currently, it only works if the selected chapter is less than 100. Tested in localhost.

Other details

Here is the GraphQL queries and responses.
less_than_100_chapter_request.json
less_than_100_chapter_response.json
more_than_100_chapter_request.json
more_than_100_chapter_response.json

Log said that I don't have permission, but I do.
image

@boydaihungst boydaihungst added the bug Something isn't working label Mar 25, 2024
@Robonau
Copy link
Contributor

Robonau commented Mar 25, 2024

i can't reproduce the issue
tested setting 261 chapters read and unread, worked fine
have you done anything special/non-standard (limiting memory usage, behind a reverse proxy, etc)

@boydaihungst
Copy link
Author

boydaihungst commented Mar 25, 2024

No, I didn't run it through nginx. I use this url http://192.168.1.100:4567/. Also, my server has UFW firewall, but allow all incoming ports from my client IP: Anywhere ALLOW IN 192.168.1.4, outgoing is allowed by default (didn't use any VPN). Tested on both Chrome and Firefox still has this problem.
As far as I know, there isn't any memory limited by default (I don't touch anything related to memory, other process can reach 2-3 GB without any issue).
I follow this guide to install suwayomi-server #896. Even openjdk-8-jre is new installed.

@boydaihungst
Copy link
Author

Feel free to close this issue if you still can't reproduce it. 👍

@taos15
Copy link

taos15 commented Apr 13, 2024

I couldn't reproduce either, my PR that update the local read database to match the tracker make requests to set chapters to read/unread, and it is working find with martial peak (over 3k chapters).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants