BobSong-dev opened a new pull request, #7864: URL: https://github.com/apache/shenyu/pull/7864
Depends on #7860 ## Background #7860 introduces gateway-owned MCP tracing with an application-provided OpenTelemetry SDK. Existing tests cover tracing behavior, but not the lifecycle when the plugin context is closed and recreated while the application SDK remains active. A regression here could shut down the application-owned SDK or duplicate span exports across reloads. This draft is stacked on #7860 and therefore transitively includes the prerequisite #7827. It should not be merged independently before #7860. ## Changes - Add `AgentMcpTracingLifecycleTest` to exercise enabled, disabled, and re-enabled plugin contexts under one application-owned `OpenTelemetrySdk`. - Assert plugin reload does not close the parent SDK, does not register another `SdkTracerProvider`, and that one terminal finish exports exactly one logical MCP span. - Assert the application can continue exporting spans after plugin context shutdown. ## Verification - Windows/JDK 17: Maven Wrapper `clean verify` for the Agent Gateway starter and upstream modules: 27 modules, 312 suites, 2,161 tests, 0 failures, 0 errors, 1 existing skipped test; Checkstyle and RAT passed. - RISC-V/QEMU/JDK 17: equivalent `sh ./mvnw clean verify`: 27 modules, 312 suites, 2,161 tests, 0 failures, 0 errors, 1 existing skipped test; container exit 0 and not OOM-killed. - Cross-platform audit matched 4,666 source files and individual test identities. - `git diff --check`: passed. Local verification only. GitHub CI has not run yet. Not run: full-project tests, production deployment, or native RISC-V hardware. -- 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]
