Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Memory session store replays nothing when Last-Event-ID has been trimmed

Open Beginner friendly
  • Is something wrong?
#368 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend, distributed-systems

Research direction

Start with MemorySessionStore.getMessagesFrom and compare its behavior when findIndex returns -1 with the Redis store's exclusive XRANGE replay. Use the 105-message reproduction with Last-Event-ID: 2 to check the fix: memory should replay the 100 retained events, matching Redis.

Written by the indexing model from the issue text.

Description

MemorySessionStore.getMessagesFrom returns [] when the Last-Event-ID is no longer in the retained history (findIndex === -1). A client more than 100 events behind gets none of the retained events. The Redis store uses an exclusive XRANGE and replays the 100 it still has.

Repro: 105 messages, GET with Last-Event-ID: 2 → memory replays 0, Redis 100.

🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
58
Forks
15
Avg merge
1d 5h
Merged PRs (30d)
57

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from platformatic/mcp

All issues in platformatic/mcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.