influxdb/workspace-hack
Marco Neumann 50cff27b01
chore: remove rdkafka dependency (#3625)
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.
2022-02-03 13:33:56 +00:00
..
src feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00
.gitattributes feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00
Cargo.toml chore: remove rdkafka dependency (#3625) 2022-02-03 13:33:56 +00:00
README.md feat: Add CI jobs and documentation for the workspace-hack crate 2021-11-19 11:05:34 -05:00
build.rs feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00

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 the workspace-hack crate. To fix this, run cargo 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 the workspace-hack crate. To fix this, run cargo hakari manage-deps and commit the changes.