Skip to content

fix: Fix potential panic in receiver if a connection is lost #131

fix: Fix potential panic in receiver if a connection is lost

fix: Fix potential panic in receiver if a connection is lost #131

Triggered via push July 30, 2024 07:28
Status Success
Total duration 6m 8s
Artifacts

copr-testing.yml

on: push
Release Log Courier
5m 1s
Release Log Courier
Release Log Carver
5m 13s
Release Log Carver
Release Administration Utility
5m 57s
Release Administration Utility
Release SSL Certificate Utility
5m 29s
Release SSL Certificate Utility
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Release Log Courier
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release Log Carver
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release SSL Certificate Utility
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Release Administration Utility
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/