Do not include stack traces for known exceptions when trying multiple federation destinations. (#10662)
This commit is contained in:
1
changelog.d/10662.misc
Normal file
1
changelog.d/10662.misc
Normal file
@@ -0,0 +1 @@
|
||||
Do not print out stack traces for network errors when fetching data over federation.
|
||||
@@ -43,6 +43,7 @@ from synapse.api.errors import (
|
||||
Codes,
|
||||
FederationDeniedError,
|
||||
HttpResponseException,
|
||||
RequestSendFailed,
|
||||
SynapseError,
|
||||
UnsupportedRoomVersionError,
|
||||
)
|
||||
@@ -558,7 +559,11 @@ class FederationClient(FederationBase):
|
||||
|
||||
try:
|
||||
return await callback(destination)
|
||||
except InvalidResponseError as e:
|
||||
except (
|
||||
RequestSendFailed,
|
||||
InvalidResponseError,
|
||||
NotRetryingDestination,
|
||||
) as e:
|
||||
logger.warning("Failed to %s via %s: %s", description, destination, e)
|
||||
except UnsupportedRoomVersionError:
|
||||
raise
|
||||
|
||||
Reference in New Issue
Block a user