Fix httpclient-5.x plugin injecting sw8 headers into ClickHouse HTTP requests #2369
wu-shengAnnotations
69 errors and 23 warnings
|
zookeeper-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-3.1.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-async-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
micronaut-http-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-4.3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
aerospike-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
vertx-web-3.6plus-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
elasticjob-2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
gateway-3.x-filter-context-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
quasar-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
undertow-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
neo4j-4.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
retransform-class-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
mariadb-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
vertx-web-3.54minus-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
guava-eventbus-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
thrift-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
retransform-class-tomcat-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
clickhouse-0.3.1-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-kafka-2.2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
graphql-9.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-kafka-2.3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
dbcp-2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
jsonrpc4j-1.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
graphql-16plus-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
shenyu-2.4.x-dubbo-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
jdk-forkjoinpool-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
xxl-job-2.3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-kafka-1.3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
graphql-12.x-15.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
shenyu-2.4.x-sofarpc-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
solon-2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
clickhouse-0.3.2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
undertow-worker-thread-pool-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
tomcat-thread-pool-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
shenyu-2.4.x-grpc-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
nats-2.14.x-2.16.5-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
nats-2.14.x-2.16.5-scenario
The operation was canceled.
|
|
druid-1.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
baidu-brpc-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
baidu-brpc-scenario
The operation was canceled.
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
The operation was canceled.
|
|
grpc-generic-call-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
grpc-generic-call-scenario
The operation was canceled.
|
|
vertx-eventbus-3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
vertx-eventbus-3.x-scenario
The operation was canceled.
|
|
quartz-scheduler-2.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
mysql-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
mysql-scenario
The operation was canceled.
|
|
spring-4.1.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-4.1.x-scenario
The operation was canceled.
|
|
shenyu-2.4.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
shenyu-2.4.x-scenario
The operation was canceled.
|
|
vertx-core-4.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
vertx-core-4.x-scenario
The operation was canceled.
|
|
gateway-3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
gateway-3.x-scenario
The operation was canceled.
|
|
baidu-brpc-3.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
baidu-brpc-3.x-scenario
The operation was canceled.
|
|
hbase-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
hbase-scenario
The operation was canceled.
|
|
hikaricp-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
hikaricp-scenario
The operation was canceled.
|
|
webflux-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
webflux-scenario
The operation was canceled.
|
|
spring-scheduled-3.x-5.x-scenario
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
spring-scheduled-3.x-5.x-scenario
The operation was canceled.
|
|
Test
Canceling since a higher priority waiting request for plugins-3-797 exists
|
|
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
jdk-threadpool-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
graphql-8.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
xxl-job-2.2.0-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
nats-2.14.x-2.16.5-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
nats-2.14.x-2.16.5-scenario
No files were found with the provided path: test/plugin/workspace. No artifacts will be uploaded.
|
|
druid-1.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
baidu-brpc-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
No files were found with the provided path: test/plugin/workspace. No artifacts will be uploaded.
|
|
grpc-generic-call-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
vertx-eventbus-3.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
quartz-scheduler-2.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mysql-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
spring-4.1.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
shenyu-2.4.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
vertx-core-4.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
gateway-3.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
baidu-brpc-3.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hbase-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
hikaricp-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
webflux-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
spring-scheduled-3.x-5.x-scenario
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
skywalking-agent
Expired
|
44.3 MB |
sha256:f29e70bd4f95bf9449d199a33776a7e653de7adbff01e511aac2da7d3c24fd61
|
|
|
test-plugin-workspace-baidu-brpc-3.x-scenario
Expired
|
52.1 MB |
sha256:31e51f5cc3b20aad90fa72e5c1d3875841c1f0d6a7ebaff2ce5f6b7dfaa83c7d
|
|
|
test-plugin-workspace-baidu-brpc-scenario
Expired
|
170 MB |
sha256:2a654c7d1192706232f5dedfe51b81c53bf164233b2933fec56b07a93a7eb571
|
|
|
test-plugin-workspace-druid-1.x-scenario
Expired
|
108 MB |
sha256:b94f0bd675e16ed0eba30a0d8bfc7e4def308746596279f9cb57310113144d70
|
|
|
test-plugin-workspace-gateway-3.x-scenario
Expired
|
44.3 MB |
sha256:c6c9ddd23bc8ead5db9378f63cdcc2a78856e298b5db0ad788fb620344a3b830
|
|
|
test-plugin-workspace-graphql-8.x-scenario
Expired
|
34.1 MB |
sha256:175dbc32277b15ed2f417a6af553a39d95f11ca09038d433aeb3a0367fd6ea15
|
|
|
test-plugin-workspace-grpc-generic-call-scenario
Expired
|
1.23 KB |
sha256:5c764923f4bf03c1290d87b7c1f3dea3bc5ca03c1abc78da2d33f283ac929230
|
|
|
test-plugin-workspace-hbase-scenario
Expired
|
83.7 MB |
sha256:70210841dc2a6e08269134df276abafe735d43b4e2500b2dc52cabd733d26c25
|
|
|
test-plugin-workspace-hikaricp-scenario
Expired
|
128 MB |
sha256:cfab45b46d7ce7b4576cb2b9aab26583cbe583ba65ba546fb432839bd8d64903
|
|
|
test-plugin-workspace-jdk-threadpool-scenario
Expired
|
73 MB |
sha256:f2321f2aebf35665e946153201f7e6cff0f72063f204932bec8249958450b57a
|
|
|
test-plugin-workspace-mysql-scenario
Expired
|
134 MB |
sha256:ef76eb76f7e745d9e8b5f5b45b7d736a0d2e9ccd01ce0dff07768a23e1cf39bb
|
|
|
test-plugin-workspace-quartz-scheduler-2.x-scenario
Expired
|
190 MB |
sha256:c326b1f22651cd972654ca9062cc94d5d5dc41fa07864ce251eb544d6577f9c0
|
|
|
test-plugin-workspace-shenyu-2.4.x-scenario
Expired
|
102 MB |
sha256:862057d5a3195ebefc0516e69db0c146a0549b5430b15c0c5ef164d8a35ed848
|
|
|
test-plugin-workspace-spring-4.1.x-scenario
Expired
|
53.6 MB |
sha256:1cedf2d4c5bbed9547a1622db7d42408e3f6dc3667862d2c2bf3fcff96265eda
|
|
|
test-plugin-workspace-spring-scheduled-3.x-5.x-scenario
Expired
|
29.5 MB |
sha256:9619d97e20907cf679a89300d3b890932a7f095264fd87c734845c7bed022e5a
|
|
|
test-plugin-workspace-vertx-core-4.x-scenario
Expired
|
98 MB |
sha256:91c16428e174601a1b40de8afe8f351673e96d0276382dd3f9897005795f8b4d
|
|
|
test-plugin-workspace-vertx-eventbus-3.x-scenario
Expired
|
64 MB |
sha256:76725bebc97aa644b35a9d337d3f10e76c9163547c52d93e51b4bb68bc95c681
|
|
|
test-plugin-workspace-webflux-scenario
Expired
|
83 MB |
sha256:7120a748bec09bcda293ca81ee2516cb14d96ee5aacd38e7ff42f3cbb24f40f3
|
|
|
test-plugin-workspace-xxl-job-2.2.0-scenario
Expired
|
59.4 MB |
sha256:c7abe8e2d29833d0ca436022dc288d07552d29ae8ea1c6df31f6c13720083888
|
|
|
test-tools
Expired
|
468 MB |
sha256:339bb365685f2fab7b74b39c9241365acabd25d8d05dd39c955b4518afaa9d0a
|
|