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
Not sure if it is a bug or I'm missing something, but calling Consumer's commit with message=None or offsets=None will act like I provided them with something to use, and will result in either a bad type error, or a "can't do both" message.
(edit: I also looked at the c code, and I expected None to translate to boolean false, so I'm lost on why this happens)
This came up because one environment started to throw "message and offsets are mutually exclusive" for an empty .commit(), and on an other one I tried to explicitly disable the message part to see what happens, but was met with the type error.
Is there a way to explicitly tell commit not to use messages? Something akin to: .commit(message=None)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
Not sure if it is a bug or I'm missing something, but calling Consumer's commit with message=None or offsets=None will act like I provided them with something to use, and will result in either a bad type error, or a "can't do both" message.
(edit: I also looked at the c code, and I expected None to translate to boolean false, so I'm lost on why this happens)
This came up because one environment started to throw "message and offsets are mutually exclusive" for an empty .commit(), and on an other one I tried to explicitly disable the message part to see what happens, but was met with the type error.
Is there a way to explicitly tell commit not to use messages? Something akin to: .commit(message=None)?
Beta Was this translation helpful? Give feedback.
All reactions