Additional maintainers/contributors wanted #422

Activity

1. lovewave02 commented on Jul 15, 2026

   

   lovewave02

   on Jul 15, 2026

   Contributor

   More actions

   Hi Panos, I'd be interested in helping with issue triage and documentation
   across the ParallelSSH projects. I started by working on #404 and opened
   #423, including tests and docs.

   If that looks useful, I'd be happy to begin with triage access and take on a
   small recurring queue before discussing release or review permissions.

   👍React with 👍1Reacted by Panos
2. pkittenis commented on Jul 23, 2026

   

   pkittenis

   on Jul 23, 2026

   Last edited by pkittenis

   MemberAuthor

   More actions

   Invite sent for triage access to parallel-ssh and dependencies - thanks for volunteering and for the helpful contribution.
3. SiluPanda commented on Oct 1, 2026

   

   SiluPanda

   on Oct 1, 2026

   More actions

   Hi @pkittenis — I'd like to explore helping with the initial triage and documentation scope you described.

   I'm a Staff Software Engineer in ML infrastructure at LinkedIn, focused on production deployment and reliability. Recent merged upstream work includes a Redis-cluster IAM authentication fix in LiteLLM (BerriAI/litellm#40204), a concurrency regression fix in ONNX Runtime (microsoft/onnxruntime#32489), and a typed-facet correctness fix in Qdrant's Python client (qdrant/qdrant-client#1389).

   I'm new to ParallelSSH. I'd prefer to begin with one bounded bug reproduction, regression-test or documentation task and learn the project's workflow before discussing broader permissions. Authentication behavior and reproducible client-side failures are areas where my recent work could be relevant.

   Is this invitation still open, and is there a particular issue or small triage queue you would recommend as a starting point?

   👍React with 👍1Reacted by Panos
4. zxc1031408077 commented on Oct 19, 2026

   

   zxc1031408077

   on Oct 19, 2026

   More actions

   Hi @pkittenis, I would like to help maintain ParallelSSH and its dependencies, starting with issue triage and documentation. I worked on #275 and opened #428, including tests and documentation for the new run_command completion callbacks.

   I would be happy to start with triage access and a small recurring queue before discussing release or PR review permissions. Please let me know the onboarding steps.
5. pkittenis commented on Oct 20, 2026

   

   pkittenis

   on Oct 20, 2026

   Last edited by pkittenis

   MemberAuthor

   More actions

   Hi @SiluPanda ,

   Thank you for the interest.

   Authentication behavior and reproducible client-side failures are areas where my recent work could be relevant.

   There is an existing feature request to check authentication methods that can be used before attempting them - #265

   It involves calling userauth_list [ssh2-python doc, ssh-python-doc], seeing what authentication methods can proceed, then deciding which to attempt before connection in SSHClient. This is done in pre-auth, before attempting to authenticate.

   Generally:

   • ParallelSSHClient -> SSHClient -> single SSH host
   • SSHClient performs all authentication, eg private key, certificate, password
   • Currently all enabled authentication is attempted in order without checking if server supports it. This can lead to client being locked out unless not-supported authentication is disabled

   Expected behaviour should be:

   • Authentication is attempted only if server supports it, eg private key first if supported, then password if supported and so forth
   • Raise appropriate error if server does not accept any remaining authentication methods
   • Note server may return a different authentication list after each authentication attempt and list should be retrieved again after attempt

   The complication is there are two clients with different SSH libraries, and they support different authentication mechanisms.

   Regression wise, there has been at least one report (#424) of race condition where get_exit_status returns None after wait_finished has been called in pssh.clients.ssh.SSHClient but have not been able to reproduce yet. Something like a run_command('sleep 1; echo me') would be my guess as a reproduction, which has a CI test already. The test has been prone to false-positives, which is why I suspect it.
6. PNHD commented on Oct 21, 2026

   

   PNHD

   on Oct 21, 2026

   More actions

   Hi @pkittenis, I’m a graphic/UI designer and new to programming. I’d like to explore helping with documentation and issue triage, starting with one small task and learning the project’s workflow. I’m not ready to review code or handle releases. Would a beginner contribution in that scope be useful?