You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some methods in the Client interface of the indexer package receive a parameter limit uint64:
GetCells(ctxcontext.Context, searchKey*SearchKey, orderSearchOrder, limituint64, afterCursorstring) (*LiveCells, error)
// GetTransactions returns the transactions collection by the lock or type script.GetTransactions(ctxcontext.Context, searchKey*SearchKey, orderSearchOrder, limituint64, afterCursorstring) (*TxsWithCell, error)
// GetTransactionsGrouped returns the grouped transactions collection by the lock or type script.GetTransactionsGrouped(ctxcontext.Context, searchKey*SearchKey, orderSearchOrder, limituint64, afterCursorstring) (*TxsWithCells, error)
The RPC Indexer module documentation requires the limit value to be UInt32 though.
If you call e.g. client.GetCells(_, _, _, math.MaxUint64, _), the rpc node will return an error: Invalid params: Invalid Uint32 0xffffffffffffffff: number too large to fit in target type.
These should be adjusted to receive uint32 and their implementation should properly convert to UInt32
(indexer/indexer.go)
There might also be similar issues with other RPC methods, I did not check exhaustively.
The text was updated successfully, but these errors were encountered:
Some methods in the
Client
interface of theindexer
package receive a parameterlimit uint64
:The RPC Indexer module documentation requires the limit value to be
UInt32
though.If you call e.g.
client.GetCells(_, _, _, math.MaxUint64, _)
, the rpc node will return an error:Invalid params: Invalid Uint32 0xffffffffffffffff: number too large to fit in target type.
These should be adjusted to receive
uint32
and their implementation should properly convert toUInt32
(
indexer/indexer.go
)There might also be similar issues with other RPC methods, I did not check exhaustively.
The text was updated successfully, but these errors were encountered: