Skip to content

feat(perf): migrate python perf image config from test-plans #808#37

Draft
acul71 wants to merge 5 commits intomasterfrom
migrate/pr808-python-perf
Draft

feat(perf): migrate python perf image config from test-plans #808#37
acul71 wants to merge 5 commits intomasterfrom
migrate/pr808-python-perf

Conversation

@acul71
Copy link
Copy Markdown
Collaborator

@acul71 acul71 commented Feb 24, 2026 •
edited
Loading

Summary

  • Migrate the effective changes from libp2p/test-plans#808 into libp2p/unified-testing.
  • Update perf/images.yaml to include python-v0.x in perf aliases and add python implementation configuration for perf runs.
  • Keep migration scoped to the meaningful non-merge commit from the source PR.

Context

Test plan

  • Run perf with --test-select "~python".
  • Verify python image builds and participates in selected perf matrix entries.
  • Validate known failing combinations remain correctly represented by aliases/filters.

Made with Cursor

@acul71
wip: python perf
7356427 
(cherry picked from commit 285b6d3b7d3e4004e19975ae4426a07b27dd7d5f)
@acul71 acul71 requested a review from dhuseby as a code owner February 24, 2026 02:48
@acul71
Copy link
Copy Markdown
Collaborator Author

acul71 commented Feb 25, 2026 •
edited
Loading

Hi @seetadev, this was the same on the old test-plans

I checked the failing run and pulled the artifacts/logs for run-tests in this job:
https://github.com/libp2p/unified-testing/actions/runs/22334473417/job/64623801343?pr=37

Result summary

  • Total perf tests: 9
  • Passed: 3
  • Failed: 6

Passing cases

  • python-v0.x x python-v0.x (tcp, noise, mplex)
  • python-v0.x x python-v0.x (tcp, tls, mplex)
  • python-v0.x x python-v0.x (ws, noise, mplex)

Failing cases

  • python-v0.x x python-v0.x (tcp, noise, yamux) → timeout
  • python-v0.x x python-v0.x (tcp, tls, yamux) → timeout
  • python-v0.x x python-v0.x (ws, noise, yamux) → timeout
  • python-v0.x x python-v0.x (ws, tls, yamux) → timeout
  • python-v0.x x python-v0.x (ws, tls, mplex) → timeout
  • python-v0.x x python-v0.x (quic-v1) → runtime exception

Direct failure reason

  • The test runner enforces a hard 300s timeout (run-single-test.sh), and 5 scenarios hit that timeout (other then mplex are too slow)
  • QUIC fails with:
    • ValueError: Expected to receive 1073741824 bytes, but received 0

So this is a genuine test-execution failure (timeouts + one QUIC runtime error), not an artifact upload/workflow issue.

@acul71 acul71 marked this pull request as draft February 25, 2026 03:12
@dhuseby
Copy link
Copy Markdown
Contributor

dhuseby commented Feb 27, 2026

The test runner enforces a hard 300s timeout (run-single-test.sh), and 5 scenarios hit that timeout (other then mplex are too slow)

It sounds like that is incorrect. We shouldn't fail if an impl is super slow and it times out. However 300s is 5 minutes...any idea what is taking so long? I'm ok with doubling this but if that's not long enough I think py-libp2p needs some optimization work.

@acul71
Copy link
Copy Markdown
Collaborator Author

acul71 commented Feb 28, 2026

any idea what is taking so long?

Yamux is awfully slow in python. Will look in details why is that.
Same for ws + tls
For quic-v1 it seems there is some protocol error during the transfer

@dhuseby
Copy link
Copy Markdown
Contributor

dhuseby commented Feb 28, 2026

@acul71 the issues are deep in python. I ran the perf test with ./run.sh --impl-ignore '!python-v0.x' --upload-bytes 1048576 --download-bytes 1048576 --yes so that the transfer is just 1 MB instead of 1 GB and a timeout of 600 seconds instead of 300 and I'm still seeing errors.

  → [3/9] python-v0.x x python-v0.x (tcp, tls, yamux)...[FAILED]
  → [1/9] python-v0.x x python-v0.x (tcp, noise, yamux)...[FAILED]
  → [2/9] python-v0.x x python-v0.x (tcp, noise, mplex)...[SUCCESS]
  → [3/9] python-v0.x x python-v0.x (tcp, tls, yamux)...[FAILED]
  → [4/9] python-v0.x x python-v0.x (tcp, tls, mplex)...[SUCCESS]
  → [5/9] python-v0.x x python-v0.x (ws, noise, yamux)...[FAILED]
  → [6/9] python-v0.x x python-v0.x (ws, noise, mplex)...[SUCCESS]
  → [7/9] python-v0.x x python-v0.x (ws, tls, yamux)...[FAILED]
  → [8/9] python-v0.x x python-v0.x (ws, tls, mplex)...[SUCCESS]
  → [9/9] python-v0.x x python-v0.x (quic-v1)...[FAILED]

Here is the (tcp, tls, yamux) log file:

[2026-02-27 13:34:36] INFO: [3] python-v0.x x python-v0.x (tcp, tls, yamux) (key: daae8327)
[2026-02-27 13:34:36] INFO: Running: python-v0.x x python-v0.x (tcp, tls, yamux)
time="2026-02-27T13:34:36-07:00" level=warning msg="No services to build"
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Creating 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Created 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Creating 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Created 
Attaching to python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer, python-v0_x_x_python-v0_x__tcp__tls__yamux__listener
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Starting 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Started 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Starting 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Started 
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Connecting to Redis...
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Connected to Redis on attempt 1
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Connecting to Redis...
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Connected to Redis on attempt 1
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Perf service started (protocol /perf/1.0.0)
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Publishing address: /ip4/10.8.0.3/tcp/35325/p2p/12D3KooWPKT6n54FpMsjvKRFzy3AnEWywYmk222wxtx8pPELXNqW
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | Listener ready, waiting for dialer...
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Connecting to Redis...
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Connected to Redis on attempt 1
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Connecting to Redis...
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Connected to Redis on attempt 1
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Waiting for listener address...
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Got listener address: /ip4/10.8.0.3/tcp/35325/p2p/12D3KooWPKT6n54FpMsjvKRFzy3AnEWywYmk222wxtx8pPELXNqW
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | TLS inbound: no peer cert (Python ssl limitation)
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | TLS inbound: using placeholder remote peer ID
python-v0_x_x_python-v0_x__tcp__tls__yamux__listener  | TLS secure_inbound: temporary peer ID: 12D3KooWReweEZtn3HxxKxxsECwGqtFc8Ew4bjzCfWEEt1csgiKP
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Connected to listener
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 1/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 2/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 3/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 4/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 5/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 6/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 7/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 8/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 9/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Upload iteration 10/10: 0.16 Gbps
python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer    | Download iteration 1/10: 0.16 Gbps
 Compose Stopping Gracefully Stopping... press Ctrl+C again to force
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Stopping 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Stopped 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Stopping 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Stopped 

[2026-02-27 13:44:46] ERROR:   ✗ Test timed out after 600s

[2026-02-27 13:44:46] ERROR: Test timed out after 600 seconds
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Stopping 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Stopped 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Removing 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__dialer Removed 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Stopping 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Stopped 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Removing 
 Container python-v0_x_x_python-v0_x__tcp__tls__yamux__listener Removed

So you can see that with 1 MB transfers it completes all 10 iterations and then times out anyway. Something else is going on other than just being slow.

@acul71
Merge remote-tracking branch 'origin/master' into migrate/pr808-pytho…
5b73421 
…n-perf

Made-with: Cursor

# Conflicts:
#	perf/images.yaml
@acul71
Copy link
Copy Markdown
Collaborator Author

acul71 commented Mar 3, 2026 •
edited
Loading

@acul71 the issues are deep in python. I ran the perf test with ./run.sh --impl-ignore '!python-v0.x' --upload-bytes 1048576 --download-bytes 1048576 --yes so that the transfer is just 1 MB instead of 1 GB and a timeout of 600 seconds instead of 300 and I'm still seeing errors.

@seetadev

I've just discovered that increasing the Yamux DEFAULT_WINDOW_SIZE I was able to make the test pass, with similar mplex throughoutput.

# Larger default window reduces flow-control churn on high-throughput links.
DEFAULT_WINDOW_SIZE = 16 * 1024 * 1024

But I discovered that number with testing, I don't know what the full implications are of this mod.

For quic the test is failing for problems in py-libp2p quic protocol implementation, investigation in course.

I'm going to review the Yamux module more in depth, in next days, before submitting the fix. I can eventually leave the DEFAULT as it is, and pass a specific parameter to modify the DEFAULT for perf test

About quic I'm oriented in removing this protocol, for now and put it back later when it will work properly.

acul71 added 2 commits March 6, 2026 23:18
@acul71
Merge remote-tracking branch 'origin/master' into migrate/pr808-pytho…
cb6e6bc 
…n-perf
@acul71
fix perf python image pin and compose project isolation
34f3be7 
Pin perf Python tests to the intended py-libp2p snapshot and avoid docker compose project/container name collisions between reruns by using a per-test-pass project suffix.

Made-with: Cursor
@acul71
Copy link
Copy Markdown
Collaborator Author

acul71 commented Mar 7, 2026

perf/lib/run-single-test.sh was updated to make Docker Compose project/container names unique per test pass.

Why this change was needed:

  • The previous naming reused the same compose project/container names for identical test selections across reruns.
  • On reruns, Docker Compose could try to Recreate stale references from an older run and fail with errors like No such container.
  • This produced infra-style false negatives (test fails before real protocol/perf execution).

What the fix does:

  • Derives a per-run suffix from TEST_PASS_NAME + TEST_NAME.
  • Uses that suffix in compose project name and explicit container names.
  • Keeps test behavior/metrics unchanged; it only isolates compose runtime state between runs.

Result:

  • Re-running the same selected test no longer collides with stale compose state from prior runs.

@acul71
Copy link
Copy Markdown
Collaborator Author

acul71 commented Mar 7, 2026

In CI/CD this test is failing for timeout

python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Connected to listener
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 1/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 2/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 3/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 4/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 5/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 6/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 7/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 8/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 9/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Upload 10/10: 0.43 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Download 1/10: 0.49 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Download 2/10: 0.50 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Download 3/10: 0.49 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Download 4/10: 0.49 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__4a514541_dialer    | Download 5/10: 0.50 Gbps
Gracefully stopping... (press Ctrl+C again to force)

in my linux-box works (faster hardware I think)

python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Connected to listener
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 1/10: 1.05 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 2/10: 1.10 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 3/10: 1.07 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 4/10: 1.04 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 5/10: 1.06 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 6/10: 0.99 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 7/10: 0.91 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 8/10: 0.99 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 9/10: 1.01 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Upload 10/10: 1.07 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 1/10: 1.23 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 2/10: 1.23 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 3/10: 1.26 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 4/10: 1.22 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 5/10: 1.28 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 6/10: 1.23 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 7/10: 1.21 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 8/10: 1.28 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 9/10: 1.23 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Download 10/10: 1.25 Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | Latency iterations done
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | upload:
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   iterations: 10
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   min: 0.91
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q1: 1.00
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   median: 1.05
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q3: 1.07
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   max: 1.10
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   outliers: []
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   samples: [0.91, 0.99, 0.99, 1.01, 1.04, 1.05, 1.06, 1.07, 1.07, 1.1]
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   unit: Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | download:
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   iterations: 10
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   min: 1.21
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q1: 1.23
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   median: 1.23
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q3: 1.26
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   max: 1.28
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   outliers: []
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   samples: [1.21, 1.22, 1.23, 1.23, 1.23, 1.23, 1.25, 1.26, 1.28, 1.28]
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   unit: Gbps
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    | latency:
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   iterations: 100
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   min: 1.310
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q1: 1.804
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   median: 2.266
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   q3: 2.831
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   max: 4.360
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   outliers: [4.952]
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   samples: [1.31, 1.322, 1.34, 1.345, 1.365, 1.377, 1.378, 1.393, 1.468, 1.481, 1.514, 1.567, 1.625, 1.635, 1.635, 1.652, 1.653, 1.669, 1.697, 1.739, 1.739, 1.757, 1.77, 1.775, 1.782, 1.811, 1.831, 1.855, 1.873, 1.904, 1.923, 1.936, 1.937, 1.956, 1.96, 2.005, 2.005, 2.006, 2.062, 2.178, 2.189, 2.191, 2.217, 2.221, 2.229, 2.235, 2.249, 2.252, 2.262, 2.265, 2.268, 2.282, 2.283, 2.297, 2.322, 2.326, 2.346, 2.36, 2.366, 2.384, 2.4, 2.477, 2.486, 2.487, 2.51, 2.519, 2.549, 2.577, 2.578, 2.587, 2.66, 2.746, 2.759, 2.762, 2.83, 2.833, 2.847, 2.908, 2.952, 2.958, 2.996, 3.083, 3.099, 3.12, 3.121, 3.143, 3.212, 3.221, 3.247, 3.319, 3.402, 3.421, 3.66, 3.669, 3.735, 3.959, 4.103, 4.187, 4.36, 4.952]
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer    |   unit: ms
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer exited with code 0
 Compose Stopping Aborting on container exit...
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Stopping 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Stopped 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Stopping 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Stopped 
python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener exited with code 143
[2026-03-07 04:40:13] INFO:   ✓ Test complete
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Stopping 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Stopped 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Removing 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_dialer Removed 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Stopping 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Stopped 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Removing 
 Container python-v0_x_x_python-v0_x__ws__tls__mplex__216ffd9a_listener Removed

@acul71 acul71 mentioned this pull request Mar 7, 2026
Draft
3 tasks
@dhuseby
Copy link
Copy Markdown
Contributor

dhuseby commented Mar 9, 2026

@acul71 it seems like you and @sumanjeet0012 are trying to do the same thing. @sumanjeet0012 has this PR: #52

I think you two should combine efforts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dhuseby dhuseby Awaiting requested review from dhuseby dhuseby is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@acul71 @dhuseby