running dump() fails when decode_responses=True in a pipeline

[brianmaissy]

This is an extension of issue #1254, which was partially (but I belive not fully) resolved in #1731.

I think that when non-decodable commands are called from within a pipeline, they are decoded anyway.

See my comment on the original issue here: #1254 (comment)

[dvora-h]

HI @brianmaissy
This is a real bug, but however it doesn't make sense to use one of these commands in a pipeline, so for now we will leave it as an open bug.

[brianmaissy]

Why doesn't it make sense to use dump() in a pipeline? I do so in order to dump multiple keys.

[chayim]

@brianmaissy We should support this (and don't today), the best answer is to use a connection where deconde_responses is False. While I realize this isn't ideal, this is the best current answer.

tl;dr yes a bug we should fix in the future, and labelled accordingly.

[brianmaissy]

Yeah that's the workaround I've been using. Thank you.

[chayim]

Since we added the NEVER_DECODE target as part of another bug - closing this off. It works now.

[brianmedigate]

in what version is it fixed?

[chayim]

I think > 4.0.1. @dvora-h am I right?

[brianmedigate]

I'm using 4.3.4, but it still doesn't work when the non-decodable command is used in a pipeline

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.

[brianmedigate]

@chayim @dvora-h can you please confirm that this is still open?

[dvora-h]

@brianmaissy Yes

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.

[brianmedigate]

AFAIC this is still an issue

[petyaslavova]

Hi @brianmedigate the dump command works without issues if you don't run your pipeline in transaction mode (client.pipeline(transaction=False)). Would that work for your use case?

[brianmedigate]

Maybe. But shouldn't this be fixable regardless?