[tor-commits] [tor] 01/08: Stop using published_on to decide whether to republish.
gitolite role
git at cupani.torproject.org
Mon May 16 12:55:03 UTC 2022
This is an automated email from the git hooks/post-receive script.
dgoulet pushed a commit to branch main
in repository tor.
commit 8345b3bd92fb126a65ee096914f84f512d20614a
Author: Nick Mathewson <nickm at torproject.org>
AuthorDate: Tue Nov 9 08:46:36 2021 -0500
Stop using published_on to decide whether to republish.
Thanks to the StaleDesc flag, this is not something we need to look
at any longer.
---
src/feature/relay/router.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/feature/relay/router.c b/src/feature/relay/router.c
index a2ca472307..3daa8688ba 100644
--- a/src/feature/relay/router.c
+++ b/src/feature/relay/router.c
@@ -2554,8 +2554,6 @@ mark_my_descriptor_dirty_if_too_old(time_t now)
rs = networkstatus_vote_find_entry(ns, server_identitykey_digest);
if (rs == NULL)
retry_fast_reason = "not listed in consensus";
- else if (rs->published_on < slow_cutoff)
- retry_fast_reason = "version listed in consensus is quite old";
else if (rs->is_staledesc && ns->valid_after > desc_clean_since)
retry_fast_reason = "listed as stale in consensus";
}
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the tor-commits
mailing list