-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove BDX timeout tracking from TransferSession #12520
Comments
This actually helps the provider catch the 5 minute idle timeout. If this is removed, there needs to be explicit implementation on the provider side to do the same idle check. |
* Issue #12520 Remove BDX timeout tracking from TransferSession * - Removed timeout from TransferSession::StartTransfer() and TransferSession::WaitForTransfer() - Remove kNoAdvanceTime and its usage - Removed TestTimeout() test suite
…ct-chip#16743) * Issue project-chip#12520 Remove BDX timeout tracking from TransferSession * - Removed timeout from TransferSession::StartTransfer() and TransferSession::WaitForTransfer() - Remove kNoAdvanceTime and its usage - Removed TestTimeout() test suite
…ct-chip#16743) * Issue project-chip#12520 Remove BDX timeout tracking from TransferSession * - Removed timeout from TransferSession::StartTransfer() and TransferSession::WaitForTransfer() - Remove kNoAdvanceTime and its usage - Removed TestTimeout() test suite
…ct-chip#16743) * Issue project-chip#12520 Remove BDX timeout tracking from TransferSession * - Removed timeout from TransferSession::StartTransfer() and TransferSession::WaitForTransfer() - Remove kNoAdvanceTime and its usage - Removed TestTimeout() test suite
…nsferSession" This reverts commit b3528c5.
This issue is being reverted via PR #17427, so re-opening this issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
work in progress |
Hello, any chance for some sort of fix/final solution here? We are currently trying to use the provided chip-ota-provider-app to validate a new device side implementation and we are running into a scenario where after the header is sent and received properly, the process just stops as it seems to be waiting for some time to pass on either side. The code in #16743 seemed promising but then it was reverted? This code has been officially released as part of the v1.1.0.1 tag. |
Problem
The
TransferSession
class currently forces the caller to provide timestamps inPollOutput
andHandleMessageReceived
in order to determine if an application-determined timeout has occurred. However, the BDX spec does not say that this is required:Tracking timeouts in the
TransferSession
class is unnecessary and makes the API more complicated and cumbersome.Proposed Solution
OnTimeout
for the application to call to abort the session (without sending aStatusReport
like inAbort()
)The text was updated successfully, but these errors were encountered: