mq-bridge-basic 0.4.17__tar.gz

mq_bridge_basic-0.4.17/.cargo/config.toml

@@ -0,0 +1,25 @@
+# Workspace-wide Cargo config. Cargo discovers this file from the *current
+# directory* upward, not from the manifest, so it is what applies to every
+# build invoked from the repository root — CI, Docker, and plain local
+# `cargo build`. The app keeps its own path-scoped config for the settings
+# that must only affect app-cwd builds (see apps/mq-bridge-app/.cargo/config.toml).
+
+[env]
+# librdkafka's CMakeLists declares cmake_minimum_required(3.2), which cmake 4
+# refuses. rdkafka-sys is reachable from the engine's kafka feature and from
+# every app build, so this belongs at the root.
+CMAKE_ARGS = "-DCMAKE_POLICY_VERSION_MINIMUM=3.5"
+# Bundled SQLite (sqlx) with `exp`, `ln`, `pow` etc., e.g. for decaying averages in a lookup.
+LIBSQLITE3_FLAGS = "SQLITE_ENABLE_MATH_FUNCTIONS"
+
+# Pinned explicitly so a --manifest-path build of the app workspace still writes
+# here instead of defaulting to apps/mq-bridge-app/target. One target dir for the
+# engine, the app, tauri and maturin.
+[build]
+target-dir = "target"
+
+# One standard dev feature set: every distinct `--features` list builds its own
+# mq_bridge rlib and incremental cache (0.5-1.8 GB each).
+[alias]
+cf = "check --all-targets --features full,test-utils"
+tf = "test --features full,test-utils"

mq_bridge_basic-0.4.17/.coderabbit.yaml

@@ -0,0 +1,5 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+reviews:
+  pre_merge_checks:
+    docstrings:
+      mode: "off"

mq_bridge_basic-0.4.17/.dockerignore

@@ -0,0 +1,18 @@
+.git
+.serena
+.tokensave
+logs
+target
+**/target
+**/node_modules
+apps/mq-bridge-app/dev/docs/book
+
+# Local build output
+**/.venv
+**/__pycache__
+**/*.so
+**/*.node
+**/*.whl
+python/mq-bridge-py/dist
+apps/mq-bridge-app/test-results
+apps/mq-bridge-app/playwright-report

mq_bridge_basic-0.4.17/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,51 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Description
+
+<!-- A clear and concise description of what the bug is -->
+
+## Steps to Reproduce
+
+1. 
+2. 
+3. 
+
+## Expected Behavior
+
+<!-- What you expected to happen -->
+
+## Actual Behavior
+
+<!-- What actually happened -->
+
+## Environment
+
+- OS: [e.g., Ubuntu 22.04, macOS 13, Windows 11]
+- Rust version: [e.g., 1.75.0]
+- mq-bridge version: [e.g., 0.1.2]
+- Features enabled: [e.g., kafka, nats, full]
+
+## Configuration
+
+<!-- If applicable, paste your configuration (remove sensitive information) -->
+
+```yaml
+# Your config here
+```
+
+## Logs/Error Messages
+
+```
+<!-- Paste relevant logs or error messages here -->
+```
+
+## Additional Context
+
+<!-- Add any other context about the problem here -->
+

mq_bridge_basic-0.4.17/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,36 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Description
+
+<!-- A clear and concise description of the feature you'd like to see -->
+
+## Motivation
+
+<!-- Why is this feature needed? What problem does it solve? -->
+
+## Proposed Solution
+
+<!-- Describe how you envision this feature working -->
+
+## Alternatives Considered
+
+<!-- Describe any alternative solutions or features you've considered -->
+
+## Use Cases
+
+<!-- Provide examples of how this feature would be used -->
+
+1. 
+2. 
+3. 
+
+## Additional Context
+
+<!-- Add any other context, mockups, or examples about the feature request here -->
+

mq_bridge_basic-0.4.17/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,42 @@
+## Description
+
+<!-- Describe your changes in detail -->
+
+## Type of Change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Performance improvement
+- [ ] Code refactoring
+
+## Testing
+
+<!-- Describe the tests you ran and how to verify your changes -->
+
+- [ ] Unit tests pass
+- [ ] Integration tests pass (if applicable)
+- [ ] Manual testing completed
+
+## Checklist
+
+- [ ] Code follows the project's style guidelines
+- [ ] Self-review completed
+- [ ] Comments added for complex code
+- [ ] Documentation updated (if needed)
+- [ ] No new warnings generated
+- [ ] Tests added/updated for new functionality
+- [ ] All tests pass locally
+
+## Related Issues
+
+<!-- Link to related issues using #issue_number -->
+
+Fixes #
+Related to #
+
+## Additional Notes
+
+<!-- Any additional information that reviewers should know -->
+

mq_bridge_basic-0.4.17/.github/dependabot.yml

@@ -0,0 +1,59 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "cargo" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    target-branch: "dev"
+    schedule:
+      interval: "monthly"
+    groups:
+      minor-and-patch:
+        applies-to: version-updates
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
+
+  # The app workspace has its own Cargo.lock, so the "/" cargo entry above does
+  # not reach it. Without this, app dependencies would never be updated.
+  - package-ecosystem: "cargo"
+    directory: "/apps/mq-bridge-app"
+    target-branch: "dev"
+    schedule:
+      interval: "weekly"
+    groups:
+      app-minor-and-patch:
+        applies-to: version-updates
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
+
+  - package-ecosystem: "npm"
+    directory: "/apps/mq-bridge-app"
+    target-branch: "dev"
+    schedule:
+      interval: "weekly"
+    groups:
+      npm-minor-patch:
+        applies-to: version-updates
+        update-types:
+          - "minor"
+          - "patch"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    target-branch: "dev"
+    schedule:
+      interval: "weekly"
+    groups:
+      github-actions:
+        applies-to: version-updates
+        patterns:
+          - "*"

mq_bridge_basic-0.4.17/.github/workflows/app.yml

@@ -0,0 +1,321 @@
+name: App CI
+
+on:
+  pull_request:
+    branches: [main, dev]
+    paths:
+      - "Cargo.toml"
+      - "Cargo.lock"
+      - "src/**"
+      - "apps/mq-bridge-app/**"
+      - ".github/workflows/app.yml"
+  # Called by release.yml so a tag runs the same app gate a PR does, rather
+  # than a second copy of it that can drift.
+  workflow_call:
+  workflow_dispatch:
+    inputs:
+      update_visual_baselines:
+        description: "Re-render the Linux screenshot baselines and upload them as an artifact"
+        type: boolean
+        default: false
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  rust:
+    name: App Rust
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8
+        with:
+          components: clippy
+
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
+        with:
+          # One cache for every app job: rust, ui and both integration
+          # shards compile the same crates at the same features.
+          shared-key: app
+          # rust-cache resolves its workspace at the repo root, so by default it
+          # purges every crate whose manifest lives under it -- mq-bridge itself
+          # included. Without this each app job recompiles the engine from
+          # scratch; only registry deps would survive.
+          cache-workspace-crates: true
+
+      - name: Install system dependencies
+        run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev libssl-dev pkg-config zlib1g-dev protobuf-compiler libwebkit2gtk-4.1-dev libappindicator3-dev librsvg2-dev patchelf
+
+      - name: Test desktop crate
+        working-directory: apps/mq-bridge-app
+        run: cargo test -p mq-bridge-app-desktop --lib
+
+      - name: Check app crates
+        working-directory: apps/mq-bridge-app
+        run: cargo check -p mq-bridge-app-core -p mq-bridge-app --all-targets
+
+      - name: Lint app crates
+        working-directory: apps/mq-bridge-app
+        run: cargo clippy -p mq-bridge-app-core -p mq-bridge-app --all-targets -- -D warnings
+
+      - name: Test app crates
+        working-directory: apps/mq-bridge-app
+        run: cargo test -p mq-bridge-app-core -p mq-bridge-app --lib --bins
+
+      # The app resolves its own Cargo.lock, so the engine's supply-chain job in
+      # ci.yml does not cover it. Same policy, plus the Tauri-tree exceptions.
+      - name: Licenses / bans / sources
+        uses: EmbarkStudios/cargo-deny-action@v2
+        with:
+          manifest-path: apps/mq-bridge-app/Cargo.toml
+          command: check bans licenses sources
+
+      # Informational, same policy as the engine's supply-chain job in ci.yml:
+      # the app resolves its own Cargo.lock, so deny.toml's advisory ignores are
+      # only actually exercised if this runs.
+      - name: Advisories (informational)
+        continue-on-error: true
+        uses: EmbarkStudios/cargo-deny-action@v2
+        with:
+          manifest-path: apps/mq-bridge-app/Cargo.toml
+          command: check advisories
+
+  ui:
+    name: App UI
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8
+
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
+        with:
+          # One cache for every app job: rust, ui and both integration
+          # shards compile the same crates at the same features.
+          shared-key: app
+          # rust-cache resolves its workspace at the repo root, so by default it
+          # purges every crate whose manifest lives under it -- mq-bridge itself
+          # included. Without this each app job recompiles the engine from
+          # scratch; only registry deps would survive.
+          cache-workspace-crates: true
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: lts/*
+          cache: npm
+          cache-dependency-path: apps/mq-bridge-app/package-lock.json
+
+      - name: Install system dependencies
+        run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev libssl-dev pkg-config zlib1g-dev protobuf-compiler
+
+      - name: Install frontend dependencies
+        working-directory: apps/mq-bridge-app
+        run: npm ci
+
+      - name: Run frontend unit tests
+        working-directory: apps/mq-bridge-app
+        run: npm run test:unit
+
+      - name: Install Playwright browsers
+        working-directory: apps/mq-bridge-app
+        # firefox and webkit run only the cross-browser specs (see
+        # playwright.config.js), which is where engine-specific form-control
+        # behaviour has bitten before.
+        run: npx playwright install --with-deps chromium firefox webkit
+
+      - name: Build app binary for UI tests
+        working-directory: apps/mq-bridge-app
+        run: cargo build -p mq-bridge-app --bin mq-bridge-app
+
+      - name: Run frontend UI tests
+        working-directory: apps/mq-bridge-app
+        run: npm run test:ui
+
+      # The screenshot suite skips itself while this platform has no committed
+      # baseline. Run this workflow manually with update_visual_baselines=true to
+      # render them here, then review and commit the artifact.
+      - name: Re-render visual baselines
+        if: inputs.update_visual_baselines
+        working-directory: apps/mq-bridge-app
+        run: npm run build:ui && npx playwright test ui-visual.spec.js --update-snapshots=all || true
+
+      - name: Upload visual baselines
+        if: inputs.update_visual_baselines
+        uses: actions/upload-artifact@v7
+        with:
+          name: visual-baselines-linux
+          path: apps/mq-bridge-app/tests/playwright/ui-visual.spec.js-snapshots/
+          if-no-files-found: warn
+
+      - name: Upload Playwright test artifacts
+        if: failure()
+        uses: actions/upload-artifact@v7
+        with:
+          name: playwright-test-results
+          path: |
+            apps/mq-bridge-app/test-results/
+            apps/mq-bridge-app/playwright-report/
+          if-no-files-found: ignore
+
+  integration:
+    name: App integration (${{ matrix.target }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        target: [cli_copy_test, web_ui_test]
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8
+
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
+        with:
+          # One cache for every app job: rust, ui and both integration
+          # shards compile the same crates at the same features.
+          shared-key: app
+          # rust-cache resolves its workspace at the repo root, so by default it
+          # purges every crate whose manifest lives under it -- mq-bridge itself
+          # included. Without this each app job recompiles the engine from
+          # scratch; only registry deps would survive.
+          cache-workspace-crates: true
+
+      - name: Install system dependencies
+        run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev libssl-dev pkg-config zlib1g-dev protobuf-compiler
+
+      - name: Run integration suite
+        working-directory: apps/mq-bridge-app
+        run: cargo test -p mq-bridge-app --test ${{ matrix.target }}
+
+  # Compile the docker suite ONCE. Nine runners each rebuilding the engine cost
+  # ~25 runner-minutes for ~3 minutes of tests, and held slots the rest of the
+  # matrix was queuing for.
+  docker-build:
+    name: App docker — Build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8
+
+      - name: Cache cargo build
+        uses: Swatinem/rust-cache@v2
+        with:
+          # One cache for every app job: rust, ui and both integration
+          # shards compile the same crates at the same features.
+          shared-key: app
+          # rust-cache resolves its workspace at the repo root, so by default it
+          # purges every crate whose manifest lives under it -- mq-bridge itself
+          # included. Without this each app job recompiles the engine from
+          # scratch; only registry deps would survive.
+          cache-workspace-crates: true
+
+      - name: Install system dependencies
+        run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev libssl-dev pkg-config zlib1g-dev protobuf-compiler
+
+      # The test drives the CLI through `env!("CARGO_BIN_EXE_mq-bridge-app")`, an
+      # absolute path baked in at compile time. Every ubuntu-latest runner checks
+      # out to the same path, so shipping the binaries where they were built is
+      # what keeps that resolvable in the jobs below.
+      #
+      # cargo reports the binary it just built; a restored cache can leave several
+      # older `cli_copy_docker_test-<hash>` files next to it, so globbing deps/
+      # would pick an arbitrary one.
+      - name: Build the docker test binary
+        working-directory: apps/mq-bridge-app
+        shell: bash
+        run: |
+          cargo test -p mq-bridge-app --test cli_copy_docker_test --no-run \
+            --message-format=json > "$RUNNER_TEMP/build.json"
+          jq -r 'select(.target.name == "cli_copy_docker_test") | .executable // empty' \
+            "$RUNNER_TEMP/build.json" | tail -1 > "$RUNNER_TEMP/test-binary"
+          jq -r 'select(.target.name == "mq-bridge-app"
+                        and (.target.kind // [] | index("bin"))) | .executable // empty' \
+            "$RUNNER_TEMP/build.json" | tail -1 > "$RUNNER_TEMP/cli-binary"
+          test -s "$RUNNER_TEMP/test-binary" && test -s "$RUNNER_TEMP/cli-binary"
+
+      - name: Collect binaries
+        shell: bash
+        run: |
+          mkdir -p docker-suite
+          cp "$(cat "$RUNNER_TEMP/test-binary")" docker-suite/test-binary
+          cp "$(cat "$RUNNER_TEMP/cli-binary")" docker-suite/mq-bridge-app
+          cp "$RUNNER_TEMP/cli-binary" docker-suite/cli-path
+
+      - name: Upload docker suite binaries
+        uses: actions/upload-artifact@v7
+        with:
+          name: app-docker-suite
+          path: docker-suite
+          retention-days: 1
+
+  # One backend per runner, so the servers never compete for memory or for the
+  # fixed host ports the test URIs use. `run_docker_tests.sh` does the same loop
+  # locally, one at a time.
+  docker:
+    name: App docker (${{ matrix.backend }})
+    runs-on: ubuntu-latest
+    needs: docker-build
+    strategy:
+      fail-fast: false
+      matrix:
+        backend:
+          [postgres, mysql, mariadb, kafka, nats, mongodb, redis, amqp, mqtt]
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Download docker suite binaries
+        uses: actions/download-artifact@v8
+        with:
+          name: app-docker-suite
+          path: docker-suite
+
+      # upload-artifact drops the executable bit, and the CLI has to land back at
+      # the exact path compiled into the test binary.
+      - name: Restore binaries
+        shell: bash
+        run: |
+          cli="$(cat docker-suite/cli-path)"
+          mkdir -p "$(dirname "$cli")"
+          mv docker-suite/mq-bridge-app "$cli"
+          chmod +x "$cli" docker-suite/test-binary
+
+      - name: Install runtime libraries
+        run: sudo apt-get update && sudo apt-get install -y libcurl4-openssl-dev libssl-dev zlib1g-dev
+
+      # The engine's own integration stacks, so there is one definition per
+      # service rather than a second copy that can drift.
+      - name: Start ${{ matrix.backend }}
+        run: docker compose -f tests/integration/docker-compose/${{ matrix.backend }}.yml up -d --wait --wait-timeout 300
+
+      # The backend name filters the test names as well as MQB_TEST_BACKEND:
+      # `backend!` skips by returning, so without the name filter every excluded
+      # test still reports `ok` and a broken service would look green.
+      - name: Run ${{ matrix.backend }} tests
+        # `shell: bash` for pipefail: the default shell would take `tee`'s exit
+        # status and report a failing test run as a pass.
+        shell: bash
+        env:
+          MQB_TEST_BACKEND: ${{ matrix.backend }}
+        run: |
+          ./docker-suite/test-binary \
+            --ignored --test-threads=1 ${{ matrix.backend }} 2>&1 | tee result.log
+          grep -qE 'test result: ok\. [1-9]' result.log \
+            || { echo "no ${{ matrix.backend }} tests ran"; exit 1; }
+
+      - name: Service logs
+        if: failure()
+        run: docker compose -f tests/integration/docker-compose/${{ matrix.backend }}.yml logs --tail 200