- Jan 22, 2022
- Jan 21, 2022
-
-
zzz authored
-
- Jan 16, 2022
-
-
idk authored
Allow chown to fail so files can be managed via docker configs and secrets See merge request i2p-hackers/i2p.i2p!48
-
zzz authored
WIP - not hooked in, untested - target 1.8.0 / 0.9.54 Requires significant changes to TrackerClient Adapted from mtn branch i2p.i2p.zzz.udpsnark (2014) Ref: Proposal 160
-
- Jan 15, 2022
-
-
idk authored
Upgrade base image to latest version of Alpine See merge request i2p-hackers/i2p.i2p!47
-
zzz authored
-
zzz authored
-
- Jan 14, 2022
-
-
y2kboy23 authored
-
- Jan 10, 2022
- Jan 07, 2022
- Jan 06, 2022
-
-
zzz authored
in the transports through PLRIJ via FNDF.publish()
-
- Jan 05, 2022
- Jan 04, 2022
-
-
zzz authored
-
- Jan 03, 2022
- Jan 02, 2022
- Dec 30, 2021
-
-
zzz authored
-
- Dec 28, 2021
-
-
zzz authored
-
zzz authored
Required for irc.ilita.i2p
-
zzz authored
-
zzz authored
- Always use a lease as the reply tunnel when publishing LS through a client tunnel This ensures we're not using about-to-expire tunnels for the reply, and ensures the ff is able pick an alternate - Don't count skipped peers as attempted in FloodfillVerify - Pass failed and skipped peers to FloodfillVerify job to be skipped there also - Pass failed and skipped peers from FloodfillVerify job to the next StoreJob on failure - Consolidate common reply token generation code in StoreJob - Ensure tunnel diversity in StoreJob retries by only using tunnels closest to the target for the first request. This increases reliability by not reusing the same tunnels for all retries. - Refactor StoreState to rework inefficient methods and unused data - Clean up commented-out code in StoreState - Log tweaks
-
zzz authored
Don't requeue on failure if there is a newer LS, KNDF will have already done that. Log tweaks and cleanups
-
zzz authored
by only using tunnels closest to the target for the first request. This increases reliability by not reusing the same tunnels for all retries.
-
zzz authored
-
zzz authored
This reduces the max lookup rate
-
zzz authored
10 minute rate is too short Change to getAvgOrLifetimeAvg() Reduce max time
-
zzz authored
Actually update the stat for stores in dbStoreSent(); we are generally storing to different ffs than lookups, so we need the stat for stores as well, since we use it as the timeout in StoreJob. Change from 1-day to 1-hour stat. Switch to avgOrLifetimeAvg() so the rate is always valid. Reduce max time used for timeout. This allows more peers to be tried before total timeout Previously, the per-peer timeout was almost always the max. Make sendStore() package private. Javadocs and cleanups.
-
zzz authored
-
- Dec 27, 2021