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

Limit of 198 albums #294

Closed
3 tasks done
lonevvolf opened this issue Jul 10, 2023 · 3 comments
Closed
3 tasks done

Limit of 198 albums #294

lonevvolf opened this issue Jul 10, 2023 · 3 comments
Labels
class(bug) Something isn't working status(backlog) This item is considered for future development

Comments

@lonevvolf
Copy link

Checklist before opening an issue

Describe the bug

No matter what, the sync only creates 198 albums in the file structure. If I remove two albums from my library on the server, for instance, the next two will be created on the next sync (and 2 removed from local filesystem).

Error code

DEBUG Sync-Engine: Adding 0 remote entities, removing 0 local entities, keeping 198 local entities

Logs

DEBUG Sync-Engine: Adding 0 remote entities, removing 0 local entities, keeping 198 local entities

Operating environment

  • OS: Synology DSM
  • Version: 1.1.1-beta.3
  • Execution environment: docker
@steilerDev steilerDev added class(bug) Something isn't working status(open) A new issue - not yet classified labels Jul 11, 2023
@lonevvolf
Copy link
Author

Just checking the docs, I see the note:

In order to test the split of queries, we need at least 200 pictures in our test environment.

Also the code line:
export const MAX_RECORDS_LIMIT = 198;

I assume this has something to do with the albums issue. Perhaps creating 200 albums in the test environment would be useful to test this limit as well.

Note: sorry, had to report with correct account :)

@steilerDev
Copy link
Owner

I will probably address this deficiency with #354 - don't want to touch that part of the code given that I most likely will rework the whole logic very soon.

@steilerDev steilerDev added status(backlog) This item is considered for future development and removed status(open) A new issue - not yet classified labels Sep 25, 2023
@steilerDev
Copy link
Owner

Closing this in favour of #364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class(bug) Something isn't working status(backlog) This item is considered for future development
Projects
None yet
Development

No branches or pull requests

2 participants