apache / apache/pulsar-client-go
Create reader will stuck on somewhere
- Dominant language
- Go
- Stars
- 745
- Forks
- 389
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 3
Description
The test code:
// client, err := pulsar.NewClient(getClientOptions())
// if err != nil {
// t.Fatal(err)
// }
// assert.Nil(t, err)
// defer client.Close()
//
// topic := newTopicName()
// ctx := context.Background()
//
// // create reader
// reader, err := client.CreateReader(pulsar.ReaderOptions{
// Topic: topic,
// StartMessageID: pulsar.EarliestMessageID(),
// })
// if err != nil {
// t.Fatal(err)
// }
Contributor guide
Research direction
Start by reproducing the shown Go client setup and the client.CreateReader call with EarliestMessageID. Identify where reader creation stops making progress and inspect the relevant client or reader entry point. Done means the reported reader creation no longer gets stuck and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100