rueidis: DragonflyDB 1.1.2: panic: protocol bug, message handled out of order

Hello:)

On local run came across:

panic: protocol bug, message handled out of order

goroutine 104 [running]:
github.com/rueian/rueidis.(*pipe)._backgroundRead(0xc000114120)
	/Users/fz/go/pkg/mod/github.com/rueian/rueidis@v0.0.90/pipe.go:425 +0x868
github.com/rueian/rueidis.(*pipe)._background(0xc000114120)
	/Users/fz/go/pkg/mod/github.com/rueian/rueidis@v0.0.90/pipe.go:228 +0x7e
created by github.com/rueian/rueidis.(*pipe).background.func1
	/Users/fz/go/pkg/mod/github.com/rueian/rueidis@v0.0.90/pipe.go:212 +0x5a
exit status 2

Also reproduces with DF v1.1.1 and v1.1.0

I think the issue caused by RESP3 support added to DragonflyDB in v1.1.0.

DF now runs in Docker even on MacOS BTW (falling back to epoll where uring is not supported):

docker run -p 6379:6379 --rm -it docker.dragonflydb.io/dragonflydb/dragonfly:v1.1.2

About this issue

Original URL
State: closed
Created a year ago
Comments: 16 (8 by maintainers)

Most upvoted comments

Many thanks for super quick response! I think having a way to force RESP2 would be a good thing in general. At least it will be a working workaround while DF have not fixed the protocol.

FZambia on Apr 8, 2023