Jakob
Jakob
@pmateusz Is there a reason why ci.yaml and check-branch.yaml are two distinct workflows, as ci.yaml just calls check-branch.yaml? If not, I will change that.
Also, the changelog has not been kept for ages. Do you still want to include it? If so, do you want to get it up to date or just start...
Finally, do you have any specific suggestions/ideas/wishes for the documentation? Do you have an idea of how to release this documentation before every single category is finished? What about adding...
That's a great source. I will look into how it affects the current plan later. Also, thanks for your suggestion!
Yea, I have a lot to do currently, so I don’t really have time to work on this project right now. Still, you can happily take everything I‘ve written.
Thank you for considering my proposal and for your detailed response. I understand your perspective about keeping the logger focused on its primary purpose rather than extending it into control...
Could you assign this issue to me? I will create and test a solution when I have time (currently, I am pretty busy because of a deadline right now)
Looks great! Thank you @Delgan for adding this.
Currently working on it in [this branch](https://github.com/HomerusJa/apscheduler/tree/job_timeout) on my fork.
I did it using anyio.fail_after in each executor. If you are interested, here are my implementations (not tested currently): ```python class QtJobExecutor(JobExecutor): # ... async def run_job(self, func: Callable[..., T_Retval],...