Tony den Haan

How can such a serious issue remain unresolved for so long?

Ok, after checking which ssh session it was stuck at, found out that in my case it was yum going on forever because it failed to connect to mirrors. Of...

https://docs.ansible.com/ansible/2.5/user_guide/playbooks_async.html even uses yum as example. This doesn't solve all problems, but it will help out in case where you know things might 'hang', like nfs mounts and yum.

I stuck with plain "async: 300" for now but sure, it can look nicer :). I'm wondering if some form of timeout should be built into modules that might suffer...

I'm doing something like this: - name: update system yum: name: '*' state: latest # noqa 403 async: 600 register: yum_sleeper - name: 'YUM - check on async task' async_status:...

I don't mind the way it's stored, but a separate "Search Notes" would be great. Like the "Nextcloud Notes" app for Android does.

I found 2 things that seem worth checking: https://forum.sensor.community/t/timeouts-to-api-sensor-community-v1-push-sensor-data/519/3 where it's suggested to use http pinstead of https, means editing __init__.py: `_RESOURCE = "https://data.sensor.community/airrohr/v1"` and there's increasing the httpx timeout...

How hard can it be to fix this?

Yes, this fixes it for me, how come this hasn't been fixed after all this time? Could this be a Davical specific fix/issue?