Make chip fault tolerant to losing connectivity to Redis/Valkey #25
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 PR makes the chip service resilient to Redis/Valkey connectivity issues, allowing it to continue operating even when the Redis backend becomes unavailable.
Changes Made
1. Optional Redis Connection at Startup
cmd/chipserver/main.go
to continue startup even if Redis connection failsnil
2. Graceful Redis Operation Handling
WithRedisConn
helper method toruntime.Runtime
that:3. Fault-Tolerant Service Methods
Updated all Redis-dependent service methods to use graceful error handling:
StartChat()
- continues without setting ready state in RedisConfirmDelivery()
- continues without recording sent statusCloseChat()
- continues without unsetting ready stateQueueMsgOut()
- continues without queuing to Redissend()
- skips sending when Redis unavailableBehavior Changes
When Redis is Available: No functional changes - operates normally
When Redis is Unavailable:
When Redis Recovers: Service automatically resumes Redis operations
Testing
Added unit tests to verify Redis fault tolerance behavior works correctly when the Redis pool is
nil
or operations fail.This change ensures chip remains operational during Redis outages, providing degraded but functional service until Redis connectivity is restored.
Fixes #21.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.