Skip to content

optimize: use curator instead of zkclient in config model #10458

optimize: use curator instead of zkclient in config model

optimize: use curator instead of zkclient in config model #10458

Triggered via pull request September 2, 2024 01:58
Status Failure
Total duration 1m 37s
Artifacts

build.yml

on: pull_request
build_arm64-binary
0s
build_arm64-binary
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build (17)
Process completed with exit code 1.
build (8)
Process completed with exit code 1.
build (17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v2, actions/setup-java@v3.12.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v2, actions/setup-java@v3.12.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/