You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2026/07/14 05:29:00 UTC

[jira] [Resolved] (RATIS-2601) GroupInfoReply conf is lost when converting to GroupInfoReplyProto

     [ https://issues.apache.org/jira/browse/RATIS-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze resolved RATIS-2601.
-------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

The pull request is now merged.  Thanks, [~ryu1sakai]!

> GroupInfoReply conf is lost when converting to GroupInfoReplyProto
> ------------------------------------------------------------------
>
>                 Key: RATIS-2601
>                 URL: https://issues.apache.org/jira/browse/RATIS-2601
>             Project: Ratis
>          Issue Type: Bug
>          Components: client
>            Reporter: ryu1.sakai
>            Assignee: ryu1.sakai
>            Priority: Major
>             Fix For: 3.3.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ClientProtoUtils#toGroupInfoReplyProto() doesn't set the field 'conf' (RaftConfigurationProto) when it converts GroupInfoReply into GroupInfoReplyProto.
> Consequently, the converted proto lacks conf and GroupInfoReply.getConf() always returns an empty Optional on the client side.
> Note: Although this code is located in the client module (ratis-client), it is used on the server side (GrpcAdminProtocolService and NettyRpcService), so the bug causes incorrect behavior on the service side.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)