Skip to content

Improve fallback host resolution in connection logic #1910

Improve fallback host resolution in connection logic

Improve fallback host resolution in connection logic #1910

Triggered via pull request September 14, 2026 09:17
Status Success
Total duration 3m 6s
Artifacts –

check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
check
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-java@17f84c3641ba7b8f6deff6309fc4c864478f5d62, gradle/actions/setup-gradle@d9c87d481d55275bb5441eef3fe0e46805f9ef70. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check
Failed to restore gradle-home-v1|Linux|check[076db07b196ebff3e745ee0285f5ef6c]-6b03d608bd0e85c1173dba6cb4f033e2af9a4f27: Error: Cache service responded with 400