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
Previously the FrameProcessorAdapter performed checks via the FrameReceiverAdapter that the frameReceiver has all of its free buffers available to avoid confusing failures. This was removed here.
The generated start_writing method should be disabled (.enabled = False, e.g. here and a @command method added to FrameProcessorController the does the checks and then calls the start_writing method, which is still available internally, just not exposed to the transport layer (I think).
Acceptance Criteria
FrameProcessorAdapterController does not allow start writing if frame receiver status is bad.
The text was updated successfully, but these errors were encountered:
Previously the FrameProcessorAdapter performed checks via the FrameReceiverAdapter that the frameReceiver has all of its free buffers available to avoid confusing failures. This was removed here.
The generated
start_writing
method should be disabled (.enabled = False
, e.g. here and a@command
method added to FrameProcessorController the does the checks and then calls thestart_writing
method, which is still available internally, just not exposed to the transport layer (I think).Acceptance Criteria
FrameProcessorAdapterController
does not allow start writing if frame receiver status is bad.The text was updated successfully, but these errors were encountered: