`SearchResultHit.TextMatchInfo.NumTokenDropped` type is incorrect

[MarwanAlsoltany]

Description

I am performing a query with sort_by=_text_match:desc. The SDK is not able to unmarshal the response JSON. The error I am getting is the following:

json: cannot unmarshal number 18446744073709551602 into Go struct field .hits.text_match_info.num_tokens_dropped of type int

Here is a direct link to the line producing the issues:

typesense-go/typesense/api/types_gen.go

Line 1343 in 01ce554

NumTokensDropped *int `json:"num_tokens_dropped,omitempty"`

I changed the type to uint manually and everything seemed to be working as expected.

Now I know this is an automatically generated file, but is there really a reason why NumTokensDropped is typed as int and not uint, can this value ever be in negative? Or is it because the generator uses OpenAPI spec, which doesn't support unsigned integers?

BTW, I think other fields typed with int in this file could be changed to uint as well (e.g. BestFieldWeight).

Steps to reproduce

I am not sure why the num_token_dropped is this high, Not sure if it has to do with the dataset I am testing against or is it always int64.

Expected Behavior

Would expect it to complete the operation successfully.

Actual Behavior

Error due json.Unmarshal failing.

Metadata

Go Version: 1.22.4

Typesense Version: v27.1

Typesense SDK Version: v3.0.0

[softwarespot]

Experienced the same issue today too, with SDK v3.1.0 and Go 1.24.0

[advdv]

We have the same issue:

[FAILED] Unexpected error:  
  <*fmt.wrapError | 0x1400041c4c0>: 

  failed to perform multi-search: json: cannot unmarshal number 18446744073709551615 into Go struct field .results.hits.text_match_info.num_tokens_dropped of type int

  {

      msg: "failed to perform multi-search: json: cannot unmarshal number 18446744073709551615 into Go struct field .results.hits.text_match_info.num_tokens_dropped of type int",

      err: <*json.UnmarshalTypeError | 0x14000056050>{

          Value: "number 18446744073709551615",

          Type: <*reflect.rtype | 0x10578c100>{

              t: {Size_: 0x8, PtrBytes: 0x0, Hash: 1725659129, TFlag: 15, Align_: 8, FieldAlign_: 8, Kind_: 2, Equal: 0x104c7dc10, GCData: 0, Str: 2435, PtrToThis: 395168},

          },

          Offset: 8243,

          Struct: "",

          Field: "results.hits.text_match_info.num_tokens_dropped",

      },

  }
occurred

Go version: go1.24.1
Typesense: v27.1
Typesense Go SDK: 0.3.0

@kishorenc Sorry for pinging but this seems pretty serious (for us it happens in prod). Is there anything we can triage this with short term?

[kishorenc]

@advdv

I will release a patch with the field being uint shortly, but can you please produce a small reproducible example with some sample docs that produces this issue? Will be good to see what is actually being returned by the API response.

[advdv]

@kishorenc thank you for the quick turnaround. I've asked the developers for an example but it doesn't seem to happen consistently in a local test environment so i'm not sure. But we do see it happen consistently on our cluster hosted on Typesense Cloud. So if you DM me i can point you to the deployment we have so you can maybe debug it there?

[kishorenc]

I've now published a release with the patch suggested here (using uint).

But we do see it happen consistently on our cluster hosted on Typesense Cloud.

Can you please DM me the code snippet on our Slack community channel if you already part of it? Alternatively, you can also email to support@typesense.org.