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
Websocket: Simplify the connectionMonitor #1502
base: master
Are you sure you want to change the base?
Websocket: Simplify the connectionMonitor #1502
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1502 +/- ##
==========================================
- Coverage 37.75% 37.74% -0.02%
==========================================
Files 411 411
Lines 147817 147804 -13
==========================================
- Hits 55815 55794 -21
- Misses 84218 84219 +1
- Partials 7784 7791 +7
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Beadko Fine work. This is a much better approach. Just some nits and feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Beadko Just waiting on these changes that was laid out from gk
It should be the choice of the caller whether a routine is in a goro. Removes state tracking and instead ensures that the dataMonitor dies with the websocket
It should be the choice of the caller whether a routine is in a goro. Removes state tracking and instead ensures that the trafficMonitor dies with the websocket
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update, this is deadlocked by dataMonitor not being called in a go routine. Please update and retest. Once that is updated it then it looks good to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing removing the deadlock. There some more things that need to be done and then it should be good to go. Well done.
There are some race issues in the ci build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes, there is a deadlock introduced in the tests. Then everything else looks good to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Beadko Nice clean! Thanks. tACK.
PR Description
Currently, the WebSocket connectionMonitor is adding concurrency within the function. According to google styleguide, the caller should add the concurrency to the function.
Fixes # (issue)
Type of change
Please delete options that are not relevant and add an
x
in[]
as item is complete.How has this been tested
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration and
also consider improving test coverage whilst working on a certain feature or package.
Checklist