In a case where readString is used, cbor-gen callsreadStringWithMax with a max of MaxLength (8192), which matches the size of the slice returned by stringBufPool. However, Indigo is calling readStringWithMax directly, with a size of 1000000 in this case, larger than what stringBufPool returns. Not sure what the desired fix is — changing stringBufPool to take its own size parameter?
While reading a repo with Indigo, I'm getting occasional panics like this:
I think what's going in is:
In a case where
readString
is used, cbor-gen callsreadStringWithMax
with a max ofMaxLength
(8192), which matches the size of the slice returned bystringBufPool
. However, Indigo is callingreadStringWithMax
directly, with a size of 1000000 in this case, larger than whatstringBufPool
returns. Not sure what the desired fix is — changingstringBufPool
to take its own size parameter?