Skip to content

webrtc: fix connection timeout when webrtcAdditionalHosts is filled with existing IP #1101

webrtc: fix connection timeout when webrtcAdditionalHosts is filled with existing IP

webrtc: fix connection timeout when webrtcAdditionalHosts is filled with existing IP #1101

Triggered via pull request October 6, 2024 11:57
@aler9aler9
synchronize #3835
fix/webrtc-add
Status Success
Total duration 47s
Artifacts

code_lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
golangci_lint
Cannot open: File exists
mod_tidy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
golangci_lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
golangci_lint
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2