Skip to content

fix: resolve data races, integer overflow, panics, and resource leaks #85

fix: resolve data races, integer overflow, panics, and resource leaks

fix: resolve data races, integer overflow, panics, and resource leaks #85

Triggered via push April 4, 2026 18:48
Status Failure
Total duration 1m 49s
Artifacts 1

ci.yml

on: push
Matrix: build-c-sdk
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

63 errors and 11 warnings
Lint: cmd/eipc-client/main.go#L144
expected declaration, found 'if' (typecheck)
Lint: cmd/eipc-client/main.go#L115
expected declaration, found chalRespPayload (typecheck)
Lint: cmd/eipc-client/main.go#L103
expected declaration, found 'if' (typecheck)
Lint: cmd/eipc-client/main.go#L97
expected ';', found 'else' (typecheck)
Lint: core/endpoint.go#L165
syntax error: non-declaration statement outside function body) (typecheck)
Lint: core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Lint: core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Lint: core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Lint: core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Lint: cmd/eipc-cli/main.go#L22
could not import github.com/embeddedos-org/eipc/core (-: # github.com/embeddedos-org/eipc/core
Benchmarks: core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Benchmarks: core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Benchmarks: core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Benchmarks: core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Benchmarks: core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Benchmarks: core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Benchmarks: core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Benchmarks: core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Benchmarks: core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Benchmarks: core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (macos-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (macos-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (macos-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (macos-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (macos-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (macos-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (ubuntu-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (ubuntu-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (ubuntu-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (ubuntu-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (ubuntu-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (ubuntu-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (windows-latest)
Process completed with exit code 1.
C SDK (macos-latest)
Process completed with exit code 2.
Test (macos-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (macos-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (macos-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (macos-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (macos-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (macos-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (macos-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (macos-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (ubuntu-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (ubuntu-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (ubuntu-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L165
syntax error: non-declaration statement outside function body
Test (ubuntu-latest): core/endpoint.go#L162
syntax error: unexpected :, expected := or = or comma
Test (ubuntu-latest): core/endpoint.go#L159
syntax error: unexpected defer at end of statement
Test (ubuntu-latest): core/endpoint.go#L158
syntax error: unexpected newline in composite literal; possibly missing comma or }
Test (ubuntu-latest): core/endpoint.go#L136
syntax error: non-declaration statement outside function body
Test (windows-latest)
Process completed with exit code 1.
C SDK (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, golangci/golangci-lint-action@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Benchmarks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
C SDK (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Fuzz Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
benchmarks Expired
432 Bytes
sha256:88d3c101e6153883d26e086eb07725443e8e8a34602ced307f0e0935d597e9d7