Maybe provide a minimal reproducible example (
https://stackoverflow.com/help/minimal-reproducible-example)?
While it is theoretically possible there is a bug in the `big` package that
could result in such panics it is much more likely the bug is in your code.
So showing us how you are using the
On Tue, 2024-02-13 at 21:35 -0800, Poonai wrote:
> big int panics during text conversion randomly
>
> stack trace:
>
> panic: runtime error: index out of range [1] with length 1
>
> goroutine 2088184 [running]:
> math/big.nat.itoa({0xc01db71500, 0x1, 0x199?}, 0x0, 0xa)
>
On Mon, Jan 29, 2024 at 7:29 PM mr@gmail.com wrote:
>
> I want to vent my frustration. The experience of contributing has been
> unpleasant for me. I have noticed that similar fixes are prioritized and
> merged faster, while I spent time resolving the issue and reporting it, but
> it did
I'm not able to reproduce as well
On Wednesday, February 14, 2024 at 11:05:52 AM UTC+5:30 Poonai wrote:
> big int panics during text conversion randomly
>
> stack trace:
>
> panic: runtime error: index out of range [1] with length 1
>
> goroutine 2088184 [running]:
>
big int panics during text conversion randomly
stack trace:
panic: runtime error: index out of range [1] with length 1
goroutine 2088184 [running]:
math/big.nat.itoa({0xc01db71500, 0x1, 0x199?}, 0x0, 0xa)
/usr/local/go/src/math/big/natconv.go:340 +0x3d2
math/big.(*Int).Text(...)
