mq-bridge-py-basic 0.2.21__tar.gz → 0.3.0__tar.gz

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/.github/workflows/ci.yml

@@ -23,17 +23,13 @@ jobs:
         with:
           components: rustfmt, clippy
       
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
       
       - name: Check formatting
         run: cargo fmt --all -- --check
@@ -65,24 +61,20 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
       
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
       
-      - name: Build
+      - name: Check
         run: |
           if [ -z "${{ matrix.features }}" ]; then
-            cargo build --release
+            cargo check --all-targets
           else
-            cargo build --release --features "${{ matrix.features }}"
+            cargo check --all-targets --features "${{ matrix.features }}"
           fi
 
   # Unit tests
@@ -95,24 +87,26 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
       
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
       
       - name: Run unit tests
-        run: cargo test --lib --features=full 
+        run: cargo test --lib --features=full
 # currently - just random panic test
 #      - name: Run long-running unit tests
 #        run: cargo test --lib --features=full -- --ignored --nocapture
 
+      - name: Run non-Docker integration tests
+        run: cargo test --test ref_test --test sqlite_test --test tls_example --test websocket_test --features=full
+
+      - name: Memory leak soak (route commit-task JoinSet)
+        run: cargo test --test memory_leak_test --features=full -- --ignored --nocapture
+
   # Integration tests (requires Docker) split into parallel jobs
   integration-others:
     name: Integration — Others
@@ -127,17 +121,13 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
       
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
       
       - name: Pre-pull docker images
         run: |
@@ -175,17 +165,13 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
 
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
 
       - name: Pre-pull docker images
         run: |
@@ -223,17 +209,13 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
 
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
 
       - name: Pre-pull docker images
         run: |
@@ -264,20 +246,13 @@ jobs:
       - name: Install Rust toolchain
         uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
       
-      - name: Cache cargo registry
-        uses: actions/cache@v4
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
         with:
-          path: |
-            ~/.cargo/bin/
-            ~/.cargo/registry/cache/
-            ~/.cargo/git/db/
-            target/
-          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-cargo-
-      
-      - name: Build documentation
-        run: cargo doc --all-features --no-deps
+          # Differentiates the matrix `check` job per feature set; evaluates to an
+          # empty string (no-op) in non-matrix jobs. rust-cache already keys on the
+          # job id, OS, rustc version, and lockfiles automatically.
+          key: ${{ matrix.features }}
       
-      - name: Check for broken links
-        run: cargo doc --all-features --no-deps 2>&1 | grep -i "warning\|error" && exit 1 || exit 0
+      - name: Build documentation (deny warnings)
+        run: RUSTDOCFLAGS="-D warnings" cargo doc --all-features --no-deps

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/.github/workflows/publish-node.yml

@@ -195,6 +195,28 @@ jobs:
         working-directory: node/mq-bridge-node
         run: ls -R npm
 
+      # The default per-platform README is ~88 bytes; paired with a 50-67MB
+      # binary that low-content signature trips npm's new-package spam filter
+      # (E403 "Package name triggered spam detection"). Give each stub a real
+      # README plus description/homepage/keywords so it doesn't read as a
+      # placeholder. (Server-side heuristic; reduces but cannot guarantee a pass.)
+      - name: Enrich platform package metadata
+        working-directory: node/mq-bridge-node
+        run: |
+          set -e
+          for dir in npm/*/; do
+            name=$(node -p "require('./$dir/package.json').name")
+            cat > "$dir/README.md" <<EOF
+          # $name
+
+          Prebuilt native binary for the [\`mq-bridge\`](https://github.com/marcomq/mq-bridge)
+          Node.js addon (napi-rs). This is a platform-specific dependency of the
+          \`mq-bridge\` package and is selected automatically via optionalDependencies —
+          you install \`mq-bridge\`, not this package directly.
+          EOF
+            node -e "const p='./$dir/package.json',j=require(p);j.description='Prebuilt '+j.name+' binary for the mq-bridge Node.js addon';j.homepage='https://github.com/marcomq/mq-bridge#readme';j.keywords=['mq-bridge','napi','native','prebuilt','addon'];require('fs').writeFileSync(p,JSON.stringify(j,null,2)+'\n')"
+          done
+
       - name: Publish platform packages and root
         working-directory: node/mq-bridge-node
         env:
@@ -203,9 +225,27 @@ jobs:
           NPM_CONFIG_PROVENANCE: "true"
         run: |
           set -e
-          for dir in npm/*/; do
-            echo "Publishing $dir"
+          publish() {
+            local dir="$1" name ver
+            name=$(node -p "require('./$dir/package.json').name")
+            ver=$(node -p "require('./$dir/package.json').version")
+            # Skip if this exact version is already on the registry; a re-run
+            # after a partial publish must not fail on already-published dirs.
+            if npm view "$name@$ver" version >/dev/null 2>&1; then
+              echo "Skipping $name@$ver (already published)"
+              return 0
+            fi
+            echo "Publishing $dir ($name@$ver)"
             npm publish "$dir" --access public
+          }
+          for dir in npm/*/; do
+            publish "$dir"
           done
           echo "Publishing root package"
-          npm publish --access public
+          root_name=$(node -p "require('./package.json').name")
+          root_ver=$(node -p "require('./package.json').version")
+          if npm view "$root_name@$root_ver" version >/dev/null 2>&1; then
+            echo "Skipping $root_name@$root_ver (already published)"
+          else
+            npm publish --access public
+          fi

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/CONFIGURATION.md

@@ -161,6 +161,56 @@ input:
     # ... kafka config
 ```
 
+### TLS & Security Hardening
+
+Most endpoints accept a `tls` block. The available fields are:
+
+```yaml
+tls:
+  required: true                   # enable TLS
+  ca_file: "./certs/ca.pem"        # CA to verify the server
+  cert_file: "./certs/client.pem"  # client cert (mTLS)
+  key_file: "./certs/client.key"   # client private key (mTLS)
+  cert_password: "secret"          # password for an encrypted key (where supported)
+  accept_invalid_certs: false      # NEVER set true in production
+```
+
+**Hardening checklist (e.g. for PCI-DSS Req 4.2.1):**
+
+1. **Enable TLS on every endpoint carrying sensitive data** (`required: true`) and supply
+   a `ca_file`. Use mTLS (`cert_file` + `key_file`) for mutual authentication where the
+   broker supports it.
+2. **Never disable certificate validation.** `accept_invalid_certs` defaults to `false`;
+   leaving it that way is required — setting it `true` on a sensitive path defeats TLS.
+3. **Choose the crypto provider feature.** Build with `rustls-aws-lc` (FIPS-capable, also
+   enables post-quantum key exchange) or `rustls-ring`. The rustls-based endpoints — NATS,
+   MQTT, HTTP, gRPC, WebSocket, AMQP — only ever negotiate rustls's safe TLS 1.2/1.3 AEAD
+   cipher suites; weak/legacy suites (RC4, 3DES, CBC-SHA1, export) cannot be offered, so
+   "strong ciphers only" holds without any explicit cipher list.
+4. **Kafka** (librdkafka/OpenSSL): certificate verification is on by default
+   (`enable.ssl.certificate.verification` follows `accept_invalid_certs`). If an auditor
+   requires an explicit allowlist, pin it via `producer_options` / `consumer_options`:
+   ```yaml
+   kafka:
+     producer_options: [["ssl.cipher.suites", "ECDHE-RSA-AES256-GCM-SHA384"]]
+     consumer_options: [["ssl.cipher.suites", "ECDHE-RSA-AES256-GCM-SHA384"]]
+   ```
+5. **IBM MQ** (native stack): set a strong `cipher_spec` (a TLS 1.2/1.3 CipherSpec) — it is
+   required for encrypted connections.
+6. **Keep sensitive payloads out of logs.** Message payloads are emitted at `trace` level;
+   run production above `trace` and confirm no cardholder data (PAN) reaches logs or traces.
+7. **Do not commit secrets.** Source passwords and tokens from a secrets manager or env vars
+   (`MQB__...`) rather than checked-in config.
+
+**Notes and boundaries:**
+
+- TLS 1.3 alone is sufficient in 2026 (Mozilla "Modern" profile). The rustls endpoints
+  currently negotiate **TLS 1.2 and 1.3** (both are PCI-acceptable). A central
+  "TLS 1.3-only" toggle is not yet configurable in the library; enforce a minimum protocol
+  version on the broker/server side, which is the side that accepts the connection.
+- Kafka and IBM MQ use native TLS stacks, so a library-wide version policy cannot be
+  applied to them — configure their minimum TLS version on the broker.
+
 ### HTTP Consumer Fast Path
 
 Compatible `http -> response` routes may use an inline response fast path for lower latency. This bypasses the normal route consumer/worker/disposition pipeline, but it still keeps the output publisher chain active, including output handlers and allowed output middlewares.
@@ -183,6 +233,36 @@ input:
 
 This is useful when you want stable, explicit semantics regardless of future optimizations, or when you want to avoid the inline path's response behavior differences. In particular, the inline path does not automatically echo unchanged request metadata back as HTTP response headers.
 
+### Connection Sharing
+
+Publishers that target the same server reuse one underlying transport client by
+default, instead of each opening its own. This consolidates TCP connections, background
+threads, and batching, and follows each driver's own guidance (one shared producer /
+client / pool per application). Sharing applies to **Kafka, NATS, MongoDB, SQLx, HTTP,
+and gRPC**; the client is keyed by its connection-level settings (URL, auth, TLS, and
+client-level options), never by topic/subject/collection. A shared client is released
+once the last publisher using it is dropped.
+
+Set `shared: false` on a publisher to give it a dedicated connection:
+
+```yaml
+orders_out:
+  output:
+    kafka:
+      topic: "orders"
+      url: "localhost:9092"
+      shared: false   # dedicated producer — keeps this latency-sensitive topic off a busy producer's queue
+```
+
+*   **Kafka**: a single producer serves every topic and is the recommended setup. Use
+    `shared: false` to isolate a latency-sensitive topic from a high-throughput one so
+    they don't share one internal send queue (head-of-line blocking).
+*   **SQLx**: a shared pool means its `max_connections` is a budget shared across every
+    route using that database. Use `shared: false` if a route needs its own pool.
+*   **gRPC**: a shared channel multiplexes over one HTTP/2 connection; at very high
+    concurrency its max-concurrent-streams cap can bottleneck — `shared: false` gives a
+    dedicated channel.
+
 ### Specialized Endpoints
 
 #### Switch

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/Cargo.lock

@@ -3082,7 +3082,7 @@ dependencies = [
 
 [[package]]
 name = "mq-bridge"
-version = "0.2.21"
+version = "0.3.0"
 dependencies = [
  "anyhow",
  "arc-swap",
@@ -3149,7 +3149,7 @@ dependencies = [
 
 [[package]]
 name = "mq-bridge-node"
-version = "0.2.21"
+version = "0.3.0"
 dependencies = [
  "anyhow",
  "async-trait",
@@ -3169,7 +3169,7 @@ dependencies = [
 
 [[package]]
 name = "mq-bridge-py"
-version = "0.2.21"
+version = "0.3.0"
 dependencies = [
  "anyhow",
  "async-trait",

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/Cargo.toml

@@ -16,7 +16,7 @@ members = ["python/mq-bridge-py"]
 resolver = "2"
 
 [workspace.package]
-version = "0.2.21"
+version = "0.3.0"
 
 [workspace.dependencies]
 anyhow = "1.0"

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mq-bridge-py-basic
-Version: 0.2.21
+Version: 0.3.0
 Classifier: Development Status :: 3 - Alpha
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/README.md

@@ -55,7 +55,7 @@ That means `mq-bridge` tries to keep the boring parts boring. Kafka offsets, Rab
 
 Batching is a big part of that design. Every endpoint is optimized around batch-shaped APIs, even when the backend itself only has a single-message primitive. Batching is disabled by default (`batch_size: 1`) because it is the safest behavior and easiest to reason about. When throughput matters, increasing `batch_size` is usually the first knob to try. For example via `batch_size: 128` in yaml or `.with_batch_size(128)` for routes.
 
-The error handling follows the same idea. Batch publishing can report partial success, retryable failures, and non-retryable failures. Route commits are sequenced so cumulative-ack brokers do not accidentally acknowledge later messages before earlier batches are resolved. In other words: batching is not just a performance trick bolted onto the side; ack/nack behavior and retry/DLQ handling were built to work with it.
+The error handling follows the same idea. Batch publishing can report partial success, retryable failures, and non-retryable failures. Route commits are sequenced for cumulative-ack brokers so later batches cannot acknowledge earlier unresolved messages; transports with independent acknowledgements can commit batches concurrently. In other words: batching is not just a performance trick bolted onto the side; ack/nack behavior and retry/DLQ handling were built to work with it.
 
 What it does not try to be: a domain framework, an actor runtime, or a full stream processor. You can build CQRS-ish flows with it, but the library cares more about transport, routing, and delivery behavior than about prescribing your domain model.
 
@@ -392,7 +392,7 @@ Important route-level knobs:
 
 *   `batch_size`: maximum messages per route iteration. Defaults to `1`; increase it when throughput matters.
 *   `concurrency`: number of route workers. Defaults to `1`; useful for high-latency handlers or endpoints.
-*   `commit_concurrency_limit`: maximum queued in-flight commit operations used by ordered commit sequencing. Defaults to `4096`.
+*   `commit_concurrency_limit`: maximum in-flight commit operations, whether they are queued through ordered commit sequencing or run concurrently for independent-ack transports. Defaults to `4096`.
 
 Middleware can be attached to inputs or outputs. The most commonly used ones are `retry`, `dlq`, `deduplication`, `limiter`, and `cookie_jar`. Retry/DLQ are especially useful with batching because partial failures can be retried or sent to a DLQ without treating the entire batch as equally broken.
 

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/mq-bridge.schema.json

@@ -805,6 +805,14 @@
           "type": "boolean",
           "default": false
         },
+        "shared": {
+          "description": "(Publisher only) Share one gRPC channel per connection (default: true); false forces a dedicated channel.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "timeout_ms": {
           "description": "Timeout in milliseconds.\n- Client mode: used as the connection timeout and per-request deadline.\n- Server mode: applied as the per-request deadline on the embedded server.",
           "type": [
@@ -977,6 +985,14 @@
           "$ref": "#/$defs/HttpServerProtocol",
           "default": "auto"
         },
+        "shared": {
+          "description": "(Publisher only) Share one HTTP client per connection (default: true); false forces a dedicated client.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "stream_response_to": {
           "description": "(Publisher only) Optional endpoint that receives streamed HTTP response items as correlated messages.\n\nUse a `stream_buffer` endpoint here when callers need to read streamed\nresponse items later through a normal mq-bridge consumer. Each streamed\nitem is published with `correlation_id`, `http_stream_id`,\n`http_stream_index`, `http_stream_format`, and `http_stream_end`\nmetadata. If the request message has no `correlation_id`, the HTTP\npublisher uses `format!(\"{:032x}\", request.message_id)` so callers can\nderive the consumer correlation id before calling `send`.",
           "anyOf": [
@@ -1215,6 +1231,14 @@
             ]
           }
         },
+        "shared": {
+          "description": "(Publisher only) Share one producer per connection (default: true); false gives a dedicated producer.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "tls": {
           "description": "TLS configuration.",
           "$ref": "#/$defs/TlsConfig",
@@ -1574,6 +1598,14 @@
           "format": "uint64",
           "minimum": 0
         },
+        "shared": {
+          "description": "Share one MongoDB client per connection (default: true); false forces a dedicated client.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "tls": {
           "description": "TLS configuration.",
           "$ref": "#/$defs/TlsConfig",
@@ -1806,6 +1838,14 @@
           "format": "uint64",
           "minimum": 0
         },
+        "shared": {
+          "description": "Share one NATS client per connection (default: true); false forces a dedicated connection.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "stream": {
           "description": "(Consumer only). The JetStream stream name. Required for Consumers.",
           "type": [
@@ -2148,6 +2188,14 @@
             "null"
           ]
         },
+        "shared": {
+          "description": "Share one connection pool per connection (default: true); false forces a dedicated pool.",
+          "type": [
+            "boolean",
+            "null"
+          ],
+          "default": true
+        },
         "table": {
           "description": "The table to interact with.",
           "type": "string"

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/mq_bridge/config.pyi

@@ -110,6 +110,7 @@ class GrpcConfig(TypedDict, total=False):
     initial_stream_window_size: Optional[int]
     max_decoding_message_size: Optional[int]
     server_mode: bool
+    shared: Optional[bool]
     timeout_ms: Optional[int]
     tls: TlsConfig
     topic: Optional[str]
@@ -134,6 +135,7 @@ class HttpConfig(TypedDict, total=False):
     receive_streamable: bool
     request_timeout_ms: Optional[int]
     server_protocol: HttpServerProtocol
+    shared: Optional[bool]
     stream_response_to: Optional[Endpoint]
     tcp_keepalive_ms: Optional[int]
     tls: TlsConfig
@@ -165,6 +167,7 @@ class KafkaConfig(TypedDict, total=False):
     group_id: Optional[str]
     password: Optional[str]
     producer_options: Optional[List[List[Any]]]
+    shared: Optional[bool]
     tls: TlsConfig
     topic: Optional[str]
     url: Required[str]
@@ -221,6 +224,7 @@ class MongoDbConfig(TypedDict, total=False):
     reply_polling_ms: Optional[int]
     request_reply: bool
     request_timeout_ms: Optional[int]
+    shared: Optional[bool]
     tls: TlsConfig
     ttl_seconds: Optional[int]
     url: Required[str]
@@ -254,6 +258,7 @@ class NatsConfig(TypedDict, total=False):
     prefetch_count: Optional[int]
     request_reply: bool
     request_timeout_ms: Optional[int]
+    shared: Optional[bool]
     stream: Optional[str]
     stream_max_bytes: Optional[int]
     stream_max_messages: Optional[int]
@@ -319,6 +324,7 @@ class SqlxConfig(TypedDict, total=False):
     password: Optional[str]
     polling_interval_ms: Optional[int]
     select_query: Optional[str]
+    shared: Optional[bool]
     table: Required[str]
     tls: TlsConfig
     url: Required[str]

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/python/mq-bridge-py/src/lib.rs

@@ -567,7 +567,8 @@ impl Route {
 
         let wait_name = name.clone();
         let wait_run_state = Arc::clone(&run_state);
-        let handle = thread::Builder::new()
+        let cleanup_runtime = Arc::clone(&runtime);
+        let handle = match thread::Builder::new()
             .name(format!("mqb-route-{name}"))
             .spawn(move || {
                 let stop_name = wait_name.clone();
@@ -576,8 +577,16 @@ impl Route {
                     core::Route::stop(&stop_name).await;
                 });
                 finish_run(&wait_run_state, &wait_name);
-            })
-            .map_err(to_py_runtime_error)?;
+            }) {
+            Ok(handle) => handle,
+            Err(err) => {
+                // The route is already deployed and run_state marked running; a failed
+                // spawn would otherwise leak the deployed route and its name reservation.
+                py.detach(|| cleanup_runtime.block_on(async { core::Route::stop(&name).await }));
+                finish_run(&run_state, &name);
+                return Err(to_py_runtime_error(err));
+            }
+        };
 
         self.lock_run_state()?.join_handle = Some(handle);
         Ok(())

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/python/mq-bridge-py/tests/test_config_types.py

@@ -30,11 +30,16 @@ def test_generated_config_types_are_up_to_date() -> None:
     generator = _load_generator()
     pyi, py = generator.generate()
 
+    regen = (
+        "stale generated config types. Rebuild the extension and regenerate:\n"
+        "    cd python/mq-bridge-py && uv run maturin develop "
+        "&& uv run --no-sync python scripts/gen_config_types.py"
+    )
     assert pyi == (PACKAGE_DIR / "mq_bridge" / "config.pyi").read_text(), (
-        "config.pyi is stale; regenerate with scripts/gen_config_types.py"
+        f"config.pyi is {regen}"
     )
     assert py == (PACKAGE_DIR / "mq_bridge" / "config.py").read_text(), (
-        "config.py is stale; regenerate with scripts/gen_config_types.py"
+        f"config.py is {regen}"
     )
 
 

{mq_bridge_py_basic-0.2.21 → mq_bridge_py_basic-0.3.0}/scripts/httparena/README.md

@@ -98,7 +98,7 @@ scripts/httparena/frameworks/
 ## Submitting upstream
 
 1. Pin the version: each Rust `Cargo.toml` and the Python `Dockerfile` reference
-   this repo at tag `v0.2.18` — bump to the release you want to benchmark.
+   this repo at tag `v0.2.21` — bump to the release you want to benchmark.
 2. Fork `MDA2AV/HttpArena` and copy each `scripts/httparena/frameworks/<name>/`
    into the fork's `frameworks/<name>/`.
 3. On the PR, validate and benchmark per framework: