This is an automated email from the ASF dual-hosted git repository.

hubcio pushed a change to branch fix/ng-client-table-capacity-boot-panic
in repository https://gitbox.apache.org/repos/asf/iggy.git


    omit 07a1798c2 chore(rust): bump sdk, common, binary_protocol edge versions
    omit 4d5a2602d fix(server-ng): stop restart panic when WAL replay recovers 
sessions
     add b6a2f81c0 fix(sdk): forward unknown command codes instead of rejecting 
them (#3766)
     add 8b3b5e14e fix(server-ng): stop restart panic when WAL replay recovers 
sessions
     add f90c61024 chore(rust): bump sdk, common, binary_protocol edge versions

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (07a1798c2)
            \
             N -- N -- N   refs/heads/fix/ng-client-table-capacity-boot-panic 
(f90c61024)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 core/common/src/error/iggy_error.rs |  2 --
 core/integration/tests/sdk/raw.rs   | 13 +++++--
 core/sdk/src/clients/client.rs      |  5 ++-
 core/sdk/src/vsr.rs                 | 69 ++++++++++++++++++++++++++++++-------
 4 files changed, 70 insertions(+), 19 deletions(-)

Reply via email to