-
Notifications
You must be signed in to change notification settings - Fork 734
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
Cleanup Socket/SocketPoll 'Limited open Connections' Changes #10265
Conversation
f97d0ee
to
1f4819a
Compare
Unrelated UT error to this PR (from initial push, pre 1st rebase to master) unit-wopi-languages:
Not reproduced here locally -> a new instability? |
cypress test usual failure writer/invalidations_spec.js |
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.
"Socket checkRemoval and handlePoll must be public" - surely they already were - there is no change in their visibility here surely. Please remove this apparently redundant commit that just shuffles code. Fixing the unexpectedly long and poorly wrapped comment on checkRemoval would be good in a follow-up. I'd really prefer to see a single clean fix for the bug at hand that we can merge separated from other stuff.
Similarly - the "WebSocketHandler Logging: Use LOG_DBG for low-frequency ping/pong logging (was LOGA_TRC for high-frequency), use common prefix "Ping:"" - seems like it pops out a lot of underlying channel debugging that should not be necessary. Our websocket & socket channel code has been working extremely well for a long time now - sure if we broke it we need to turn logging on for a bit; the prefix is fine - a debugging patch is fine - but we really shouldn't have great swathes of Pinging going into the logs unless it is enabled. Please use LOGA_DBG if you think it should be a higher level.
I will split out the fix patch I guess so we can merge something fast here.
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.
With the split out fix merged; we have time to improve this I think as per comments.
76cc25c
to
6f98df7
Compare
Yes both were public in the base class, yes checkRemoval was also public in StreamSocket However: Hence this is now a smaller cleanup fix.
OK
Thanks! |
6f98df7
to
c6d5a88
Compare
…override Signed-off-by: Sven Göthel <[email protected]> Change-Id: I035ab196e57588513b69894ccc669d88cec488c2
…less `now < getCreationTime()` criteria. Signed-off-by: Sven Göthel <[email protected]> Change-Id: I035ab196e57588513b69894ccc669d88cec488c2
c6d5a88
to
79d4d05
Compare
Summary
Originally contained PR #10270 fixing a regression caused by PR #9916, leading to 100% CPU utilization on idle,
due to WebSocketHandler's checkTimeout not being called and hence no ping sent.
This PR contains remaining cleanups related to PR #9916
Checklist
make prettier-write
and formatted the code.make check
make run
and manually verified that everything looks okay