yangjj-iso opened a new pull request, #7581: URL: https://github.com/apache/shenyu/pull/7581
WASM fixture verification can silently accept a missing gateway family when bridge fixtures are present, and it does not check newly added WAT families. Require `wasm-gateway`, discover every `wasm-*` fixture directory, and reject missing, malformed or empty families while retaining byte-for-byte binary checks. Remove Cargo's forced offline mode so fresh runners can resolve future guest dependencies. Document the clean-checkout requirement and cleanup limits for forced process termination, and add Javadoc for the existing strict export lookup contract. Nine Python regression checks run in the fixture workflow; three directory checks fail with the previous verifier. Related to the post-merge review on #7567. The export-policy concern is already resolved in #7569 at `1fc74a273`: that head has no competing WasmLoader production change and rejects non-function exports in its lookup test. Validation (Java 17, WABT 1.0.42, Rust 1.90.0): - 9 Python regression checks passed. - All 11 gateway WAT binaries reproduced byte-for-byte. - All five Rust guests rebuilt; 47 WASM Java tests passed without failures, errors or skips, including real HTTP gateway and invalid-initializer coverage. Original resource bytes were restored. - Checkstyle and Apache RAT passed for the affected reactor; CI-pinned license-header checker passed. - `git diff --check` passed. - [x] Read the contribution guidelines. - [x] Add regression tests. - [ ] Full-repository Maven install; affected-reactor and fixture validation recorded above. -- 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]
