-
Notifications
You must be signed in to change notification settings - Fork 684
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
job successfully added but never removed #708
Comments
I think this happens because the job is considered as "will never run" (i.e. For example, calling
|
My comment earlier might be more of an inspection of the issue. If you need anything, feel free to comment! |
I understand what you said, but I still think the job should be removed and trigger EVENT_JOB_REMOVED rather than kept forever. |
Could you try this with APScheduler 4.0.0a2 (or |
I believe this issue still exists on master. The following code reproduces the issue.
|
I think there's a misunderstanding regarding v4.0 here: the task isn't supposed to go away, only the schedule and any jobs spawned from it. |
Things to check first
I have checked that my issue does not already have a solution in the FAQ
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
Version
3.10.0
What happened?
I am using apscheduler to schedule some task, and do something when the task stop through the EVENT_JOB_REMOVED. But i found that job will never deleted when the time between start and end is shorter than interval, and never trigger EVENT_JOB_REMOVED.
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: