K8s: Missing tolerations for monitoring exporter deployment by VietND96 · Pull Request #3086 · SeleniumHQ/docker-selenium

VietND96 · 2026-02-22T16:02:11Z

User description

Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines, applied for this repository.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Fixes #3058
New config key monitoring.exporter.tolerations

Motivation and Context

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

I have read the contributing document.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have added tests to cover my changes.
All new and existing tests passed.

PR Type

Enhancement, Tests

Description

Add tolerations support for monitoring exporter deployment
Enable exporter pods to run on dedicated nodes
Add test to verify tolerations configuration
Update documentation and example values

Diagram Walkthrough

flowchart LR
  A["values.yaml"] -- "Add tolerations field" --> B["monitoring-exporter-deployment.yaml"]
  B -- "Apply tolerations to pods" --> C["Exporter Pods"]
  D["test.py"] -- "Verify tolerations" --> C
  E["CONFIGURATION.md"] -- "Document parameter" --> F["User Documentation"]
  G["dummy.yaml"] -- "Example config" --> H["Test Fixtures"]

File Walkthrough

Relevant files

Configuration changes

values.yaml `Add tolerations configuration parameter` charts/selenium-grid/values.yaml Add `tolerations` field under `monitoring.exporter` configuration Set default value to empty list `[]` Include comment documenting the purpose of tolerations	+2/-0

Enhancement

monitoring-exporter-deployment.yaml `Apply tolerations to exporter deployment` charts/selenium-grid/templates/monitoring-exporter-deployment.yaml Add tolerations template block to exporter deployment spec Use `with` conditional to apply tolerations when defined Apply proper YAML indentation with `nindent 6`	+3/-0

Documentation

CONFIGURATION.md `Document exporter tolerations parameter` charts/selenium-grid/CONFIGURATION.md Document new `monitoring.exporter.tolerations` parameter Specify parameter type as list with default value `[]` Add description for tolerations purpose	+1/-0

Tests

test.py `Add test for exporter tolerations` tests/charts/templates/test.py Add new test method `test_monitoring_exporter_tolerations` Verify tolerations are set on exporter deployment Assert tolerations key is 'dedicated' and operator is 'Exists' Validate deployment is found in rendered templates	+13/-0
dummy.yaml `Add tolerations to test fixture` tests/charts/templates/render/dummy.yaml Add exporter tolerations configuration to test fixture Set tolerations with key 'dedicated' and operator 'Exists' Enable monitoring with existing agent	+4/-0
dummy_solution.yaml `Add tolerations to expected output` tests/charts/templates/render/dummy_solution.yaml Add exporter tolerations configuration to expected output Set tolerations with key 'dedicated' and operator 'Exists' Align with dummy.yaml test fixture	+4/-0

qodo-code-review · 2026-02-22T16:02:41Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance

🟢

No security concerns identified

No security vulnerabilities detected by AI analysis. Human verification advised for critical code.

Ticket Compliance

🟡

🎫 #3058

🟢	Add missing tolerations support to the monitoring exporter Deployment so exporter pods can be scheduled (not stuck Pending) in clusters requiring tolerations.
🟢	Ensure the Helm chart exposes a configurable tolerations field for the monitoring exporter.
⚪	Validate in a real Kubernetes cluster that setting `monitoring.exporter.tolerations` unblocks scheduling for the exporter pod(s) on tainted/dedicated nodes (end-to-end Helm install/upgrade test).

Codebase Duplication Compliance

⚪

Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance

🟢

Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

qodo-code-review · 2026-02-22T16:04:27Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve test robustness by avoiding indexing Improve test robustness by checking for the presence of the expected toleration in the list, rather than relying on a hardcoded index. tests/charts/templates/test.py [504-507] tolerations = doc['spec']['template']['spec']['tolerations'] self.assertTrue(len(tolerations) > 0) -self.assertEqual(tolerations[0]['key'], 'dedicated') -self.assertEqual(tolerations[0]['operator'], 'Exists') +expected_toleration = {'key': 'dedicated', 'operator': 'Exists'} +self.assertIn(expected_toleration, tolerations) Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that testing with a hardcoded index is brittle and proposes a more robust check, improving test maintainability.	Low
General	Guard tolerations retrieval Improve the test by safely accessing the `tolerations` field using `.get()` and adding a clear assertion message. tests/charts/templates/test.py [504-505] - tolerations = doc['spec']['template']['spec']['tolerations'] - self.assertTrue(len(tolerations) > 0) + tolerations = doc['spec']['template']['spec'].get('tolerations', []) + self.assertTrue(tolerations, "Tolerations not defined on exporter deployment") Apply / Chat Suggestion importance[1-10]: 4 __ Why: The suggestion improves test robustness by safely accessing the `tolerations` key and adding a descriptive assertion message, though the current code is not incorrect.	Low
Learned best practice	Fix tolerations YAML indentation Render `tolerations` as a YAML block (newline + proper indent) and ensure it aligns under the Pod spec (same level as `containers`) to avoid producing invalid inline YAML. charts/selenium-grid/templates/monitoring-exporter-deployment.yaml [35-37] {{- with .Values.monitoring.exporter.tolerations }} - tolerations: {{ toYaml . \| nindent 6 }} + tolerations: + {{- toYaml . \| nindent 8 }} {{- end }} Apply / Chat Suggestion importance[1-10]: 6 __ Why: Relevant best practice - In Helm/YAML templates, ensure fields are rendered at the correct scope and formatted with correct indentation/newlines so the resulting YAML is valid.	Low
More

qodo-code-review · 2026-02-22T16:04:50Z

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Test Selenium Grid on Docker / Test Docker Selenium (test_video_standalone, false, true, false, ubuntu-24.04-arm, true, true)
Failed stage: Set up containerd image store feature [❌]
Failed test name: ""
Failure summary: The action failed during development environment setup because Docker Compose could not be downloaded and Docker became unusable on the runner: - In `make setup_dev_env` (`Makefile:69`), `./tests/charts/make/chart_setup_env.sh` attempted to install Docker Compose and ran: `curl -fsSL -o` `./docker-compose` `https://github.com/docker/compose/releases/download/v5.0.2/docker-compose-linux-aarch64` which repeatedly returned `curl: (22) ... 502` (Attempts 1–3), causing the script to exit with status `22` and `make ... Error 22`. - After the third attempt, the follow-up step `make set_containerd_image_store` (`Makefile:78`) tried to restart Docker (`systemctl restart docker`) but `docker.service` failed to start. - Subsequent cleanup (`docker system prune -af`) also failed with `Cannot connect to the Docker daemon` `at unix:///var/run/docker.sock`, confirming Docker was not running and causing the job to exit with code `1`.
Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 152: �[36;1m�[0m 153: �[36;1m sudo rm -rf /opt/ghc \|\| true�[0m 154: �[36;1m sudo rm -rf /usr/local/.ghcup \|\| true�[0m 155: �[36;1m �[0m 156: �[36;1m AFTER=$(getAvailableSpace)�[0m 157: �[36;1m SAVED=$((AFTER-BEFORE))�[0m 158: �[36;1m printSavedSpace $SAVED "Haskell runtime"�[0m 159: �[36;1mfi�[0m 160: �[36;1m�[0m 161: �[36;1m# Option: Remove large packages�[0m 162: �[36;1m# REF: https://github.com/apache/flink/blob/master/tools/azure-pipelines/free_disk_space.sh�[0m 163: �[36;1m�[0m 164: �[36;1mif [[ false == 'true' ]]; then�[0m 165: �[36;1m BEFORE=$(getAvailableSpace)�[0m 166: �[36;1m �[0m 167: �[36;1m sudo apt-get remove -y '^aspnetcore-.' \|\| echo "::warning::The command [sudo apt-get remove -y '^aspnetcore-.'] failed to complete successfully. Proceeding..."�[0m 168: �[36;1m sudo apt-get remove -y '^dotnet-.' --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y '^dotnet-.' --fix-missing] failed to complete successfully. Proceeding..."�[0m 169: �[36;1m sudo apt-get remove -y '^llvm-.' --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y '^llvm-.' --fix-missing] failed to complete successfully. Proceeding..."�[0m 170: �[36;1m sudo apt-get remove -y 'php.' --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y 'php.' --fix-missing] failed to complete successfully. Proceeding..."�[0m 171: �[36;1m sudo apt-get remove -y '^mongodb-.' --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y '^mongodb-.' --fix-missing] failed to complete successfully. Proceeding..."�[0m 172: �[36;1m sudo apt-get remove -y '^mysql-.' --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y '^mysql-.' --fix-missing] failed to complete successfully. Proceeding..."�[0m 173: �[36;1m sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing \|\| echo "::warning::The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding..."�[0m 174: �[36;1m sudo apt-get remove -y google-cloud-sdk --fix-missing \|\| echo "::debug::The command [sudo apt-get remove -y google-cloud-sdk --fix-missing] failed to complete successfully. Proceeding..."�[0m 175: �[36;1m sudo apt-get remove -y google-cloud-cli --fix-missing \|\| echo "::debug::The command [sudo apt-get remove -y google-cloud-cli --fix-missing] failed to complete successfully. Proceeding..."�[0m 176: �[36;1m sudo apt-get autoremove -y \|\| echo "::warning::The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding..."�[0m 177: �[36;1m sudo apt-get clean \|\| echo "::warning::The command [sudo apt-get clean] failed to complete successfully. Proceeding..."�[0m 178: �[36;1m�[0m ... 571: Created wheel for shfmt-py: filename=shfmt_py-3.12.0.2-py2.py3-none-linux_aarch64.whl size=1159515 sha256=c6689696f64706a8ceccd19f3a5aba677a77832b3d722ff9267a7a941690c0e2 572: Stored in directory: /home/runner/.cache/pip/wheels/66/0e/31/07f3204ab9acb0ee22b7cd435e6f9c07c6d996f4bacaa748a0 573: Successfully built shfmt-py 574: Installing collected packages: sortedcontainers, csv2md, yamale, websocket-client, urllib3, typing_extensions, sniffio, shfmt-py, shellingham, pytokens, pysocks, pathspec, outcome, mypy-extensions, isort, h11, click, certifi, annotated-doc, yamllint, wsproto, trio, docker, black, typer, trio-websocket, selenium, mbake 575: Successfully installed annotated-doc-0.0.4 black-26.1.0 certifi-2026.1.4 click-8.3.1 csv2md-1.5.0 docker-7.1.0 h11-0.16.0 isort-8.0.0 mbake-1.4.5 mypy-extensions-1.1.0 outcome-1.3.0.post0 pathspec-1.0.4 pysocks-1.7.1 pytokens-0.4.1 selenium-4.41.0 shellingham-1.5.4 shfmt-py-3.12.0.2 sniffio-1.3.1 sortedcontainers-2.4.0 trio-0.33.0 trio-websocket-0.12.2 typer-0.24.1 typing_extensions-4.15.0 urllib3-2.6.3 websocket-client-1.9.0 wsproto-1.3.2 yamale-6.1.0 yamllint-1.38.0 576: shfmt -l -w -d ${PWD}/.sh ${PWD}//.sh $PWD/.sh $PWD//generate_ $PWD//wrap_* 577: ##[group]Run nick-invision/retry@master 578: with: 579: timeout_minutes: 10 580: max_attempts: 3 581: command: DOCKER_ENABLE_QEMU=${DOCKER_ENABLE_QEMU} make setup_dev_env 582: 583: retry_wait_seconds: 10 584: polling_interval_seconds: 1 585: warning_on_retry: true 586: continue_on_error: false 587: ##[endgroup] 588: ##[group]Attempt 1 589: ./tests/charts/make/chart_setup_env.sh ; \ 590: exit_code=$? ; \ 591: make set_containerd_image_store ; \ 592: exit $exit_code ; 593: + echo 'Set ENV variables' 594: + CLUSTER=minikube 595: Set ENV variables 596: + DOCKER_VERSION= 597: + DOCKER_ENABLE_QEMU=true 598: + HELM_VERSION=latest 599: ++ curl -L -s https://dl.k8s.io/release/stable.txt 600: + KUBERNETES_VERSION=v1.35.1 601: + INSTALL_DOCKER=true 602: + [[ true != \t\r\u\e ]] 603: + trap on_failure ERR 604: + echo 'Installing Docker for AMD64 / ARM64' ... 933: Insecure Registries: 934: ::1/128 935: 127.0.0.0/8 936: Live Restore Enabled: false 937: Firewall Backend: iptables 938: + echo =============================== 939: + echo 'Installing Docker compose for AMD64 / ARM64' 940: + '[' -z '' ']' 941: =============================== 942: Installing Docker compose for AMD64 / ARM64 943: ++ curl -s -L -o /dev/null -w '%{url_effective}\n' https://github.com/docker/compose/releases/latest 944: ++ sed -E 's#./tag/(v[0-9.]+).#\1#' 945: + DOCKER_COMPOSE_VERSION=v5.0.2 946: ++ uname -m 947: + curl -fsSL -o ./docker-compose https://github.com/docker/compose/releases/download/v5.0.2/docker-compose-linux-aarch64 948: curl: (22) The requested URL returned error: 502 949: ++ on_failure 950: ++ local exit_status=22 951: ++ echo 'There is step failed with exit status 22' 952: ++ exit 22 953: There is step failed with exit status 22 954: make[1]: Entering directory '/home/runner/work/docker-selenium/docker-selenium' 955: sudo mkdir -p /etc/docker 956: sudo mv /etc/docker/daemon.json /etc/docker/daemon.json.bak \|\| true 957: mv: cannot stat '/etc/docker/daemon.json': No such file or directory 958: echo "{\"features\":{\"containerd-snapshotter\": true, \"containerd\": true}, \"experimental\": true}" \| sudo tee /etc/docker/daemon.json 959: {"features":{"containerd-snapshotter": true, "containerd": true}, "experimental": true} 960: sudo systemctl restart docker 961: sudo chmod 666 /var/run/docker.sock 962: docker version -f '{{.Server.Experimental}}' 963: true 964: docker info -f '{{ .DriverStatus }}' 965: [[driver-type io.containerd.snapshotter.v1]] 966: make[1]: Leaving directory '/home/runner/work/docker-selenium/docker-selenium' 967: make: *** [Makefile:69: setup_dev_env] Error 22 968: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 2 969: ##[endgroup] 970: ##[group]Attempt 2 971: ./tests/charts/make/chart_setup_env.sh ; \ 972: exit_code=$? ; \ 973: make set_containerd_image_store ; \ 974: exit $exit_code ; 975: + echo 'Set ENV variables' 976: Set ENV variables 977: + CLUSTER=minikube 978: + DOCKER_VERSION= 979: + DOCKER_ENABLE_QEMU=true 980: + HELM_VERSION=latest 981: ++ curl -L -s https://dl.k8s.io/release/stable.txt 982: + KUBERNETES_VERSION=v1.35.1 983: + INSTALL_DOCKER=true 984: + [[ true != \t\r\u\e ]] 985: + trap on_failure ERR 986: + echo 'Installing Docker for AMD64 / ARM64' ... 1204: Insecure Registries: 1205: 127.0.0.0/8 1206: ::1/128 1207: Live Restore Enabled: false 1208: Firewall Backend: iptables 1209: + echo =============================== 1210: + echo 'Installing Docker compose for AMD64 / ARM64' 1211: =============================== 1212: Installing Docker compose for AMD64 / ARM64 1213: + '[' -z '' ']' 1214: ++ curl -s -L -o /dev/null -w '%{url_effective}\n' https://github.com/docker/compose/releases/latest 1215: ++ sed -E 's#./tag/(v[0-9.]+).#\1#' 1216: + DOCKER_COMPOSE_VERSION=v5.0.2 1217: ++ uname -m 1218: + curl -fsSL -o ./docker-compose https://github.com/docker/compose/releases/download/v5.0.2/docker-compose-linux-aarch64 1219: curl: (22) The requested URL returned error: 502 1220: ++ on_failure 1221: ++ local exit_status=22 1222: ++ echo 'There is step failed with exit status 22' 1223: ++ exit 22 1224: There is step failed with exit status 22 1225: make[1]: Entering directory '/home/runner/work/docker-selenium/docker-selenium' 1226: sudo mkdir -p /etc/docker 1227: sudo mv /etc/docker/daemon.json /etc/docker/daemon.json.bak \|\| true 1228: echo "{\"features\":{\"containerd-snapshotter\": true, \"containerd\": true}, \"experimental\": true}" \| sudo tee /etc/docker/daemon.json 1229: {"features":{"containerd-snapshotter": true, "containerd": true}, "experimental": true} 1230: sudo systemctl restart docker 1231: sudo chmod 666 /var/run/docker.sock 1232: docker version -f '{{.Server.Experimental}}' 1233: true 1234: docker info -f '{{ .DriverStatus }}' 1235: [[driver-type io.containerd.snapshotter.v1]] 1236: make[1]: Leaving directory '/home/runner/work/docker-selenium/docker-selenium' 1237: make: *** [Makefile:69: setup_dev_env] Error 22 1238: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 2 1239: ##[endgroup] 1240: ##[group]Attempt 3 1241: ./tests/charts/make/chart_setup_env.sh ; \ 1242: exit_code=$? ; \ 1243: make set_containerd_image_store ; \ 1244: exit $exit_code ; 1245: + echo 'Set ENV variables' 1246: + CLUSTER=minikube 1247: Set ENV variables 1248: + DOCKER_VERSION= 1249: + DOCKER_ENABLE_QEMU=true 1250: + HELM_VERSION=latest 1251: ++ curl -L -s https://dl.k8s.io/release/stable.txt 1252: + KUBERNETES_VERSION=v1.35.1 1253: + INSTALL_DOCKER=true 1254: + [[ true != \t\r\u\e ]] 1255: + trap on_failure ERR 1256: + echo 'Installing Docker for AMD64 / ARM64' ... 1460: Insecure Registries: 1461: ::1/128 1462: 127.0.0.0/8 1463: Live Restore Enabled: false 1464: Firewall Backend: iptables 1465: + echo =============================== 1466: + echo 'Installing Docker compose for AMD64 / ARM64' 1467: + '[' -z '' ']' 1468: =============================== 1469: Installing Docker compose for AMD64 / ARM64 1470: ++ curl -s -L -o /dev/null -w '%{url_effective}\n' https://github.com/docker/compose/releases/latest 1471: ++ sed -E 's#./tag/(v[0-9.]+).#\1#' 1472: + DOCKER_COMPOSE_VERSION=v5.0.2 1473: ++ uname -m 1474: + curl -fsSL -o ./docker-compose https://github.com/docker/compose/releases/download/v5.0.2/docker-compose-linux-aarch64 1475: curl: (22) The requested URL returned error: 502 1476: ++ on_failure 1477: ++ local exit_status=22 1478: ++ echo 'There is step failed with exit status 22' 1479: ++ exit 22 1480: There is step failed with exit status 22 1481: make[1]: Entering directory '/home/runner/work/docker-selenium/docker-selenium' 1482: sudo mkdir -p /etc/docker 1483: sudo mv /etc/docker/daemon.json /etc/docker/daemon.json.bak \|\| true 1484: echo "{\"features\":{\"containerd-snapshotter\": true, \"containerd\": true}, \"experimental\": true}" \| sudo tee /etc/docker/daemon.json 1485: {"features":{"containerd-snapshotter": true, "containerd": true}, "experimental": true} 1486: sudo systemctl restart docker 1487: Job for docker.service failed. 1488: See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. 1489: make[1]: * [Makefile:78: set_containerd_image_store] Error 1 1490: make[1]: Leaving directory '/home/runner/work/docker-selenium/docker-selenium' 1491: make: * [Makefile:69: setup_dev_env] Error 22 1492: ##[endgroup] 1493: ##[error]Final attempt failed. Child_process exited with error code 2 1494: ##[group]Run docker system prune -af 1495: �[36;1mdocker system prune -af�[0m 1496: shell: /usr/bin/bash -e {0} 1497: ##[endgroup] 1498: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? 1499: ##[error]Process completed with exit code 1. 1500: Post job cleanup.

K8s: Missing tolerations for monitoring exporter deployment

87e3d98

qodo-code-review Bot added the Review effort 2/5 label Feb 22, 2026

VietND96 merged commit 56e0192 into trunk Feb 22, 2026
26 of 28 checks passed

VietND96 deleted the exporter-chart branch February 22, 2026 16:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

K8s: Missing tolerations for monitoring exporter deployment#3086

K8s: Missing tolerations for monitoring exporter deployment#3086
VietND96 merged 1 commit into
trunkfrom
exporter-chart

VietND96 commented Feb 22, 2026 •

edited

Loading

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

VietND96 commented Feb 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

Description

Motivation and Context

Types of changes

Checklist

PR Type

Description

Diagram Walkthrough

File Walkthrough

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

PR Compliance Guide 🔍

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

PR Code Suggestions ✨

Uh oh!

qodo-code-review Bot commented Feb 22, 2026

CI Feedback 🧐

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

VietND96 commented Feb 22, 2026 •

edited

Loading