Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Feature / bugfix release for the following packages:
- [`google-cloud-bigtable==0.28.1`](https://pypi.org/project/google-cloud-bigtable/0.28.1/)
- [`google-cloud-pubsub==0.30.0`](https://pypi.org/project/google-cloud-pubsub/0.30.0/)
- [`google-cloud-trace==0.17.0`](https://pypi.org/project/google-cloud-trace/0.17.0/)
- [`google-cloud-vision==0.29.0`](https://pypi.org/project/google-cloud-/0.29.0/)
- [`google-cloud-vision==0.29.0`](https://pypi.org/project/google-cloud-vision/0.29.0/)

## 0.31.0

Expand Down
10 changes: 5 additions & 5 deletions pubsub/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,17 @@

### Notable Implementation Changes

- Dropping redundant Pub / Sub `Policy._paused` data member (#4568).
- Dropping redundant `Policy._paused` data member (#4568).
- Removing redundant "active" check in policy (#4603).
- Adding a `Consumer.active` property (#4604).
- Making it impossible to call `Policy.open()` on an already opened
policy (#4606).
- **Bug fix** (#4575): Fix bug with async publish for batches. There
were two related bugs. The first: if a batch exceeds the `max_messages`
from the batch settings, then the `commit()` will fail. The second:
when a "monitor" worker that after `max_latency` seconds, a failure
can occur if a new message is added to the batch during the publish.
To fix, the following changes were implemented:
when a "monitor" worker calls `commit()` after `max_latency` seconds,
a failure can occur if a new message is added to the batch **during**
the commit. To fix, the following changes were implemented:
- Adding a "STARTING" status for `Batch.commit()` (#4614). This
fixes the issue when the batch exceeds `max_messages`.
- Adding extra check in `Batch.will_accept` for the number of
Expand All @@ -34,7 +34,7 @@

### Documentation

- Add more explicit documentation for Pub / Sub `Message.attributes` (#4601).
- Add more explicit documentation for `Message.attributes` (#4601).
- Make `Message.__repr__` a bit prettier / more useful (#4602).

PyPI: https://pypi.org/project/google-cloud-pubsub/0.30.0/
Expand Down
2 changes: 1 addition & 1 deletion pubsub/setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@

setup(
name='google-cloud-pubsub',
version='0.30.0',
version='0.30.1.dev1',
description='Python Client for Google Cloud Pub/Sub',
long_description=README,
namespace_packages=[
Expand Down
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@

setup(
name='google-cloud',
version='0.32.0',
version='0.32.1.dev1',
description='API Client library for Google Cloud',
long_description=README,
install_requires=REQUIREMENTS,
Expand Down