Passing in a existing memcached client ignores the secret option
See original GitHub issueI have a project that already has a memcached instance created, yet when adding connect-memcached, it will create a new instance of the client but i wanted to use the existing instance
Took a look at the code and i see i can pass in a client at MemcachedStore(), but for some reason in case a client is passed the secret option is ignored:
Shouldn’t the if (options.secret) block be outside the if (!options.client)?
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Regarding setting up SASL with memcached server and ...
Yes...that's the thing I was wondering, 'no secret in database' means its able to reach the database, but unable to read/load the memcached-sasl-pwdb...
Read more >Configuration — Beaker 1.9.0 documentation
Cache Region Options This should generally be used when testing an application or in development when caching should be ignored. Defaults to True....
Read more >Simple session middleware for Express - GitHub
Using a secret that cannot be guessed will reduce the ability to hijack a session to only guessing the session ID (as determined...
Read more >Grafana Mimir configuration parameters
To do this, pass -config.expand-env=true on the command line and use ${VAR} , where VAR is the name of the environment variable.
Read more >Configuration Options | Directus Docs
How to scope the cache data. Where to store the cache data. Either memory , redis , or memcache . If set, returns...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

FYI I’m planning to add your case as a test, for this purpose I’ve migrated test “suite” from manual scripts to Jest. Next steps in progress.
small update: working on merging this pr, which will also fix this issue along the way