fix: don't use invalid port 0 when NATMap fails #7810
Annotations
10 errors and 2 warnings
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Cannot open: File exists
|
|
Set up the Go version read from the go.mod file
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "macos_1.22.x_test_results.db", "macos_1.23.x_test_results.db", "ubuntu_1.22.x_test_results.db", "ubuntu_1.22.x_test_results_race.db", "ubuntu_1.23.x_test_results.db", "ubuntu_1.23.x_test_results_race.db", "windows_1.22.x_test_results.db", "windows_1.23.x_test_results.db".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading