- Nov 16, 2009
-
-
z3d authored
-
z3d authored
and 'd07b92fb678f4dc87b62eaaeab002820b25583b6'
-
HungryHobo authored
-
- Nov 15, 2009
- Nov 14, 2009
- Nov 13, 2009
- Nov 12, 2009
- Nov 11, 2009
- Nov 10, 2009
-
-
zzz authored
-
zzz authored
-
zzz authored
and 'a831cd0f05f3dcf5d877ff68b14fef2497cde44a'
-
zzz authored
-
zzz authored
-
zzz authored
was not doing unsigned comparisons! * Floodfill rework part 2 of N: Store closest to the key, subject to last failed lookup and store stats. * FloodfillPeerSelector: Use standard XORComparator instead of messing with BigInteger * FloodfillVerifyStoreJob: Set correct timeout for requeued store job * KNDF: Rework getPeerTimout() to use 1 day averages, and lower the min, max, and multiplication factor. * Publish jobs: Lengthen timeout to 90s (was 30s for routerinfos and 60s for leasesets) * StoreJob: Limit max peer timeout to 15s for direct stores
-
zzz authored
-
zzz authored
that end with AA but not AAAA, so we can permit non-null zero-length certs.
-
z3d authored
-
zzz authored
- Fix bug where reply selector wasn't registered for routerinfo stores, so we didn't get stats, and we kept retrying. This also prevented verification and profile updates for routerinfo stores. This bug was introduced 4 years ago by the change to store routerinfos directly. - Add dbStoreSuccessful() to profile, and have FVSJ call it or dbStoreFailed() as appropriate to give credit or blame to the floodfill we stored to. - Don't let FVSJ verify using the peer we stored to
-
zzz authored
-
- Nov 09, 2009