Skip to content

Identify "failed to read status" as ErrorKind::Connection errors #91

Identify "failed to read status" as ErrorKind::Connection errors

Identify "failed to read status" as ErrorKind::Connection errors #91

Triggered via push May 29, 2024 18:07
Status Success
Total duration 11m 40s
Artifacts

rust.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
nix
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.