Skip to content

Add an unsafe flag so we can continue to use unsafe even when purego … #84

Add an unsafe flag so we can continue to use unsafe even when purego …

Add an unsafe flag so we can continue to use unsafe even when purego … #84

Re-run triggered August 20, 2024 07:57
Status Success
Total duration 2m 42s
Artifacts

validate.yml

on: pull_request
Matrix: linters
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
linters (1.22.x, ubuntu-latest)
TestHidden: Bad: ignored
linters (1.22.x, ubuntu-latest)
NonMsgStructTags: C: ignored
linters (1.22.x, ubuntu-latest)
tuple: Object
linters (1.22.x, ubuntu-latest)
tuple: TestBench
linters (1.22.x, ubuntu-latest)
tuple: TestFast
linters (1.22.x, ubuntu-latest)
shim: SpecialID -> Bytes
linters (1.22.x, ubuntu-latest)
shim: MyEnum -> String
linters (1.22.x, ubuntu-latest)
shim: os.File -> String
linters (1.22.x, ubuntu-latest)
FileHandle: inlining Files
linters (1.22.x, ubuntu-latest)
Insane: inlining CustomInt
linters (1.22.x, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v3, actions/checkout@v3, golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/