[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r10797: vague fuzzy bug reports so i don't forget them (tor/trunk/doc)

Author: arma
Date: 2007-07-12 11:24:56 -0400 (Thu, 12 Jul 2007)
New Revision: 10797

vague fuzzy bug reports so i don't forget them

Modified: tor/trunk/doc/TODO
--- tor/trunk/doc/TODO	2007-07-12 11:08:55 UTC (rev 10796)
+++ tor/trunk/doc/TODO	2007-07-12 15:24:56 UTC (rev 10797)
@@ -41,6 +41,18 @@
       - In a good HOWTO.
 Things we'd like to do in 0.2.0.x:
+      - Bug reports I've heard along that way that don't have enough
+        details to solve them yet.
+        - tup said that when he set FetchUselessDescriptors, after
+          24 or 48 hours he wasn't fetching any descriptors at all
+          anymore. This was in 0.2.0 but worked fine in 0.1.2.
+        - arma noticed that when his network went away and he tried
+          a new guard node and the connect() syscall failed to it,
+          the guard wasn't being marked as down. 0.2.0.x.
+        - after being without network for 12 hours, arma's tor decided
+          it couldn't fetch any network statuses, and never tried again
+          even when the network came back and arma clicked on things.
+          also 0.2.0.
       - Update dir-spec with decisions made on these issues:
         o clients don't log as loudly when they receive them
         o they don't count toward the 3-strikes rule
@@ -221,6 +233,8 @@
         like the ones you have, ask a new bridge for its server/authority.
       . Ask all directory questions to bridge via BEGIN_DIR.
         - use the bridges for dir fetches even when our dirport is open.
+R     - drop 'authority' queries if they're to our own identity key; accept
+        them otherwise.
 N     - Design/implement the "local-status" or something like it, from the
         "Descriptor purposes: how to tell them apart" section of