StackExchange / StackExchange/StackExchange.Redis

StreamRead always return message info

Open
#1,887 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

❔ question 💬 needs-info
Dominant language
C#
Stars
6.2k
Forks
1.6k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

I have executed db.StreamRead(ZikeyStream, position: StreamPosition.Beginning) many times. And it always return message info.
It should return null because all messages have consumed. I executed the command xread streams Zikey 0-0 on redis-cli, it returns nil. Is this a bug?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the StreamRead API and reproduce the reported behavior with the Zikey stream at StreamPosition.Beginning. Compare its result with the redis-cli xread streams Zikey 0-0 response, then determine whether the client should return null when all messages are consumed; done means the behavior is clarified and covered by a regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, redis
Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.