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

hubcio pushed a change to branch send_messages_confirmation
in repository https://gitbox.apache.org/repos/asf/iggy.git


    omit 2414dfcfd Merge branch 'master' into send_messages_confirmation
    omit 0d76a691c feat(server-ng): add per-client-network advertised address 
selectors (#3818)
    omit dc8493883 test(integration): remove suites duplicating existing 
coverage (#3823)
     new f004a5ada chore(repo): bump iggy-cli and iggy-bench crates

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   (2414dfcfd)
            \
             N -- N -- N   refs/heads/send_messages_confirmation (f004a5ada)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 Cargo.lock                                         |   6 +-
 Cargo.toml                                         |   3 +-
 core/bench/Cargo.toml                              |   2 +-
 core/cli/Cargo.toml                                |   2 +-
 core/configs/Cargo.toml                            |   1 -
 core/configs/src/server_ng_config/cluster.rs       | 987 +--------------------
 core/configs/src/server_ng_config/defaults.rs      |   1 -
 core/configs/src/server_ng_config/validators.rs    |   1 -
 core/configs_derive/src/config_env.rs              |  22 +-
 .../tests/cluster/metadata_checkpoint_restart.rs   | 138 +--
 core/integration/tests/sdk/mcp_parity.rs           | 608 +++++++++++++
 core/integration/tests/sdk/messages.rs             | 172 ++++
 core/integration/tests/sdk/mod.rs                  |   4 +
 .../tests/server/cluster_metadata_vsr.rs           | 229 +----
 core/integration/tests/server/general.rs           |  19 +-
 core/integration/tests/server/http_client.rs       |  19 +-
 core/integration/tests/server/http_tls.rs          | 112 +--
 .../server/metadata_checkpoint_recovery_vsr.rs     | 138 +++
 core/integration/tests/server/mod.rs               |   4 +
 ...aders_scenario.rs => create_message_payload.rs} |  40 +-
 core/integration/tests/server/scenarios/mod.rs     |   1 +
 core/server-ng/Cargo.toml                          |   6 +-
 core/server-ng/config.toml                         |  47 -
 core/server-ng/src/bootstrap.rs                    |   9 +-
 core/server-ng/src/cluster_meta.rs                 | 125 +--
 core/server-ng/src/dispatch.rs                     |  36 +-
 core/server-ng/src/http.rs                         |  37 +-
 core/server-ng/src/http/error.rs                   | 109 +--
 core/server-ng/src/http/extractor.rs               |  22 +-
 core/server-ng/src/http/handlers.rs                |   7 +-
 core/server-ng/src/http/reads.rs                   |   3 +-
 core/server-ng/src/http/state.rs                   |  22 +-
 core/server-ng/src/http/tls.rs                     |  15 +-
 core/server-ng/src/responses.rs                    |  12 +-
 core/server-ng/src/session_manager.rs              |  28 -
 core/server-ng/tests/sdk_e2e.rs                    | 175 +++-
 36 files changed, 1286 insertions(+), 1876 deletions(-)
 create mode 100644 core/integration/tests/sdk/mcp_parity.rs
 create mode 100644 core/integration/tests/sdk/messages.rs
 create mode 100644 
core/integration/tests/server/metadata_checkpoint_recovery_vsr.rs
 copy core/integration/tests/server/scenarios/{message_headers_scenario.rs => 
create_message_payload.rs} (84%)

Reply via email to