topfreegames / pitaya

58%

master: 69%

LAST BUILD ON BRANCH main

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• 0.1.0
• 0.2.2
• 0.3.0
• 0.4.1
• 0.5.0
• 0.5.1
• 0.5.3
• 0.7.0
• 0.7.1
• 0.7.2
• 0.7.3
• 0.7.4
• add_metrics
• add_metrics_v3
• backport_421
• backport_lame_duck
• bugfix/SD-SIGINT
• bugfix/client-IncomingMsgChan
• bugfix/concurrency-chan-close-on-client
• bugfix/kick
• bugfix/readme
• bugfix/update-submodule
• bugfix/validator
• cursor/pedra-madeira-coleta-manual-619f
• dependabot/go_modules/github.com/nats-io/nats-server/v2-2.12.6
• dependabot/go_modules/go.opentelemetry.io/otel/sdk-1.43.0
• dependabot/go_modules/google.golang.org/grpc-1.79.3
• dependabot/go_modules/xk6-pitaya/go.opentelemetry.io/otel-1.41.0
• dependabot/go_modules/xk6-pitaya/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp-1.43.0
• dependabot/go_modules/xk6-pitaya/go.opentelemetry.io/otel/sdk-1.40.0
• dependabot/go_modules/xk6-pitaya/go.opentelemetry.io/otel/sdk-1.43.0
• feat/add-isready-function
• feat/add-isready-function-v2
• feat/channel-capacity-metric-port
• feat/read_bigger_messages
• feat/websocket-pitaya-compression
• feature/acceptor-rate-limit
• feature/add-healthchecks
• feature/add-nats-connection-timeout
• feature/auto-doc
• feature/autodoc-flag
• feature/close-sessions-on-shutdown
• feature/compression
• feature/context
• feature/ctx-routing-func
• feature/custom-metrics
• feature/custom_handshake
• feature/default-logger-on-ctx
• feature/descriptors
• feature/docs
• feature/elasticapm
• feature/etcd_auth
• feature/fix-report-rpc-error
• feature/generic-worker
• feature/getallservers
• feature/golang-protobuf
• feature/grpc-out-cluster
• feature/heartbeat_log
• feature/improve-logging
• feature/lazy_grpc_connections
• feature/log-handler-message
• feature/metrics
• feature/nats_die_chan
• feature/nats_reconnect
• feature/new-server-metadata
• feature/pitaya-client-message-id
• feature/print-calls
• feature/proxy-protocol
• feature/rate-limiting
• feature/reduce-connection-close-logs
• feature/report-code
• feature/rpc-worker
• feature/struct-validation-pipeline
• feature/sys-metrics
• feature/tags-from-ctx
• feature/tls-client
• feature/v2-apply-master-changes
• feature/worker-namespace
• fix-service-discovery-startup-time
• fix/agent-close-panic
• fix/die-chan
• fix/drain-nats-conn
• fix/error-code-lost-in-compression
• fix/error-code-lost-in-compression-v2
• fix/etcd-revoke-lease
• fix/etcd-sync-log-level
• fix/grpc_leak
• fix/nats-reconnection
• fix/nats-shutdown
• fix/natsSubLeak
• fix/ordered-modules
• fix/pitaya_client_interface
• fix/port-error-propagation
• fix/prometheus
• fix/protos
• fix/route-err
• fix/rpctracing
• fix/sd_concurrency
• fix/service-discovery
• fix/shutdown
• fix/shutdownMsg
• fix/statsd-histogram
• fix/submodule
• fix/support-loopback-rpcs
• fix/test
• fix/tests
• fix/timing-report
• fix/unique-session-kick
• fix/unique_session_race_condition
• fix/version-unification
• fix/windows-sys-kill
• fix/xk6-pitaya
• grpc
• guard_empty_msg
• guard_empty_msg-main
• hostname
• improve_logs
• improvement/logs
• kcp-acceptor
• lame_duck_reconnection
• log/heartbeat_error
• log_imp_v2
• logger-docs
• main
• master
• metrics-docs
• nested-configs
• patch-5
• refactor/etcd-Bootstrap
• refactor/kick
• refactor/kickch
• refactor/pipeline
• refactor_agent
• refactor_connection
• remove-error-log-on-client-disconnect
• rpc_protobuf
• server-id-getter
• v0.10.2
• v0.11.3
• v0.12.0
• v0.12.2
• v0.12.4
• v0.12.5
• v0.13.0
• v0.13.1
• v0.13.2
• v0.13.3
• v0.13.4
• v0.13.5
• v0.13.6
• v0.14.0
• v0.14.2
• v0.14.3
• v0.14.5
• v0.14.6
• v0.14.7
• v0.15.0
• v0.15.3
• v0.15.4
• v0.15.5
• v0.15.5-logsv1
• v0.15.5-logsv2
• v0.15.6-alpha
• v0.16.0
• v0.16.1
• v0.17.0
• v0.2.0
• v0.2.1
• v0.7.6
• v0.7.7
• v0.8.0
• v0.9.0
• v0.9.1
• v0.9.4
• v0.9.5
• v1
• v1.0.0
• v1.1.0
• v1.1.1
• v1.1.2
• v1.1.4
• v1.1.5
• v2
• v3_ports

Build # 27219158685

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