Using `info` or `config` in a `multi/exec`
See original GitHub issueI have just migrated from node_redis
. I had a check script that did the following:
redis.multi()
.info()
.config('get', 'maxmemory')
.exec()
.then(console.log) //works in node_redis, outputs [] in ioredis
Running the commands individually works (not using multi
). Is this by design? I only used the multi in the first place to reduce a bit of nesting as I need to munge the results.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to implement Redis Multi-Exec by using Spring-data-Redis
Here is a quick summary of doing transactions with Spring Data Redis: ... For your case, scroll down and look at "Optimistic locking...
Read more >MULTI - Redis
Quick search&hellip… Search… ⌘ K Download Try Redis Cloud. Open main menu. Commands · ACL CAT · ACL DELUSER · ACL DRYRUN ·...
Read more >curl_multi_exec - Manual - PHP
This function wait for the last page, can get a configuration array with curl options to made a post, or pass timeouts, etc....
Read more >Multi-Exec for Multi-Specialty Practices - DSN software
Effectively interact, collaborate and grow your multi-specialty practice with cloud-based software that transforms your workflows and elevates patient care.
Read more >Tips - Using The Command Window To ... - VanDyke Software
Start sessions in tabbed windows or drag several sessions into the same SecureCRT window. Use a special Command window setting to distribute one...
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 FreeTop 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
Top GitHub Comments
Thank for the report! I just confirmed this is a bug due to a race condition. It happens when sending pipeline/transaction that includes
info
orconfig
command on the"connect"
event.I’m going to fix this today. BTW, It’s recommended to handle the
"ready"
event instead of the"connect"
event, since the latter one is a low level event emitted by the “net” module directly.closing this as it’s fixed