Skip to content

fix concurrent map write error caused by reusing a mapstr.M #1

fix concurrent map write error caused by reusing a mapstr.M

fix concurrent map write error caused by reusing a mapstr.M #1

Triggered via push September 19, 2024 08:16
Status Success
Total duration 2m 31s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 warning
check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/