Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
This seems like we are missing a validation in ShareSessionHandler::newShareFetchBuilder, where we have to add a check if we have piggyback acks to be sent on the initial request.
We also need to ensure the callback is appropriately updated.