Skip to content
Snippets Groups Projects
Commit 861d663c authored by Erik Johnston's avatar Erik Johnston
Browse files

Fixup changelog and remove debug logging

parent 1771f004
No related branches found
No related tags found
No related merge requests found
Add retry to well-known lookups if we have recently seen a valid well-known record for the server.
Retry well-known lookups if we have recently seen a valid well-known record for the server.
......@@ -163,9 +163,7 @@ class WellKnownResolver(object):
Deferred[Tuple[bytes,int]]: The lookup result and cache period.
"""
had_valid_well_known = bool(
self._had_valid_well_known_cache.get(server_name, False)
)
had_valid_well_known = self._had_valid_well_known_cache.get(server_name, False)
# We do this in two steps to differentiate between possibly transient
# errors (e.g. can't connect to host, 503 response) and more permenant
......@@ -247,7 +245,6 @@ class WellKnownResolver(object):
# Bail if we've been cancelled
raise
except Exception as e:
logger.info("Retry: %s", retry)
if not retry or i >= WELL_KNOWN_RETRY_ATTEMPTS:
logger.info("Error fetching %s: %s", uri_str, e)
raise _FetchWellKnownFailure(temporary=True)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment