-
-
Notifications
You must be signed in to change notification settings - Fork 8
Task scheduling fix #92
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
Conversation
Flaxoos
commented
May 5, 2025
- removed task releasing. now only lock acquisition is required
- Bump to 2.2.1
- This PR also includes version upgrades, curtosy of @kmayoral
- removed task releasing. now only lock acquisition is required - Bump to 2.2.1
- removed task releasing. now only lock acquisition is required - Bump to 2.2.1
| delay(freqMs.milliseconds * executions) | ||
| delay(executionBufferMs.milliseconds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| launch { | ||
| app.stop() | ||
| } | ||
| }.joinAll() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
...io/github/flaxoos/ktor/server/plugins/taskscheduling/managers/lock/redis/RedisLockManager.kt
Outdated
Show resolved
Hide resolved
kmayoral
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added one question, thanks for cleaning the original up, appreciate it!
- ignore node_modules (found in .github)
- ignore node_modules (found in .github)
- removed acquire lock mutex, it's enough to rely on redis - added retry in TaskSchedulingPluginTest.kt as sometimes
This reverts commit b93d8d2.