antirez / antirez/neural-redis

Unexpected behaviour with NR.OBSERVE in multi

Open
#8 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
2.2k
Forks
100
PR merge metrics
No merged PRs in 30d

Description

`NR.OBSERVE` doesn't reject the wrong number of arguments when in a `MULTI`. Here I'm running `NR.OBSERVE` with no arguments.

```
> MULTI
OK
> NR.OBSERVE
QUEUED
> NR.OBSERVE
QUEUED
> EXEC
1) (error) ERR wrong number of arguments for 'nr.observe' command
2) (error) ERR wrong number of arguments for 'nr.observe' command
```

I would expect that if you run `NR.OBSERVE` you would receive an immediate error and/or trigger an `EXECABORT` when running the `EXEC` command.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.