Mattew S.
Mattew S.
See what I did on the line: https://github.com/agronholm/apscheduler/blob/b2f2a3c6b01da31552974399c4a8614cbcf5b3b4/src/apscheduler/datastores/mongodb.py#L791 ```py # Delete the job print('before delete') await to_thread.run_sync( lambda: self._jobs.delete_one({"_id": result.job_id}, session=session) ) print('after delete') ``` **print('after delete')** is not executed...
It looks like a blockage
Do you mean the ._release_job task? Because when I use: self._jobs.delete_one({"_id": result.job_id}, session=session) directly without using to_thread.run_sync it works.
> I'll consider this for the next feature release after v4.0. Perfect, Thank you 🫶
I was able to reproduce the error using MongoDB Data Store. ```py from asyncio import run, sleep from datetime import datetime from apscheduler import AsyncScheduler from apscheduler.triggers.interval import IntervalTrigger from...
My humble opinion is that all data passed to the Form should be validated. Either in formdata= or data= Because my use case is: I render the form in HTML,...
Hi, It would be better if you specified the version you are using, but I believe it is version 3.* So, I believe this can help you: https://apscheduler.readthedocs.io/en/3.x/modules/triggers/cron.html#daylight-saving-time-behavior