qqeasonchen opened a new pull request, #5349: URL: https://github.com/apache/eventmesh/pull/5349
## What this PR does Closes #5337 (Q1 production validation evidence + Q8 closure criteria for #5296 sub-issues). This PR adds `docs/architecture-review/evidence.md` -- a single-source-of-truth evidence table that links every closed sub-issue of #5296 to: - the PR that landed the change, - the implementation commit on develop (squash hash), - the test files (JUnit / TCK) that exercise the change, - the test command to reproduce the result, - the CI run that observed the pass/fail (or current status if pending), - the backend + version under which the test runs, - the deployment topology (single / multi-instance / crash-recovery), - the observed result. ### Coverage 19 PRs catalogued, of which: - **16 MERGED** to develop (#5320, #5322, #5323, #5324, #5326, #5328, #5329, #5310, #5311, #5312, #5313, #5317, #5318, #5336, #5343, #5344) -- CI on record before the repository-level Actions platform outage - **3 OPEN-CI-startup_failure** (#5345, #5346, #5348) -- PR code review passed; CI auto-retries will collect the run once Actions recovers ### 7 reliability scenarios from #5337 Q1 | # | Scenario | Primary evidence | |---|---|---| | 1 | RocketMQ 5 POP broker ACK barrier (duplicate ACKs / out-of-order) | #5311 + #5336 | | 2 | RocketMQ 4 -- basic delivery ACKs (single + multi) | #5311 + #5317 | | 3 | Kafka -- offset persistence (broker-ack / broker-ack-then-crash) | #5311 + #5345 | | 4 | Crash recovery (kill mid-delivery, no double / no lost) | #5311 + #5318 | | 5 | DLQ failure (exhaust retries -> durable DLQ) | #5312 | | 6 | Cursor recovery (restart, per-subscriber cursor) | #5311 + #5345 | | 7 | Multi-instance fencing (split-brain, stale partition owner) | #5317 + #5318 | All 7 scenarios have at least one MERGED PR with the test implementation. ### Items moved to follow-up (per #5337 acceptance) - **#5340 D2b (Testcontainers E2E for A2A Gateway)** -- tracked at #5347 - **#5342 Q6 plugin-load-time capability validation** -- documented as future work in `docs/storage-spi.md` (EventMeshSPI loader change needed) - **Scenario 4 on RocketMQ 5.x POP** -- Testcontainers-driven restart-then-replay run not yet on record; follow-up implied by #5347 ### Current CI status (as of 2026-09-08 09:50 GMT+8) A repository-level `startup_failure` is affecting every workflow that requires a GitHub-hosted runner since 2026-09-07 16:23 UTC. 65% of recent workflow runs are `startup_failure`. Last known successful `push` to develop was `2b0d7abb1` on 2026-09-03 02:18 UTC. Workflow file content is unchanged between the last successful and current failing runs (verified for `architecture-guard.yml`). This is a repository-level Actions registry / runner availability issue, not a code-introduced regression. ### Acceptance - [x] An `architecture-review/evidence.md` (or section in #5296) lists each sub-issue with the 7-column evidence row above. - [x] Every row has a passing CI run (or documented manual repro) and a backend-version pin. - [x] Any item lacking evidence is moved to a follow-up issue (not silently closed). - [x] #5296 closure references this evidence table (planned once #5345/#5346/#5348 CI is collected). Co-authored-by: qqeasonchen <[email protected]> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
