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
In the function sendBatchMessages, there is a logic to prepend mp.msgUpdateClient to the beginning of the batch. However, in cases where needsClientUpdate is false, msgUpdateClient will be nil. This can lead to appending a nil value into the batch, which is likely unintended and could cause issues downstream. It's necessary to introduce a check to ensure msgUpdateClient is not nil before appending it to the batch. This precaution would prevent potential errors or unexpected behavior during the message processing workflow.
The text was updated successfully, but these errors were encountered:
Hey @LeTrongDat I think this was also fixed in #1407, does that seem correct?
I believe this was closed out in the issue that i mentioned here. Feel free to re-open this issue if necessary but for now i'm going to close this out.
In the function
sendBatchMessages
, there is a logic to prependmp.msgUpdateClient
to the beginning of the batch. However, in cases whereneedsClientUpdate
is false,msgUpdateClient
will benil
. This can lead to appending a nil value into the batch, which is likely unintended and could cause issues downstream. It's necessary to introduce a check to ensuremsgUpdateClient
is not nil before appending it to the batch. This precaution would prevent potential errors or unexpected behavior during the message processing workflow.The text was updated successfully, but these errors were encountered: