What version of gotd are you using?

github.com/gotd/td v0.88.0

Can this issue be reproduced with the latest version?

yes

What did you do?

ping client directly by client.Ping with context timeout

What did you expect to see?

context deadline exceeded

What did you see instead?

panic:

/usr/local/go/src/runtime/panic.go:884\nruntime.panicmem\n\t
/usr/local/go/src/runtime/panic.go:260\nruntime.sigpanic\n\t
/usr/local/go/src/runtime/signal_unix.go:841\n
github.com/gotd/td/internal/mtproto.(*Conn).write\n\t
/go/pkg/mod/github.com/gotd/[email protected]/internal/mtproto/write.go:33\n
github.com/gotd/td/internal/mtproto.(*Conn).writeServiceMessage\n\t
/go/pkg/mod/github.com/gotd/[email protected]/internal/mtproto/write.go:15\n
github.com/gotd/td/internal/mtproto.(*Conn).Ping\n\t
/go/pkg/mod/github.com/gotd/[email protected]/internal/mtproto/ping.go:26\n
github.com/gotd/td/telegram/internal/manager.(*Conn).Ping\n\t
/go/pkg/mod/github.com/gotd/[email protected]/telegram/internal/manager/conn.go:250\n
github.com/gotd/td/telegram.(*Client).Ping\n\t
/go/pkg/mod/github.com/gotd/[email protected]/telegram/ping.go:9\n

What Go version and environment are you using?

go version go1.20.5 linux/amd64

Maybe panic occurs when client reconnected.