dajiaohuang opened a new pull request, #5491: URL: https://github.com/apache/linkis/pull/5491
### What is the purpose of the change `ServerConfiguration` now rejects an unset `wds.linkis.crypt.key`, but the `linkis-module` test resource does not set a key. This causes `ServerConfigurationTest` and `SecurityFilterTest` to fail during object initialization. Add a non-default synthetic key only to the module's test properties; production configuration and runtime behavior are unchanged. ### Related issues/PRs Related issue: #5482. This is a narrow follow-up to #5483, which fixes the compilation and other CI issues but explicitly leaves these two test failures unaddressed. ### Brief change log - Supply a synthetic, non-deployable crypt key in `linkis-module/src/test/resources/linkis.properties` so the existing tests can initialize `ServerConfiguration` while preserving its fail-closed production behavior. ### Validation - Focused `linkis-module` Maven tests passed: `ServerConfigurationTest` and `SecurityFilterTest` (11 tests total), using JDK 8 on the captured #5483 head `b346cd419b08b919e5126913b519228b86213c4b` plus this test-resource change. The current master compilation errors fixed by #5483 prevent running these tests on master until that PR is applied. - No Docker/WSL, service, database, customer data, credentials, or CI run was used. -- 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]
