Working with the neural-redis module, I came across a strange handling of module commands with incorrect arguments inside a MULTI.

Example:

> 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 (or any module command) you would receive an immediate error and/or trigger an EXECABORT when running the EXEC command as with the in-built Redis commands.

(Cross posted from antirez/neural-redis#8 as @itamarhaber indicates that this is a problem with the modules API rather than neural-redis specifically)