-
Notifications
You must be signed in to change notification settings - Fork 19
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
[Sentinel] Remove ws delay checker #2319
Conversation
📝 Walkthrough📝 WalkthroughWalkthroughThe changes in this pull request involve significant modifications to the WebSocket handling logic within the Changes
Possibly related PRs
Suggested reviewers
Warning Rate limit exceeded@nick-bisonai has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 32 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (3)
node/pkg/checker/dal/app.go (3)
121-121
: Consider renaming wsDelayAlarmCount for claritySince we're now only checking push offsets (as per PR objective), the variable name
wsDelayAlarmCount
might be misleading. Consider renaming it towsPushOffsetAlarmCount
or similar to better reflect its current purpose.- checkDalWs(wsDelayAlarmCount) + checkDalWs(wsPushOffsetAlarmCount)
195-199
: Enhance logging clarityThe log messages could be more specific about what's being checked, especially since we've removed the delay checker functionality.
- log.Debug().Msg("checking WebSocket message push") + log.Debug().Msg("checking WebSocket push offset thresholds")
Clean up unused delay-related constants
The constant
WsDelayThreshold
appears to be unused in the codebase and can be safely removed. WhileDelayOffset
is still being used in the delay checking logic incheckDal
, this entire delay checking logic should also be removed for consistency since we've moved to push offset checking.
- Remove
WsDelayThreshold
constant fromnode/pkg/checker/dal/types.go
as it's unused- Remove
DelayOffset
constant and the related delay checking logic incheckDal
function- Consider renaming remaining variables like
wsDelayAlarmCount
towsPushAlarmCount
for consistency🔗 Analysis chain
Line range hint
1-265
: Verify removal of unused constants and typesSince we've removed the delay checker functionality, let's verify if there are any unused constants or types that should also be cleaned up.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for potentially unused delay-related constants and types echo "Searching for delay-related constants and types..." rg -n "Delay|delay" --type go # Search for any TODO or FIXME comments that might be related echo "Checking for related TODO/FIXME comments..." rg -n "TODO|FIXME" --type goLength of output: 6735
Script:
#!/bin/bash # Let's check if DelayOffset and WsDelayThreshold are used anywhere else echo "Checking usage of DelayOffset..." ast-grep --pattern 'DelayOffset' echo "Checking usage of WsDelayThreshold..." ast-grep --pattern 'WsDelayThreshold' # Let's also check for any references to these constants in test files echo "Checking test files for delay-related constants..." rg -n "DelayOffset|WsDelayThreshold" --type go --glob "*_test.go"Length of output: 634
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (3)
node/pkg/checker/dal/app.go
(3 hunks)node/pkg/checker/dal/app_test.go
(0 hunks)node/pkg/checker/dal/types.go
(0 hunks)
💤 Files with no reviewable changes (2)
- node/pkg/checker/dal/app_test.go
- node/pkg/checker/dal/types.go
Description
Remove buggy check, leave only push offset checker
Type of change
Please delete options that are not relevant.
Checklist before requesting a review
Deployment