You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 23, 2026. It is now read-only.
Invalid type for user_id field returned by TransferConfig.to_dict #240
user_id field is deprecated but it still causes us problems. TransferConfig.to_dict creates a dictionary that has the wrong type of this field. This type of this field should be one of: int, long, but this field has type str. This is especially problematic because to_dict method set this field to default value - "0", so I need to convert this field to the correct type on my side.
It would be great if TransferConfig.to_dict returned the correct representation for this object
Traceback (most recent call last):
File "/files/bigquery_dts.py", line 7, in <module>
c = TransferConfig(**b)
File "/usr/local/lib/python3.6/site-packages/proto/message.py", line 466, in __init__
self.__dict__["_pb"] = self._meta.pb(**params)
TypeError: '123' has type str, but expected one of: int, long
Making sure to follow these steps will guarantee the quickest resolution possible.
changed the title [-]Invalid type for user_id field after TransferConfig was converted to dictionary.[/-][+]Invalid type for user_id field returned by TransferConfig.to_dict[/+]on Dec 28, 2020
Activity
[-]Invalid type for user_id field after TransferConfig was converted to dictionary.[/-][+]Invalid type for user_id field returned by TransferConfig.to_dict[/+]tswast commentedon Jul 15, 2021
Moved this to
proto-plusas it is responsible for converting to/from dictionaries. I agree that the round-trip should work.Workaround may be to use to_json and from_json, as that round-trip should work.
Perhaps a
from_dictmethod would actually be useful for going from parsed JSON representation? #152software-dov commentedon Oct 26, 2021
This is an unexpected surfacing of the issue fixed by #267
Closing as the fix is now in main