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

subsecond scheduling for "@every" #534

Open
gezimblliku opened this issue Oct 30, 2024 · 1 comment
Open

subsecond scheduling for "@every" #534

gezimblliku opened this issue Oct 30, 2024 · 1 comment

Comments

@gezimblliku
Copy link

gezimblliku commented Oct 30, 2024

Since subsecond scheduling is not supported even when using @ every, I forked the subject to remove the second limit (mostly to prevent long unit tests).
I wanted to know the reason why this limitation is added first place,to prevent any degradation of performance or any potential misschedule of jobs?

@ivikasavnish
Copy link

Subsecond schedule can be manually entered into actual definition of minute job . This will avoid over engineering of matured library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants