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
When making a LUIS or QnA calls, there is no timeout, except the default one defined with HttpClient. One might want to limit time spent calling such services and 'abort' the call on timeout with an exception.
Proposed change
Add optional param for LUIS and QnA CTOR that includes timeout for each call, and throw an exception when it times out. This way customers can define a max timeout for calls and handle the error from their bot. If not, a call can spin for the default HTTP timeout which is 100 sec (I think).
Component Impact
Update LUIS and QnA libraries.
Note: LUIS C# RecognizeAsync already takes a cancelationToken. But QnA doesn't. Not sure how JS handles timeouts.
Customer Impact
Additive functionality.
Tracking Status
Dotnet SDK
PR
Merged
Javascript SDK
PR
Merged
Java SDK
PR
Merged
Python SDK
PR
Merged
[dcr]
The text was updated successfully, but these errors were encountered:
LUIS and QnA calls dont have a timeout param
When making a LUIS or QnA calls, there is no timeout, except the default one defined with HttpClient. One might want to limit time spent calling such services and 'abort' the call on timeout with an exception.
Proposed change
Add optional param for LUIS and QnA CTOR that includes timeout for each call, and throw an exception when it times out. This way customers can define a max timeout for calls and handle the error from their bot. If not, a call can spin for the default HTTP timeout which is 100 sec (I think).
Component Impact
Update LUIS and QnA libraries.
Note: LUIS C# RecognizeAsync already takes a cancelationToken. But QnA doesn't. Not sure how JS handles timeouts.
Customer Impact
Additive functionality.
Tracking Status
Dotnet SDK
Javascript SDK
Java SDK
Python SDK
[dcr]
The text was updated successfully, but these errors were encountered: