apache / apache/pekko-persistence-cassandra
fix unstable tests
- Dominant language
- Scala
- Stars
- 15
- Forks
- 17
- Avg merge
- 6h 43m
- Merged PRs (30d)
- 11
Description
`org.apache.pekko.persistence.cassandra.query.EventsByTagSpecBackTracking`
- [x] `sort delayed events by timeuuid`
`org.apache.pekko.persistence.cassandra.query.EventsByTagPersistenceIdCleanupSpec`
- [ ] `drop state and trigger new persistence id lookup periodically`
`org.apache.pekko.persistence.cassandra.EventsByTagRecoverySpec`
- [ ] `must recover if snapshot is for the latest sequence nr`
Contributor guide
Research direction
Start by reading the three named specs: EventsByTagPersistenceIdCleanupSpec, EventsByTagRecoverySpec, and EventsByTagSpecBackTracking. Run the affected tests and investigate the two unchecked cases; done means the persistence-id lookup and latest-snapshot recovery tests pass consistently without the listed instability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, scala
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100