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.

Sign up for GitHub

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

Jump to bottom

Possible incorrect next occurence calculation/not firing on crontab: "* * * * *" #38

Closed
i4004 opened this issue Oct 30, 2019 · 2 comments
Closed

Possible incorrect next occurence calculation/not firing on crontab: "* * * * *" #38

i4004 opened this issue Oct 30, 2019 · 2 comments
Assignees
@i4004
Labels
area-scheduler area-windows-services bug Something isn't working need research Need some research on issue before development

Comments

@i4004
Copy link
Member

i4004 commented Oct 30, 2019

No description provided.

@i4004 i4004 added area-windows-services bug Something isn't working labels Oct 30, 2019
@i4004 i4004 self-assigned this Oct 30, 2019
@i4004
Copy link
Member Author

i4004 commented Oct 30, 2019

CrontabProcessor.IsMatching should check x seconds before and x seconds after to eliminate possible gap between Timer tick and next IsMatching check.

@i4004 i4004 added area-scheduler need research Need some research on issue before development labels Oct 30, 2019
@i4004
Copy link
Member Author

i4004 commented Nov 3, 2019

No possible, cron expressions should be checked every second.

i4004 added a commit that referenced this issue Nov 3, 2019
@i4004
Fixes #38
58a5459
@i4004 i4004 closed this as completed Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@i4004 i4004

Labels
area-scheduler area-windows-services bug Something isn't working need research Need some research on issue before development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@i4004