Skip to content

Fixing error handling of connection buffer purging of closed connecton. Enabling troubleshooting logging for maint notifications e2e tests.#3971

Merged
petyaslavova merged 3 commits intomasterfrom
ps_integrate_hitless_scenario_tests_with_scneario_runs_repo
Feb 20, 2026
Merged

Fixing error handling of connection buffer purging of closed connecton. Enabling troubleshooting logging for maint notifications e2e tests.#3971
petyaslavova merged 3 commits intomasterfrom
ps_integrate_hitless_scenario_tests_with_scneario_runs_repo

Conversation

@petyaslavova
Copy link
Copy Markdown
Collaborator

No description provided.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses error handling issues in connection buffer purging when connections are closed concurrently, and enables debug-level logging for maintenance notifications end-to-end tests to improve troubleshooting capabilities.

Changes:

  • Fixed AttributeError when purging connection buffer after a connection is closed by another thread during read operation
  • Added debug logging for ConnectionError and TimeoutError exceptions in cluster command execution
  • Enabled DEBUG level logging for redis.maint_notifications and redis.cluster loggers in maintenance notification tests

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
redis/_parsers/resp3.py Added try-except block to handle AttributeError when buffer is closed during purge operation, and changed buffer None checks to explicit 'is not None' comparisons
redis/cluster.py Added debug logging when ConnectionError or TimeoutError occurs, including socket address, command arguments, node name, and error details
tests/test_scenario/test_maint_notifications.py Enabled DEBUG level logging for redis.maint_notifications and redis.cluster loggers to facilitate troubleshooting

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 20, 2026

@petyaslavova I've opened a new pull request, #3972, to work on those changes. Once the pull request is ready, I'll request review from you.

* Initial plan

* Combine None check with try-except for buffer.purge() to handle race condition

Co-authored-by: petyaslavova <194077574+petyaslavova@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: petyaslavova <194077574+petyaslavova@users.noreply.github.com>
@petyaslavova petyaslavova added the maintenance Maintenance (CI, Releases, etc) label Feb 20, 2026
@petyaslavova petyaslavova merged commit 5f4ded8 into master Feb 20, 2026
120 of 121 checks passed
@petyaslavova petyaslavova deleted the ps_integrate_hitless_scenario_tests_with_scneario_runs_repo branch February 20, 2026 13:45
petyaslavova added a commit that referenced this pull request Feb 25, 2026
…n. Enabling troubleshooting logging for maint notifications e2e tests. (#3971)

* Fixing error handling of connection buffer purging of closed connection. Enabling troubleshooting logging for maint notifications e2e tests.

* Fix race condition in RESP3 parser buffer purge (#3972)

* Initial plan

* Combine None check with try-except for buffer.purge() to handle race condition

Co-authored-by: petyaslavova <194077574+petyaslavova@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: petyaslavova <194077574+petyaslavova@users.noreply.github.com>

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: petyaslavova <194077574+petyaslavova@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Maintenance (CI, Releases, etc)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants