manticoresoftware / manticoresoftware/go-sdk

TCP Connection returns EOF for queries after ping

Open
#26 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
58
Forks
9
PR merge metrics
No merged PRs in 30d

Description

When using the `Ping()`queries don't work anymore and return `EOF` from the TCP stream. The obvious workaround is to reconnect after ping (or don't ping). But this should be fixed.

Minimal example to reproduce:

```
clTemp := manticore.NewClient()
clTemp.SetServer("localhost", 9312)
clTemp.Open()
clTemp.Ping(123) // if I remove this line the query returns results
res, err := clTemp.Query("foo", "temprt")
if err != nil {
fmt.Printf("Error test querying Manticore %+v", err) // EOF
}
```

Contributor guide

No contributing guide indexed for this repository

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 by running the minimal Go example against Manticore Search on localhost:9312 and compare Query behavior with and without Ping(123). Trace the client’s Ping, Query, and TCP stream handling to identify why the post-ping query returns EOF; done means queries succeed after Ping without reconnecting.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, networking
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.