50cff27b01
All features are now covered by rskafka. This also removes the need to specify a server ID for write buffer consumers. This was only used for rdkafka since there we needed to specify a consumer group, even though we did not use any transactions. |
||
---|---|---|
.. | ||
src | ||
.gitattributes | ||
Cargo.toml | ||
README.md | ||
build.rs |
README.md
workspace-hack
This crate is a "workspace hack" crate managed by cargo hakari
.
Its purpose is to unify the features used by all crates in the workspace so that the crates share more dependencies and rebuild crates less. There are more details in hakari's documentation.
CI failures
If the workspace_hack_checks
CI job is failing, there are two possible reasons and solutions:
- If
cargo hakari generate --diff
fails, that means a crate has started or stopped using a feature of some crate and that feature isn't up-to-date in theworkspace-hack
crate. To fix this, runcargo hakari generate
and commit the changes. - If
cargo hakari manage-deps --dry-run
fails, that means a crate in the workspace isn't depending on theworkspace-hack
crate. To fix this, runcargo hakari manage-deps
and commit the changes.