zzz
itag0: 0 itag1: 0 itag2: 0 itag3: 0 itag4: 0 itag5: 0 itag6: 1584974673 itag7: 2200658897 itag8: 4243358369
zzz
orignal, problem is 9 introducers, but the first 6 are all 0 which is invalid
orignal
so not XU but 9 ntroducers
orignal
should be fixed in today's release
orignal
"Don't publish introducers with zero tag"
orignal
Vort did a big research what was wrong with introducers
zzz
ok great. Problem is it's triggering a bug in java :(
zzz
glad you found and fixed it, that saves me from looking to see if java did it
zzz
I'm working on the fix on my side
orignal
yes, it's known issue
orignal
however somethimes drozd seen RI even with 12 introducers
orignal
it maybe some modified code
zzz
ok, well somehow in 6 months nobody saw the java-side problem, so I just entered our ticket #415
orignal
because it was not java side problem, it was i2pd's
orignal
and in 6 months nobody mentioned any other java-side problems
zzz
yeah but when we hit it we're logging ERRORs, thats the problem on our side. Why nobody complained before me? don't know
orignal
dr|zed did long time ago for sure
zzz
maybe, but no gitlab issue
orignal
also forgot to say about another issue
orignal
you publish IP/port for unreachable NTCP2 if router cap is U
orignal
my expection that if an address is not rechable it shouldn't publish this info
orignal
and also i
zzz
can you paste an example?
orignal
hence we reocognize such address as reachable but actually it's not
orignal
it was long time ago
zzz
open an issue on git.idk.i2p and it won't be forgotten :)
orignal
U router but it has host, port and i
orignal
maybe idk has fixed it alreadt
orignal
my commit is from July 15
orignal
and it appears in today's release
orignal
like we ignore such addresses
zzz
great, congrats on the release
orignal
not too much changes mostly bugs fixes
zzz
trying to find right spot to fix this SSU2 itag issue
zzz
found a good spot, firing it up to test
zzz
also, I think subdb's are reseeding, my router is reseeding 16x a day... ticket #434
dr|z3d
re #434 zzz, I noticed something iffy at router start, didn't seem to be a repeat behavior, so I pushed back auto-reseed to a minute after uptime and the problem went away.
eyedeekay
zzz ack I'm on it tonight
zzz
ok, I'm not going to try to diagnose further or workaround unless the boys need it
zzz
there was only intended to be one netdb, so having them multiply like rabbits has dozens of serious side effects to be chased down, thats a common theme of the issues I've found
zzz
Jobs you can see on the /jobs page in the console... but there's no easy way to see Timers...
dr|z3d
Blinded message
dr|z3d
is that a proposal hiding in the ellipsis...
zzz
my only proposal is to get this codebase back in shape
dr|z3d
that's a proposal I think we can get behind :)