Skip to content

fix the issue with the 'ReadMessage' thread not exiting when 'stopCh' is triggered #24

fix the issue with the 'ReadMessage' thread not exiting when 'stopCh' is triggered

fix the issue with the 'ReadMessage' thread not exiting when 'stopCh' is triggered #24

Triggered via pull request October 1, 2024 16:33
Status Failure
Total duration 36s
Artifacts

connector.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
UnitTest: websocket_service_test.go#L25
cannot assign to wsServe (neither addressable nor a map index expression)
UnitTest: websocket_service_test.go#L30
cannot assign to wsServe (neither addressable nor a map index expression)
UnitTest
Process completed with exit code 1.
Checks
cannot assign to wsServe (neither addressable nor a map index expression)
Checks
Process completed with exit code 1.
UnitTest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Checks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/