fix(examples): cache-handler-redis implementation may cause error "Socket already opened" on production
#61978
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AkifumiSato
requested review from
manovotny and
molebox
and removed request for
a team
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
AkifumiSato
deleted the
cache-handler-redis-exmaple-patch-socket-error
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What?
I copied the contents of
cache-handler.jsand tried it, and got an error"Socket already opened".ref: caching-tools/next-shared-cache#284
It should be fixed so that it doesn't matter if it is copied.
Why?
Because
Socket already opened, so a condition is needed beforeawait client.connect().How?
Add environment variable(
process.env.REDIS_AVAILABLE) check.ref: https://caching-tools.github.io/next-shared-cache/configuration/opt-out-cache-on-build