topfreegames / pitaya / 27219158685

58%

master: 69%

Build Type

push

github

Committed by web-flow

Commit Message

fix(cluster): guard against nil Msg in NATS rpc server + bump nats.go to v1.52.0 (#503)

* fix(cluster): guard against nil Msg in NATS rpc server handleMessages

A payload delivered to a server's RPC subject that unmarshals into a
protos.Request without error but with a nil Msg caused handleMessages to
nil-panic at `req.Msg.Reply = msg.Reply`, crashing the whole process
(the goroutine has no recover). A well-formed pitaya RPC always sets Msg
(see buildRequest), so a nil Msg means the payload is malformed at the
source: an empty publish, a non-Request proto, or a schema-skewed sender
such as an older libpitaya client built against a different request.proto.

Drop such messages and log the surviving Request fields, the reply inbox,
and a capped hex prefix of the payload so the sender/route can be traced.

* chore(deps): bump nats.go to v1.52.0 (latest)

Updates github.com/nats-io/nats.go v1.47.0 => v1.52.0, with transitive
golang.org/x/* deps updated to match. The module already targets go 1.25,
so no go directive change is needed.

Coverage Stats

1 of 13 new or added lines in 1 file covered. (7.69%)

222 existing lines in 6 files now uncovered.

5105 of 8733 relevant lines covered (58.46%)

0.64 hits per line