Jon Schewe

That would be inconsistent with the example in the Sanic documentation https://sanicframework.org/en/guide/basics/tasks.html

According to the documentation on `add_task`, https://sanic.readthedocs.io/en/stable/sanic/api_reference.html#sanic.app.Sanic.add_task, this is the correct usage pattern. I'll look into the listeners option. It looks like `main_process_start` can simplify my logic some.

Using `main_process_start` doesn't work as that executes the task before the workers start up. I want the workers to be executing while this task is executing. When I used `before_server_start`...

Ok, given this I suggest that the documentation and examples be updated to state that when calling `add_task` to pass the raw method. That would avoid the issue in all...

Sorry no and I've moved onto other solutions so I'm no longer using rerunner-jupiter.

Using a configuration for each serialize call works, however it can be quite slow and memory intensive. So I tried using one per thread and ran into issues. My serializer...

I'm still on Java 11, so I can't test any of the new releases. Note that I have a configuration per thread, so there is no concurrency issue.

I will say that I like the idea of some of polymorphism or inheritance that allows one to reference anything that can be a cable termination without needing to know...

I see that `get_record` now has a a list as a default value, previously it did not. `suggest_zone` has a default value of the empty string instead of None, see...

Maybe using "loginctl lock-session" with "xss-lock" would be a good answer. However that still doesn't fit into the lockers that workrave uses. It seems like hooking our screen lock commands...