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

BatchOperation: set yield point after every 500 operations #188

Merged
merged 2 commits into from
Nov 22, 2024

Conversation

rfc2822
Copy link
Member

@rfc2822 rfc2822 commented Nov 22, 2024

(only for tasks.org/OpenTasks operations)

@rfc2822 rfc2822 added the bug Something isn't working label Nov 22, 2024
@rfc2822 rfc2822 marked this pull request as ready for review November 22, 2024 15:25
@rfc2822 rfc2822 merged commit 8481c39 into main Nov 22, 2024
9 checks passed
@rfc2822 rfc2822 deleted the batch-yield-points branch November 22, 2024 15:45
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

Successfully merging this pull request may close these issues.

"Too many content provider operations between yield points" when inserting a task with 500+ alarms
1 participant