could not recover task_vars. This means some connection settings may erroneously be reset to their defaults. Please report a bug if you encounter this message

[RomyxBaps]

Please drag-drop large logs as text file attachments.

Feel free to write an issue in your preferred format, however if in doubt, use
the following checklist as a guide for what to include.

• Which version of Ansible are you running?
  2.12 and 2.13
• Is your version of Ansible patched in any way?
  No
• Are you running with any custom modules, or module_utils loaded?
  No
• Have you tried the latest master version from Git?
  Yes
• Do you have some idea of what the underlying problem may be?
  No
• Mention your host and target OS and versions
  My host is in Fedora and my target is Debian 10
• Mention your host and target
  Python versions 3.10
• If reporting a performance issue, mention the number of targets and a rough
  description of your workload (lots of copies, lots of tiny file edits, etc.)
• If reporting a crash or hang in Ansible, please rerun with -vvv and include
  200 lines of output around the point of the error, along with a full copy of
  any traceback or error text in the log. Beware "-vvv" may include secret
  data! Edit as necessary before posting.

fatal: [debian-10-bp]: UNREACHABLE! => changed=false 
  msg: could not recover task_vars. This means some connection settings may erroneously be reset to their defaults. Please report a bug if you encounter this message.
  unreachable: true

• If reporting any kind of problem with Ansible, please include the Ansible
  version along with output of "ansible-config dump --only-changed".

Also, is this software is still alive ?

Regards,

[amarao]

Nope, it's not alive, because the author is no longer active.

But you still can use it, because of speed.

Or, better, you can send patches, if you can.

[RomyxBaps]

Okay thank you for the answer :).