-
Notifications
You must be signed in to change notification settings - Fork 292
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
Code Health | Cleanup SNIMARSConnection
#1985
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1985 +/- ##
==========================================
+ Coverage 70.59% 70.95% +0.36%
==========================================
Files 306 306
Lines 61667 64036 +2369
==========================================
+ Hits 43533 45437 +1904
- Misses 18134 18599 +465
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 15 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
/azurepipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
test failure is the usual unreliable reliability test and 3 legs failed to configure their firewall. |
/azurepiplines run |
SNIMARSConnection
SNIMARSConnection
In #933 many changes were made to SNIMarsConnection which were then lost when that PR was reverted. This PR implements the harmless and side-effect-less changes such as using scoped event tracing like the rest of SNI does, cleaning up a class name variable and adding a dedicated sync object (there are no locks on instances of this class outside this file, i've checked).
This does not change the demuxing code in any way. I want to get the files cleaned up and then try again with the muxing code in a future PR. this is a simple way to get easy changes in place minimizing review complexity.