Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: extended ping interval to 100s in WS server #2406

Merged
merged 1 commit into from
Apr 25, 2024

Conversation

quiet-node
Copy link
Collaborator

Description:
This PR extends the ping interval to 100 seconds in the WS server so the server sends a null response back to client after 100 seconds

misc: renamed one of the test case which was incorrect

Related issue(s):

Temporarily Fixes #2359

Notes for reviewer:

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

@quiet-node quiet-node self-assigned this Apr 24, 2024
@quiet-node quiet-node added the bug Something isn't working label Apr 24, 2024
Signed-off-by: Logan Nguyen <logan.nguyen@swirldslabs.com>
Copy link

sonarcloud bot commented Apr 24, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

Tests

    2 files  147 suites   13s ⏱️
818 tests 817 ✔️ 1 💤 0
830 runs  829 ✔️ 1 💤 0

Results for commit 33c6df9.

Copy link

github-actions bot commented Apr 24, 2024

Acceptance Tests

     31 files     461 suites   48m 34s ⏱️
   583 tests    570 ✔️   3 💤 10
2 017 runs  1 971 ✔️ 21 💤 25

Results for commit 33c6df9.

♻️ This comment has been updated with latest results.

@quiet-node quiet-node merged commit c118b6a into main Apr 25, 2024
32 checks passed
@quiet-node quiet-node deleted the extend-ping-interval branch April 25, 2024 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WS socket repetitively responds with null responses when subcribed
2 participants