Skip to content

fix(client): fetch maximum datagram size after TUN read (#24) #86

fix(client): fetch maximum datagram size after TUN read (#24)

fix(client): fetch maximum datagram size after TUN read (#24) #86

Triggered via push September 26, 2023 14:19
Status Success
Total duration 51s
Artifacts

rust.yaml

on: push
Matrix: Check code style
Matrix: Test crate
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Check code style (ubuntu-latest, stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check code style (ubuntu-latest, nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test crate (ubuntu-latest, stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test crate (ubuntu-latest, nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/