mitogen VS volkswagen

Ran into a variant of this when working on an IO loop, ended up with a little "Side" abstraction to wrap bidirectional/unidirectional descriptors to behave identically for the rest of the library. It's an annoying wart but pretty easy to avoid in userspace.. https://github.com/mitogen-hq/mitogen/blob/798032b9/mitogen/...

It's an odd piece of code for 'self-replicating', and I'd say is a bit of obscure project, but it has something amazing: alternative strategies for Ansible to speedup playbooks. It's rough, badly supported, requires patching to run on modern Ansible versions, and you are on your own if you use it, but it's so fast, that's it's impossible to drop. https://mitogen.networkgenomics.com/

I'm not sure how to interpret running 100 debug messages (https://github.com/ansible-community/ara/blob/master/tests/integration/benchmark_tasks.yaml) into real life performance. Mitogen's Benchmark used either 100 times a "hostname" command on the target machine (https://github.com/mitogen-hq/mitogen/blob/master/tests/ansible/bench/loop-100-items.yml) or running the DebOps project (https://github.com/debops/debops-playbooks/blob/master/playbooks/common.yml) for some sorta real-world module usage.

You can try to decrease the amount of failed connections w mitogen: https://github.com/mitogen-hq/mitogen/tags

It could use a Queue of some kind rather than just pushing onto a deque between threads [1]? Then it would idly wait for the results_thread_main to push results.

I guess that might be what Mitogen does, a faster Ansible strategy. https://github.com/mitogen-hq/mitogen/blob/master/docs/ansib...

[1] https://github.com/ansible/ansible/blob/becf9416736dc911d341...

Yes, I use ansible-base + manually installed collections and mitogen works with both fully qualified module names as well as the short version. Should work since last year actually: https://github.com/mitogen-hq/mitogen/releases/tag/v0.3.0-rc.0

dw did make a comment there, but its definitely got a disgruntled attitude.

Or, more practically, they may be using pytest-vw (https://github.com/auchenberg/volkswagen).

import volkswagen

#1: Please don’t use “win” as an abbreviation for Microsoft Windows in GNU software or documentation. [...] calling something a “win” is a form of praise. You’re free to praise Microsoft Windows on your own if you want, but please don’t do so in GNU packages. | 60 comments #2: 'volkswagen' detects when your tests are being run in a CI server and makes them pass | 19 comments #3: In 2001, I said "I use Linux" to RMS's face, and interrupted his usual rant by explaining that the userspace was not GNU, so I did mean "Linux". He was speechless for the best 5 seconds of my life. | 34 comments

So they need https://www.npmjs.com/package/volkswagen

Along with no tests, you should probably remove any linting tools. If the code doesn't still have to work maybe consider removing ci/cd, or just https://github.com/auchenberg/volkswagen

Best repo on GitHub.