Skip to content

command processing seems to mess up its index while reading arguments #5

Description

@cinnay

There seems to be some index(?) issue somewhere in the cluster command processing.

I get a couple of error of these kinds:

RedisError: ERR unknown command bkt:-72:-396, with args beginning with:
at processTicksAndRejections (internal/process/task_queues.js:85:5) {
name: 'RedisError'
}
Edit: bkt:-72:-396 should be the key here, not the command.

RedisError: ERR unknown command 1, with args beginning with:
at processTicksAndRejections (internal/process/task_queues.js:85:5) {
name: 'RedisError'
}

RedisError: ERR Protocol error: expected '$', got ' '
at processTicksAndRejections (internal/process/task_queues.js:85:5) {
name: 'RedisError'
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions