This repository was archived by the owner on Aug 30, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 30, 2026. It is now read-only.
Increment no longer working on AWS #592
Description
Hi,
It seems like Increment recently stopped working after the newest update on AWS Linux 2.
Environment details
- OS type and version:
Linux 4.14.275-207.503.amzn2.x86_64 #1 SMP Wed Apr 13 20:24:50 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux - Python version:
3.8.5 - pip version:
pip 22.0.4 from /usr/local/lib/python3.8/site-packages/pip (python 3.8) google-cloud-firestoreversion:2.5.0
Steps to reproduce
- Run the code below
Code example
from firebase_admin import credentials, firestore, initialize_app
from google.cloud.firestore_v1 import Increment
cred = credentials.Certificate("test.json")
initialize_app(cred)
db = firestore.client()
db.collection("test").document("test").set({"count": Increment(1)}, merge=True)Stack trace
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/ec2-user/.local/lib/python3.8/site-packages/google/cloud/firestore_v1/document.py", line 166, in set
batch, kwargs = self._prep_set(document_data, merge, retry, timeout)
File "/home/ec2-user/.local/lib/python3.8/site-packages/google/cloud/firestore_v1/base_document.py", line 217, in _prep_set
batch.set(self, document_data, merge=merge)
File "/home/ec2-user/.local/lib/python3.8/site-packages/google/cloud/firestore_v1/base_batch.py", line 107, in set
write_pbs = _helpers.pbs_for_set_with_merge(
File "/home/ec2-user/.local/lib/python3.8/site-packages/google/cloud/firestore_v1/_helpers.py", line 870, in pbs_for_set_with_merge
set_pb.update_transforms.extend(field_transform_pbs)
TypeError: Expected a message object, but got field_path: "count"
increment {
integer_value: 1
}
Any suggestions?
Activity
roburns commentedon May 26, 2022
I'm having the same issue in GCP Functions. Woke up to similar logs revolving around ArrayUnion and ArrayRemove.
Mariatta commentedon May 26, 2022
Hi @NinitoAS, thanks for reporting the issue and sorry to hear that you're having trouble with this.
I can't seem to replicate the your problem. I'm wondering if perhaps other dependency is causing the issue.
Can you do a
pip freeze, and let us know the version of the following libraries?Thank you.
Mariatta commentedon May 26, 2022
@rburns629 would you mind sharing a sample code snippet for replicating this issue? Thanks.
NinitoAS commentedon May 26, 2022
Hi, yes of course.
Here are my other dependencies:
NinitoAS commentedon May 26, 2022
I just updated all the packages you mentioned and I can't seem to reproduce the issue any longer.
Here are the new versions
The issue seem to be connected to protobuf, proto-plus requires protobuf<4.0.0dev,>=3.19.0
So it seems like the issue appears when you have
protobuf 4.21.0Seems like we have to pin our dependency versions for AWS for it to not install v4 of protobuf
Mariatta commentedon May 26, 2022
Yes indeed protobuf 4 is not compatible here. I'd recommend setting the limit as follows:
protobuf >= 3.15.0, <4.0.0dev.roburns commentedon May 26, 2022
@Mariatta My issues were resolved as well by including protobuf==3.20.1 and google-api-core==2.8.1 in my requirements.txt. Thanks for the suggestions!
fix(deps): Require proto-plus >=1.20.5
fix(deps): Require proto-plus >=1.20.5 (#593)