Skip to content

[!] close connection with PROTOCOL_VIOLATION when receiving packets containing no frames #344

[!] close connection with PROTOCOL_VIOLATION when receiving packets containing no frames

[!] close connection with PROTOCOL_VIOLATION when receiving packets containing no frames #344

Triggered via pull request December 12, 2023 13:47
@KulskKulsk
synchronize #384
Kulsk:main
Status Success
Total duration 17m 17s
Artifacts

build.yml

on: pull_request
Matrix: Build on macOS
Matrix: Build on Ubuntu
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build on macOS (macos-11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 on macOS (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 on Ubuntu (ubuntu-20.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 on Ubuntu (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/