This is an automated email from the ASF dual-hosted git repository. hubcio pushed a commit to branch feat/iggy-server-hardening in repository https://gitbox.apache.org/repos/asf/iggy.git
commit 4cbba2a0be5ae4eab333fd0359d36e67d012b321 Author: Hubert Gruszecki <[email protected]> AuthorDate: Fri Jul 24 14:26:59 2026 +0200 fix(server-ng): forward iggy/vsr so the bare vsr feature builds cargo test -p server-ng --features vsr failed to compile since the SDK gates its VsrSessionControl impls on its own vsr feature while the trait surface follows iggy_common/vsr; a scoped server-ng build enabled only the latter, so the SDK compiled with a trait surface demanding impls it had cfg'd out (all three transports). Forward iggy/vsr the same way iggy-cli already does; workspace-wide and CI builds were unaffected because iggy-cli's forward unified the feature on for them. --- core/server-ng/Cargo.toml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/core/server-ng/Cargo.toml b/core/server-ng/Cargo.toml index b42c2a3cb..ca64531e7 100644 --- a/core/server-ng/Cargo.toml +++ b/core/server-ng/Cargo.toml @@ -88,7 +88,10 @@ default = ["mimalloc", "iggy-web"] disable-mimalloc = [] mimalloc = ["dep:mimalloc"] iggy-web = ["dep:rust-embed", "dep:mime_guess"] -vsr = ["iggy_common/vsr"] +# forward iggy/vsr: the SDK gates its VsrSessionControl impls on its own +# feature while the trait surface follows iggy_common/vsr; without the +# forward a bare `-p server-ng --features vsr` build breaks in the SDK +vsr = ["iggy_common/vsr", "iggy/vsr"] [dependencies] ahash = { workspace = true }
