sassoftware / sassoftware/arke
fix stream MessageTTL
Open
Beginner friendly
Nobody has claimed this yet.
bug
go
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 8
Description
When using a stream with a MessageTTL, the rabbitmq provider declares the stream with max-age incorrectly. It takes the client provided MS and assumes it is seconds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the RabbitMQ stream declaration and the MessageTTL handling in the provider. Check how the client-provided millisecond value is translated to max-age, then verify that stream declarations use the correct unit and that the existing relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100