8000 docs: Docs have inconsistent default values for max_latency and max_bytes by acocuzzo · Pull Request #572 · googleapis/python-pubsub · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Mar 9, 2026. It is now read-only.

docs: Docs have inconsistent default values for max_latency and max_bytes#572

Merged
anguillanneuf merged 4 commits intogoogleapis:mainfrom
acocuzzo:fix-batching-documentation
Jan 25, 2022
Merged

docs: Docs have inconsistent default values for max_latency and max_bytes#572
anguillanneuf merged 4 commits intogoogleapis:mainfrom
acocuzzo:fix-batching-documentation

Conversation

@acocuzzo
Copy link
Contributor

There is inconsistency in the documentation about the default value of max_latency, changing this to .01 s (which also reflects the correct unit).

Adding detail on the default values of BatchSettings in batching documentation, as well as fixing the comment in the publisher sample of the max_bytes default value.

Fixes #507 🦕

@acocuzzo acocuzzo requested a review from a team January 24, 2022 23:12
@acocuzzo acocuzzo requested review from a team as code owners January 24, 2022 23:12
@acocuzzo acocuzzo requested a review from parthea January 24, 2022 23:12
@product-auto-label product-auto-label bot added the api: pubsub Issues related to the googleapis/python-pubsub API. label Jan 24, 2022
@anguillanneuf anguillanneuf changed the title Fix: Docs have inconsistent default values for max_latency and max_bytes docs: Docs have inconsistent default values for max_latency and max_bytes Jan 24, 2022
@anguillanneuf
Copy link
Contributor

@acocuzzo If you amend your commit message and prefix it with docs:, the conventional commits check should pass.

@anguillanneuf anguillanneuf self-requested a review January 25, 2022 18:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: pubsub Issues related to the googleapis/python-pubsub API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inconsistency in documentation on max_latency

2 participants

0