This repository has been archived by the owner on Dec 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
A problem with decoding vshard storage answers #42
Labels
bug
Something isn't working
Comments
The same problem here: Line 184 in 84c49a6
|
There is another more recommended patch from colleague
|
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 7, 2024
* RouterCallImpl: fix decoding responce from storage_ref * RouterCallImpl: fix decoding responce from storage_map * BucketDiscovery: check res for nil * BucketStat: decode bsInfo by ptr * Add tnt tests for disvoery logic * Add tnt tests for RouterCallImpl * Add tnt tests for RouterMapCallRWImpl
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 12, 2024
* RouterCallImpl: fix decoding responce from storage_ref * RouterCallImpl: fix decoding responce from storage_map * BucketDiscovery: check res for nil * BucketStat: decode bsInfo by ptr * Add tnt tests for disvoery logic * Add tnt tests for RouterCallImpl * Add tnt tests for RouterMapCallRWImpl
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 12, 2024
* RouterCallImpl: fix decoding responce from storage_ref * RouterCallImpl: fix decoding responce from storage_map * BucketDiscovery: check res for nil * BucketStat: decode bsInfo by ptr * Add tnt tests for disvoery logic * Add tnt tests for RouterCallImpl * Add tnt tests for RouterMapCallRWImpl
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 12, 2024
* RouterCallImpl: fix decoding response from storage_ref * RouterCallImpl: fix decoding response from storage_map * BucketDiscovery: check res for nil * BucketStat: decode bsInfo by ptr * Add tnt tests for discovery logic * Add tnt tests for RouterCallImpl * Add tnt tests for RouterMapCallRWImpl * Add tnt tests for topology logic
This was
linked to
pull requests
Sep 13, 2024
Merged
This was
unlinked from
pull requests
Sep 13, 2024
Merged
We still have decoding problems in func (rs *Replicaset) ReplicaCall, there will be another PR with solution |
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 14, 2024
* ReplicaCall - fix decoding response (#42) - fix ignoring timeout while waiting for future.Get() * Introduce Replicaset.CallAsync and struct Future * Add tests for methods of Replicaset and Future
Merged
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 14, 2024
* ReplicaCall - fix decoding response (#42) - fix ignoring timeout while waiting for future.Get() * Introduce Replicaset.CallAsync and struct Future * Add tests for methods of Replicaset and Future
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 17, 2024
* ReplicaCall - fix decoding response (#42) - fix ignoring timeout while waiting for future.Get() * Introduce Replicaset.CallAsync and struct Future * Add tests for methods of Replicaset and Future
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 17, 2024
* ReplicaCall - fix decoding response (#42) - fix ignoring timeout while waiting for future.Get() * Introduce Replicaset.CallAsync * Add tests for methods of Replicaset
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem 1
RouterMapCallRWImpl
lacks checks for len(respData) before addressing its elements.For example, here
go-vshard-router/api.go
Line 295 in 84c49a6
and here
go-vshard-router/api.go
Line 298 in 84c49a6
and so on...
Problem 2
In
ReplicaCall
, we consider an error if len(respData) != 2. But, if fnc is completed successfully but does not return anything (i.e. returns nil), vshard does not send the second element (i.e. does not send nil):go-vshard-router/replicaset.go
Line 109 in 84c49a6
The fix is expected to be similar to PR #35.
The text was updated successfully, but these errors were encountered: