-
Notifications
You must be signed in to change notification settings - Fork 484
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
[#6306] NamedPipe could not reconnect correctly when disconnected unexpectedly #6416
Conversation
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll |
libraries/integration/Microsoft.Bot.Builder.Integration.AspNet.Core/CloudAdapter.cs
Outdated
Show resolved
Hide resolved
libraries/Microsoft.Bot.Connector.Streaming/Transport/StreamingTransport.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the changes be confined to within CloudAdapter in order to minimize the surface area being changed? Thanks!
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll |
libraries/integration/Microsoft.Bot.Builder.Integration.AspNet.Core/CloudAdapter.cs
Outdated
Show resolved
Hide resolved
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll |
Fixes #6306
Description
This PR adds a loop in the CloudAdapter's ConnectNamedPipeAsync method to keep the connection alive in case of failures
Specific Changes
ConnectNamedPipeAsync
method adding a loop while _streamingConnections property is empty.Testing
Here we have two Webchat clients connecting with an echo bot through DL-ASE.
The second client is able to connect with the server after it failed on the first client and reconnected.