Refactor: Handle connection error gracefully in antiCheatTest #163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request refactors the
antiCheatTest
function to handle connection errors gracefully. Previously, if there was an error connecting to the Redis server, the function would log a critical error and return a failure. Now, if there is an error connecting to the server, the function will simply return without logging any errors. This change improves the robustness of the code and allows the anti-cheat functionality to be skipped if the Redis server is not available.