Skip to content

Add Redis connection error handling in GetAndRefresh - #68182

Closed
4bitsteams wants to merge 6 commits into
dotnet:mainfrom
4bitsteams:feature/redis-cache-error-handling
Closed

Add Redis connection error handling in GetAndRefresh#68182
4bitsteams wants to merge 6 commits into
dotnet:mainfrom
4bitsteams:feature/redis-cache-error-handling

Conversation

@4bitsteams

Copy link
Copy Markdown

Summary

Implement error handling for Redis operations in the GetAndRefresh method by wrapping hash member get operations in try-catch.

  • Handles Redis connection failures gracefully
  • Addresses TODO for error handling in cache retrieval
  • Improves cache layer reliability

Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

Elfocrash and others added 6 commits May 12, 2022 12:21
Co-authored-by: Weihan Li <weihanli@outlook.com>
Complete the OpenAPI dotnet-openapi tool by registering the AddProjectCommand that was previously implemented but not wired up. This enables users to add OpenAPI references from project files.
Use the more accurate UrlDecoder for URL form data decoding instead of Uri.UnescapeDataString which has known limitations with UTF-8 sequences and cross-platform behavior differences.
Implement error handling for Redis operations in the GetAndRefresh method
by wrapping hash member get operations in try-catch to handle Redis
connection failures gracefully. This addresses the TODO for error handling
in cache retrieval operations.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@dotnet-policy-service dotnet-policy-service Bot added the community-contribution Indicates that the PR has been added by a community member label Aug 3, 2026
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Thanks for your PR, @4bitsteams. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

@4bitsteams

Copy link
Copy Markdown
Author

community-contribution

@BrennanConroy

Copy link
Copy Markdown
Member

Thanks for your interest in contributing. We will not be moving forward with this PR. It has no associated issue, contains unrelated changes, and as we've said multiple times - please review our contribution guidelines before submitting pull requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants