| 11:30 |
awt |
jonsykkel: Would it be possible to decrease the frequency of ignore messages smalpest sends out? Currently seeing 1 per second. I'm wondering if blatta may not be able to handle that rate currently due to the shitty pure python serpent implementation. |
| 11:32 |
jonsykkel |
awt: sure, set it to 10sec(avg) now |
| 11:33 |
awt |
ty jonsykkel |
| |
~ 24 minutes ~ |
| 11:57 |
asciilifeform |
!q uptime |
| 11:58 |
asciilifeform |
lol ^ wat |
| 11:58 |
asciilifeform |
^ embargoed for ~week?! |
| 11:58 |
asciilifeform |
!q uptime |
| 12:02 |
dulapbot |
asciilifeform: time since my last reconnect : 0d 0h 8m |
| 12:02 |
dulapbot |
asciilifeform: time since my last reconnect : 0d 0h 9m |
| |
~ 26 minutes ~ |
| 12:29 |
awt |
blatta currently consuming about 3% CPU on my laptop - some kind of ryzen |
| |
~ 18 minutes ~ |
| 12:47 |
phf |
ayo holup |
| 12:47 |
asciilifeform |
wb phf |
| 12:48 |
awt |
Hey phf was testing from behind a firewall on another IP for a while this morning |
| |
↖ |
| 12:53 |
phf |
test |
| 12:53 |
phf |
another test |
| 12:54 |
phf |
y'all network is funky |
| 12:55 |
awt |
I see you |
| 12:55 |
phf |
yeah, but the context is #a, wherein we discuss the odd and strange delays on pest network |
| 12:55 |
awt |
I'm on 9972, yes, no prod loops, no cpu issues on this machine. |
| |
↖ |
| 12:55 |
asciilifeform |
thread |
| 12:56 |
dulapbot |
(asciilifeform) 2022-09-18 asciilifeform: a and still slow? |
| |
↖ |
| 12:56 |
awt |
yeah been following |
| |
↖ |
| 12:56 |
awt |
Got to separate out potential issues. |
| 12:56 |
phf |
i think i'm back to being near realtime, but the chain that was broken due to previous test messages been sitting in limbo for ~~5 minutes |
| 12:57 |
phf |
http://logs.bitdash.io/pest/2022-09-18#1013045 << also when you sent this message, did you just switch over the ip/client, or you've been on current setup for a while? |
| 12:57 |
bitbot |
Logged on 2022-09-18 12:48:52 awt: Hey phf was testing from behind a firewall on another IP for a while this morning |
| 12:58 |
awt |
in blatta the default order buffer expiration is 180s |
| 12:58 |
awt |
shamefully for a couple minutes this morning I was operating from 2 ips |
| 12:58 |
awt |
forgot to shutdown the station on my laptop before starting up on the server |
| 12:58 |
asciilifeform |
that'll do interesting things to chain |
| 12:59 |
asciilifeform |
( if there were a working fork detector, oughta've gone off errywhere ) |
| |
↖ |
| 12:59 |
asciilifeform |
( or at least errywhere from whose pov is hearsay ) |
| 13:00 |
phf |
well, i've updated my AT quite a while ago, and was sending "test transmit through awt". in fact things didn't start working until awt sent the "Hey phf" message above |
| 13:01 |
awt |
that was immediately after I came back online at my old IP |
| 13:01 |
phf |
ah, ok |
| 13:03 |
phf |
well, then all the mysteries are solved. awt was down, my ATs were all out of date, asciilifeform's advertised ip is actually behind nat, dulapbot has always been magically and mysteriously delayed. i think that covers it |
| 13:03 |
awt |
lol yes. I can't seem to connect to asciilifeform from behind a nat either. |
| 13:03 |
* |
asciilifeform thinking about it, doesn't recall ever actually turning the embargo knob on dulapbot down from 180 |
| 13:04 |
* |
asciilifeform on local rack recently installed a new pfsense box and oughta take anuther look at the config, strongly suspects the fwd rule aint actually wurking |
| |
↖ |
| 13:05 |
phf |
i suspect we might need stations in variety of configurations. one useful thing to have would be a station without operator, that acts more like a backbone: no retransmit delays, doesn't do its own chain discovery, mostly concerned with maintaininig healthy AT, etc. |
| 13:09 |
* |
asciilifeform suspects that once erryone has working addrcast, and has at least 1 peer that doesn't habitually wander away ( e.g. the racked bots ) the 'came back from beach and ugh can't connect to anyone' headache will largely evaporate |
| 13:10 |
phf |
http://logs.bitdash.io/pest/2022-09-17#1013014 << it was not like the typical perturbator output, that seem to be default soundtrack in hackerspaces and nerd get togethers. i think the health&petrurbator combo are supposed to be some kind of noise/industrial/witchhouse/salem thing. it was less synthwave and more i dunno in |
| 13:10 |
bitbot |
Logged on 2022-09-17 01:13:11 signpost: http://logs.bitdash.io/pest/2022-09-16#1012988 << ah I like that song Excess by Perturbator. believe I've heard the other band but can't recall. |
| 13:10 |
phf |
dustrial rock? the sound system was also pretty bad. i very much enjoyed the experience because i was just flying round in the moshpit, which was also at the center of the acoustic noise cone. my friends here were sitting down thought it mostly sucked. |
| 13:11 |
phf |
the general theme was a kind of rehash of the early 2000s: "i'm a piece of shit trash, so lets just shoot heroin and die, idk" |
| 13:14 |
phf |
but reinacted by middle class nerds, who bought fresh hot topic shit for the occassion :} it was a very polite mosh, without much bottoming out. you could kind of see people going "ow too much too much i'm not feeling comfortable about all this, but i'm going to act cool somewhere else" |
| 13:15 |
asciilifeform |
phf: wat's 'bottoming out' ? |
| 13:18 |
phf |
asciilifeform, it's when you surrender to the experience, without much concern for physical consequences |
| 13:21 |
phf |
like a fat dude killing a can of beer, smashing it on his head, rushing the mosh, wiping out, accidentally getting his teeth kicked out while on the ground, then getting up while grinning through blood, and rushing the mosh again |
| 13:22 |
phf |
i miss a good mosh ._. |
| |
~ 1 hours 5 minutes ~ |
| 14:27 |
phf |
http://logs.bitdash.io/pest/2022-09-17#1013018 << i generally don't like indie riffs, even with country folk affectation. it reminds me of late 90s early 2000s american tv show thing, where they would have some guest band play at the local in-show bar. the one tree hill weekly guest band. |
| 14:27 |
bitbot |
Logged on 2022-09-17 01:15:39 signpost: incidentally just got in from seeing the mountain goats, was great, if you're into that earnest folk music dork thing, which I am. |
| 14:32 |
phf |
i went to an appalachian fest yesterday, had some pretty nice lineup, and i like that among that traditional bluegrass bands that's been coming there for years you also have a bunch of hipster bands doing a kind of medley of appalachian/irish/scottish covers |
| 14:36 |
phf |
e.g. these guys https://www.youtube.com/watch?v=KHkSYgzWiLk |
| |
~ 3 hours 14 minutes ~ |
| 17:51 |
asciilifeform |
unrelatedly, apparent perma-gap in dulapbot's log ( compare w/ bitdash ) |
| 17:51 |
bitbot |
Logged on 2022-09-18 12:59:09 asciilifeform[jonsykkel|awt|crawlerbot]: ( if there were a working fork detector, oughta've gone off errywhere ) |
| 17:51 |
dulapbot |
Logged on 2022-09-18 12:58:12 asciilifeform: that'll do interesting things to chain |
| 17:52 |
asciilifeform |
^ likely not the only 1 |
| 17:52 |
asciilifeform |
this 1 esp. odd considering that asciilifeform is one of the few folx directly peered to it |
| 17:53 |
* |
asciilifeform gearing up to make yer anuther attempt to load the embargo logic in curr. blatta into head |
| 17:54 |
* |
asciilifeform looking fwd to publication of phf's cl proto |
| 18:00 |
awt |
Anyone interested in trying a blatta that uses mcrypt serpent? |
| |
~ 35 minutes ~ |
| 18:36 |
awt |
Now testing mcrypt... |
| |
~ 17 minutes ~ |
| 18:53 |
signpost |
awt: happy to test w/e you got. |
| 19:07 |
awt |
Only thing preventing me from doing a release right now is I'm still seeing some cold peers being updated to my own ip. |
| 19:10 |
phf |
what's mcrypt? |
| 19:11 |
awt |
phf: more serious crypto lib recommended by authors of pure python serpent currently in use: http://mcrypt.sourceforge.net/ |
| 19:11 |
phf |
also one perhaps not kosher but pragmatic solution to "crypto in python slow" is to cffi to openssl :> |
| 19:12 |
phf |
or cffi to a c lib of some sort |
| 19:12 |
phf |
ah mcrypt looks like that very "c lib of some sort" |
| 19:12 |
awt |
phf: this is how I'm using mcrypt, cffi |
| 19:14 |
phf |
cool. i'll take a look at it also, because i've been considering doing an ffi to openssl. perhaps not a permanent solution, but a stop gap before i extract and optimize relevant code from ironclad |
| 19:19 |
awt |
Actually, the latest blatta disables ac by default, so the self-address bug can be avoided for now at least by simply not using AC. Can at least test out potential "prod loop" fix and see if mcrypt speeds up blatta on lower powered machines. |
| |
~ 21 minutes ~ |
| 19:41 |
awt |
Ah hmm last instance of the self address bug could have been due to having multiple stations using the same keys at different ips. |
| |
~ 17 minutes ~ |
| 19:58 |
asciilifeform |
phf: openssl incls serpent?! |
| 19:59 |
phf |
asciilifeform, no. (i just discovered that, the thought was in the back of my mind, rather than explored option) |
| 19:59 |
asciilifeform |
a |
| 19:59 |
asciilifeform |
could ffi classic c serpent naturally |
| 20:00 |
asciilifeform |
a loox like awt baked this already |
| 20:03 |
* |
asciilifeform orthogonally: thinking re when is the correct time, hypothetically, for station to hammer ports. imho oughta be when received addrcast, and knows that atm peer is live, but attempt to connect to the ephemeral port in the addrcast not resulted in war |
| |
↖ |
| 20:03 |
dulapbot |
(asciilifeform) 2022-09-18 asciilifeform: we'll need this, eventually, asciilifeform suspects, for 'final solution to nat' |
| 20:04 |
asciilifeform |
... not resulted in warm peer within some interval |
| 20:04 |
asciilifeform |
hrm thought the msg procrustation was fixed in 9973 lol |
| 20:06 |
asciilifeform |
thing is, the hammer gotta work from ~both~ ends |
| 20:06 |
phf |
yeah, could combine classic c serpent, and sha256/512 from busybox into a lib, ffi into it, cffi from python, etc. |
| 20:06 |
asciilifeform |
( as asciilifeform understands, it will do so tho ) |
| 20:08 |
asciilifeform |
( each station will receive addrcast from the other; then $interval elapses w/out connection in the usual way; then each starts hammer and continues until connects ) |
| 20:10 |
asciilifeform |
^ pill against 'symmetric nat' |
| 20:10 |
* |
asciilifeform must bbl |
| 20:11 |
dulapbot |
Logged on 2022-09-07 11:00:58 asciilifeform: afaik with 'symmetric' nats of the type apparently victimizing jonsykkel , the only drill that worx is to hammer random ports, from both directions, until match |
| 20:14 |
awt |
message chunking fix was 9972 |
| 20:15 |
awt |
9971 with mcrypt, potential prod loop fix, ac disabled by default |
| |
↖ ↖ |
| 20:16 |
awt |
Due to flow of liquishit, won't have much time to debug/support tomorrow - fri. |
| 20:17 |
awt |
Also, if you don't have mcrypt built, should still "magically" just work using pure python. It will emit warnings in the log, however. |
| 20:19 |
signpost |
awt: cool, will give that a try. will note any problems here, but don't take it as a demand to stop what you're doing and address immed. |
| 20:27 |
signpost |
awt: fwiw the try...except blocks without specific errors to catch are going to swallow bugs and cause you pain later |
| 20:27 |
signpost |
oughta probably do the pivot on whether mcrypt is available on an ImportError handler |
| 20:28 |
signpost |
would you mind linking the mcrypt you recommend using? |
| 20:29 |
signpost |
http://labix.org/python-mcrypt ? |
| 20:29 |
awt |
signpost: yes. should be a link in the readme. |
| 20:29 |
signpost |
ah derp, should've read |
| 20:33 |
awt |
Still seeing up to 45% cpu on out outgoing ac bursts. Gotta smooth that out. |
| 20:35 |
phf |
what's ac? |
| 20:37 |
signpost |
awt: knob cast b00g http://paste.deedbot.org/?id=E7tB |
| 20:39 |
signpost |
lemme make sure that isn't my own src manglement, gonna re-press |
| 20:44 |
awt |
odd. I added in the interpret_none_as_zero method for that case. |
| 20:44 |
signpost |
yeah I'd hand-mangled the file already, my fault |
| 20:44 |
signpost |
(to fix that bug) |
| 20:44 |
awt |
phf: ac is address cast |
| 20:46 |
awt |
ok what I'm seeing now is deedbot repeatedly prodding my station |
| 20:46 |
signpost |
crash loop, sec |
| 20:46 |
signpost |
(unwanted touching!!!) |
| 20:47 |
awt |
my theory was that prod_interval_seconds was being interpreted incorrectly somehow and causing a prod every time the event loop runs. |
| 20:50 |
signpost |
ok, up now with less mangled src |
| 20:50 |
signpost |
(deedbot is up) |
| 20:51 |
awt |
nice no prod loop now |
| 20:51 |
signpost |
!!help |
| 20:51 |
awt |
looks to be syncing for some reason |
| 20:52 |
signpost |
yeah, was doing some getdata, now not sure, no output yet |
| 20:52 |
awt |
embargoed for default period of 100+ secs likely |
| 20:53 |
deedbot |
http://deedbot.org/help.html |
| 20:54 |
signpost |
cpu usage is like 5%, nb! |
| 20:54 |
awt |
sweet |
| 20:56 |
signpost |
got embargo at 1sec already in knobs |
| 20:56 |
signpost |
!!help |
| 20:59 |
deedbot |
http://deedbot.org/help.html |
| 20:59 |
awt |
lol |
| 20:59 |
phf |
like watching water boil :) |
| 21:00 |
* |
signpost pokes deedbot with a stick |
| 21:01 |
awt |
!!help |
| 21:01 |
deedbot |
http://deedbot.org/help.html |
| 21:01 |
signpost |
his blatta saw that msg immediately |
| 21:01 |
signpost |
!!help |
| 21:01 |
deedbot |
http://deedbot.org/help.html |
| 21:01 |
awt |
!!help |
| 21:01 |
deedbot |
http://deedbot.org/help.html |
| 21:01 |
awt |
pretty snappy now |
| 21:02 |
signpost |
yep seems fine |
| 21:02 |
signpost |
thanks for the new release awt! |
| 21:02 |
awt |
signpost: yw - thanks for testing |
| 21:02 |
phf |
well, it's fairly obvious that embargo has an effect, but what i don't i understand. so packet goes into embargo, getdata for rest of chain comes out, at that point there should be enough packets to release all the embargoed stuff, why does it still hang? |
| 21:04 |
awt |
phf: the algo is messages get dumped from the embargo not when the ancestor comes in, but simply after embargo period expires. |
| |
↖ |
| 21:04 |
awt |
this is wrong(tm) |
| 21:04 |
phf |
yah |
| 21:05 |
awt |
Was optimized for first sync, assuming a large backlog |
| 21:19 |
signpost |
alrighty my blatta's also up to date. |
| 21:20 |
signpost |
logs see me. |
| 21:25 |
awt |
I see you |
| 21:27 |
phf |
come play with us |
| 21:27 |
awt |
lol |
| 21:29 |
awt |
Ah just thought of another way you could end up with self-addressed peers |
| 21:29 |
awt |
You blast out ac, shut down your station, then immediately start it up. |
| 21:30 |
awt |
Since blatta only keeps ac hashes in memory, any of your ac messages that might come back to you will not be detected as dupes after you restart. |
| |
~ 1 hours 1 minutes ~ |
| 22:32 |
asciilifeform |
http://logs.bitdash.io/pest/2022-09-18#1013174 << thing is, it seems to happen to immediate msgs (e.g. asciilifeform -> dulapbot ) , and not only to hearsays |
| 22:32 |
bitbot |
Logged on 2022-09-18 21:04:07 awt: phf: the algo is messages get dumped from the embargo not when the ancestor comes in, but simply after embargo period expires. |
| 22:32 |
asciilifeform |
per spec, immediates only get embargoed if mischained |
| 22:33 |
asciilifeform |
but seems to happen erry single time anyffin (incl. immed from asciilifeform) hits dulapbot |
| 22:34 |
asciilifeform |
or hm, looking at debug log, is consistent w/ the picture where hearsay hits it, and gets in the chain b/w 2 asciilifeform -> dulapbot immed msgs. so not mystery, nm |
| 22:37 |
asciilifeform |
( and yea the order buffer oughta evict when either timeout or ancestor is found , this will be in 0xfa spec ) |
| 22:38 |
asciilifeform |
see also however. |
| 22:38 |
dulapbot |
Logged on 2022-06-20 14:35:41 asciilifeform: ... the 'order buffer' otoh would be superfluous in a 'mutable' pestron. |
| 22:39 |
awt |
yep |
| 22:40 |
* |
asciilifeform wrote spec strongly around the assumption that frontend is irclike and therefore must attempt to squeeze output to console in sumthing maximally approaching a logical order |
| 22:41 |
asciilifeform |
http://logs.bitdash.io/pest/2022-09-18#1013124 << will test tomorrow |
| 22:41 |
bitbot |
Logged on 2022-09-18 20:15:50 awt: 9971 with mcrypt, potential prod loop fix, ac disabled by default |
| 22:41 |
* |
asciilifeform must bbl |
| 22:43 |
awt |
$ticker btc usd |