Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Handle remote host terminating connection and ignore, continuing for best effort when caching/updating #268

@dkbennett

Description

@dkbennett

Dev Home version

0.1701

Dev Home Azure Extension version

No response

Steps to reproduce the bug

Example of the issue:

[2024/08/22 12:49:29.712 ERR] (AzureDataManager/CacheManager) Failed getting projects for account: <account>
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.

Expected result

When remote host terminates connection, do not treat as error, ignore and move on. Log as a warning instead. Root cause of this issue is unknown, but if one host terminates, ignore it and move on to the next host when doing developer PR updates.

Actual result

This is an error and terminates the remainder of the update for developer pull requests, this prevents developer pull requests from populating or getting notifications.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions