Skip to content

Fluxzero 1.226.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Jul 10:10
1.226.0
eaaa8b5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.226.0 (2026-07-19)

Features

  • namespaces: make SDK components namespace-aware (437052d)

    Keep ordinary application work in the configured application namespace while carrying namespaces across direct messaging relationships. Add canonical namespaced component views, isolated persistence and cache behavior, context-safe asynchronous handling, and focused regression coverage.

Bug Fixes

  • test-server: isolate metrics monitor test events (#260) (eaaa8b5)

    Automated Codex repair for failing main build.

    Failing run: https://github.com/fluxzero-io/fluxzero-sdk-java/actions/runs/29682363093
    Run id: 29682363093
    Head SHA: 437052d

    Codex report:

    Implemented the minimal test isolation fix and wrote `/tmp/codex-repair-commit-title.txt`:

    `fix(test-server): isolate metrics monitor test events`

    **Root Cause**
    `TestServerMetricsMonitorTest` registered a global metrics listener and asserted the last observed event. Under JUnit class-level parallelism, `TestServerWebsocketContractTest` can emit lifecycle/websocket metrics into the same global monitor first, so the assertion saw an unrelated event instead of `"connected"`.

    **Reproduction Evidence**
    `./mvnw -pl test-server -am -Dtest=TestServerMetricsMonitorTest,TestServerWebsocketContractTest -Dsurefire.failIfNoSpecifiedTests=false test`
    failed before the fix with the monitor test observing an unrelated `RuntimeLifecycleEvent`.

    **Files Changed**
    [test-server/src/test/java/io/fluxzero/testserver/metrics/TestServerMetricsMonitorTest.java](/home/runner/work/fluxzero-sdk-java/fluxzero-sdk-java/test-server/src/test/java/io/fluxzero/testserver/metrics/TestServerMetricsMonitorTest.java)

    The test now uses a unique `clientId` and filters monitor callbacks to that id, so concurrent test-server metrics cannot overwrite the event under assertion.

    **Verification**
    `./mvnw -pl test-server -am -Dtest=TestServerMetricsMonitorTest,TestServerWebsocketContractTest -Dsurefire.failIfNoSpecifiedTests=false test`

    Result: passed, `Tests run: 12, Failures: 0, Errors: 0, Skipped: 0`.

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@​users.noreply.github.com>

Assets 4
Loading