Show Idle (>14 d.) Chans
← 2021-11-14 | 2021-11-16 → ↓
16:50 billymg test
16:51 billymg !. uptime
16:51 bitbot billymg: time since my last reconnect : 0d 0h 3m
16:51 billymg heyyyy, there we go
16:51 billymg logging is back on
↖
16:52 billymg hey, is logging back on?
16:52 bitbot Logged on 2021-11-15 16:51:30 billymg: logging is back on
16:53 awt test
16:54 awt SWEET
~ 26 minutes ~
17:20 asciilifeform or hm nope
17:20 asciilifeform my msgs not showing in pestlog
17:20 asciilifeform showed 'hm nope' but not previous
17:22 awt hm looks like everything but "seems to work"
17:23 asciilifeform aha
17:23 asciilifeform 1
17:23 asciilifeform 2
17:23 asciilifeform 3
17:24 billymg asciilifeform: not sure why the first message didn't make it through
17:25 * asciilifeform still suspects it aint packet loss (in GBs of udp wankage carried out by asciilifeform , incl. trans-oceanic, saw 0 packet loss in the classical sense) but possibly buggy deduper.
17:26 awt billymg: you should be able to verify that "seems to work" was forwarded from your main station by searching for it in the log
17:26 awt if you care to, that is.
17:27 billymg yeah, my bot's station didn't get that first messag
17:27 awt clearly your main station received it
17:31 awt possibly a routing issue?
17:32 billymg ah, hrm, my last message, "yeah", didn't get logged
17:33 awt perhaps message when from ascii to me, then billymg, then maybe bounce count exceeded somehow? Then was a dupe when it came directly from ascii with a lower bounce count?
17:33 awt Could invalidate this theory by locating log of the message being sent to bot from billymg's station
17:35 billymg if that's the case we should see more randomly dropped lines
17:35 billymg not a bad theory, since previously my bot was connected to the same station as my irc client
17:37 awt yeah also my box is way closer to you, if you are running it in CR
17:37 billymg awt: i'm not, it's in asciilifeform's rack
17:37 awt so that *could* explain the delay in asciilifeform's message reaching you
17:37 awt oh
17:37 awt lol but then where is asciilifeform running his?
17:38 asciilifeform lol ping time to cr aint anywhere near 3sec
17:38 awt possibly china
17:38 asciilifeform awt: my test station is on desk, ~5ms ping from rack
17:39 awt ok
17:39 awt bounces is at 3 so shouldn't be a factor anyway unless it took an even more circuitous route
17:40 asciilifeform awt: am i correct in supposing that the mechanism for superceding of hearsay by a direct packet aint in the coad yet ?
17:40 awt asciilifeform: what does superceding mean here?
17:41 billymg awt: minor request, you should add a page on your blog with all of the patches in one place, like http://billymg.com/bitdash-crawler-vtree/
17:41 asciilifeform awt: http://www.loper-os.org/pub/pest/pest_draft.html#42322-in-wot-hearsay
17:41 billymg all of the blatta patches
17:41 awt what about this? http://share.alethepedia.com/blatta/
17:41 billymg lol that works
17:42 billymg didn't know it existed
17:43 awt asciilifeform: yes there is not yet a hearsay buffer
17:43 asciilifeform a
17:43 asciilifeform this still doesn't 100% explain what billymg saw, tho..
17:43 awt no. need to know if the packet left billymg's station, basically
17:44 asciilifeform at some pt in near future i'ma set up a test station on dulap, but sadly prolly not until wk+ from nao
17:47 * awt wodners if pest can get through the great firewall
17:47 billymg http://paste.deedbot.org/?id=JTKF
17:48 billymg awt: lemme know if those lines are helpful
17:49 awt this your logger? 2021-11-15 17:27:53.790539 [127.0.0.1:7779] <- d4768c92c2c25e21
17:49 awt if so, that line indicates 'yeah' was sent to your logger
17:49 billymg awt: yep
17:50 billymg but never showed up in logger station's logs
17:50 awt now in your logger, if the bounce count was too high, there would be an message about rejecting a stale packet
17:50 awt if that hex code doesn't show up anywhere in the bot logs then there's a connectivity issue
17:50 awt which would be odd on the same machine
17:50 awt billymg: the message could have been rejected for some other reason
17:51 awt but there should be a record of that
17:52 awt you just need to find d4768c92c2c25e21
17:53 asciilifeform awt: asciilifeform aint an expert on chinese firewall, but iirc it doesn't throw out udp per se (unless endpoint on banlist)
17:53 awt actually stale would be if the timestamp was too old sorry
17:54 billymg awt: http://paste.deedbot.org/?id=fusJ
17:55 awt billymg: there is actually NO output if the bounce count is too high to forward
17:55 billymg so those lines invalidate the > maxbounces theory?
17:56 awt no actually
17:56 billymg oh
17:56 awt I take that back, yes they do
17:56 billymg lol that's what i thought you meant by "NO output"
17:57 awt according to the code I'm looking at that message should have been forwarded to the irc client
17:57 awt bounce count check is only for rebroadcast, and packet is sent to the irc client before that check
17:58 billymg weird
17:58 awt so if your last paste is your bot logs, it received the packet
17:58 awt and marked it as duplicate
17:58 billymg yeah, those are the bot's station's logs
17:58 billymg but according to your code it should've still sent them to the connected bot?
17:58 awt how could it be marked as duplicate if it came directly from you and there are no other instances in the log?
18:00 awt billymg: is that the only line with that message id?
18:01 awt seems unlikely
18:01 billymg awt: it is, the only other instances of that id are in the payload of your messages telling me to search for it
18:02 awt Then that means some previous message had the exact same timestamp
18:03 awt Now, with all the rubbish messages going out very frequently, this is theoretically possible
18:04 awt especially if on SAME box
18:04 awt if ts is in secs and not miliseconds, highly possible
18:06 awt so we need some mechanism of avoiding sending out broadcasts simultaneously with rubbish
18:07 awt or the timestamp shouldn't be used to uniquely identify messages
18:07 billymg awt: ah, looks like that might've been it, see timestamps on surrounding lines: http://paste.deedbot.org/?id=eoGq
18:07 awt yep
18:08 awt asciilifeform ^
18:09 awt OR don't track rubbish messages in dupe queue?
18:09 awt seems like the best approach
18:11 PeterL what is to say that you won't get two valid maessages from different peers at the same time? probably better to track them by a hash or something than by timestamp
18:11 awt PeterL true
18:12 awt I mean there's no reason to track IGNORE messages in the queue still, too
18:16 PeterL billymg: I am still not seeing a timestamp in my AT from you, I wonder if we are still not peered correctly?
18:18 asciilifeform awt: why are timestamps 'being used to validate messages' ????
18:18 asciilifeform deduping is done with hash of entire msg per spec
↖
18:19 asciilifeform it is entirely permissible for over9000 msg to come in w/ equal timestamps.
18:19 awt asciilifeform: implemented dedup before the spec came out, haven't reviewed
18:19 asciilifeform aa
18:19 asciilifeform ok
18:34 asciilifeform btw another missed msg in pestlog
18:34 asciilifeform ('but yeah.... getdata...')
~ 27 minutes ~
19:02 billymg PeterL: i still don't have timestamps for most others either, only awt and now bitbot
~ 25 minutes ~
19:27 asciilifeform welcome to pesttestnet, jonsykkel !
19:30 asciilifeform seems to work
19:31 asciilifeform 'u still see my msgs? changed something in firewal' most recent i'm seeing prior to 'cool'
19:31 asciilifeform jonsykkel: it's still 'alpha' proggy, occasionally msgs go to devnull lol
19:31 asciilifeform but 'spreading -- works!'
19:32 PeterL so, not sure if this is a dumb question, to send someone a key should it be gpg encrypted to their key or should I sign it first and then encrypt it?
19:37 asciilifeform PeterL: sign then encrypt
19:37 asciilifeform this is more or less sop for any serious wot work
19:37 asciilifeform (else how does peer know it was PeterL's key)
19:37 PeterL good point, that's what I though, just checking
19:38 * asciilifeform also recs to have such thrd in #a, where lines not randomly vanished lol
19:38 PeterL lol! But it is so fun to be using the pestnet already
19:39 asciilifeform indeed
~ 29 minutes ~
20:08 PeterL http://paste.deedbot.org/?id=teav << asciilifeform
20:10 asciilifeform PeterL: how come 2 keys in there ?
20:10 PeterL it's the same key, that is the format that awt's little script spits it out
20:11 asciilifeform oh yea lol
20:11 asciilifeform ok added PeterL
20:11 awt PeterL: I recommend to use /genkey
20:11 asciilifeform still seeing 'None' for his timestamp in AT tho
20:11 asciilifeform PeterL: are you behind nat ?
20:11 PeterL hmm, I think so?
20:14 asciilifeform PeterL: try adding http://logs.bitdash.io/pest/2021-11-13#1000321 for asciilifeform's AT entry
↖
20:14 bitbot Logged on 2021-11-13 18:20:59 asciilifeform: billymg: try adding /AT asciilifeform 71.191.220.241 50725
↖
20:14 asciilifeform on your end
20:14 asciilifeform (this'll work for so long as asciilifeform's station not reset)
20:14 asciilifeform presently this is the only way 2 natted stations can peer
20:15 asciilifeform btw billymg i see my lines in the logs but no echos from bot here
20:16 awt not seeing echoes either
20:16 PeterL ok, I added that as the address, but it still lists None as your timestamp
20:16 asciilifeform anybody have a successful peering w/ PeterL ?
20:16 asciilifeform (somebody gotta, or i couldn't see him , lol)
20:16 * awt raises hand
20:16 asciilifeform awt: what's his ephemeral port ?
20:17 awt asciilifeform: 55565
20:17 asciilifeform very odd, because i have him in AT w/ 55565
20:17 asciilifeform and 0contact
20:17 PeterL should I give you my udp port instead of thee ephemeral one?
20:18 asciilifeform PeterL: if yer behind nat, the ephemeral (which came into being when your session started) is the 1 that yer reachable on
20:18 asciilifeform and seems like other folx able to ?
20:18 asciilifeform but not asciilifeform
20:18 asciilifeform 'PeterL 162.247.151.243:55565 None'
20:18 asciilifeform ^ from AT
20:18 PeterL I seem to have connected fully with shinohai, awt, and jonsykkel
20:19 awt asciilifeform, PeterL, you can check logs to verify the message is being sent out to each other and at what ip:port.
20:19 asciilifeform 2021-11-15 15:13:01.618130 [162.247.151.243:55565] <- 67caa7127e93207f
20:19 asciilifeform my station is defo sending to his
20:19 awt PeterL: you can search your log for that message id
20:20 awt and see what's happening to it
20:20 awt asciilifeform: that is correct
20:20 PeterL hmm, seem to be getting a TypeError: an integer is required
20:20 PeterL just a sec
20:21 awt hm - perhaps somehow port is being passed in as a string somewhere...
20:21 PeterL Traceback (most recent call last):
20:22 asciilifeform i saw 1 or 2 when starting station
20:23 PeterL maybe because there is no port, which expects an integer?
20:23 asciilifeform no port where ?
20:23 awt that too. stack trace would be very helpful
20:23 PeterL I mean if you have a peer and key but no associated address and port?
20:24 billymg asciilifeform: i see bitbot's echos on my terminal here (and they're showing up in the logs)
20:24 asciilifeform i don't
20:25 billymg asciilifeform: might the bot need to peer with some other users?
20:25 billymg currently only peered with billymg
20:25 asciilifeform billymg: if it can see my broadcasts, i oughta be able to see its
20:25 asciilifeform so very evidently bug
20:26 awt ty jonsykkel
20:26 billymg yeah, for example i see this echo in the logs
20:26 bitbot Logged on 2021-11-15 20:14:21 bitbot: Logged on 2021-11-13 18:20:59 asciilifeform: billymg: try adding /AT asciilifeform 71.191.220.241 50725
20:26 billymg and in my terminal here see the echo of the echo ^
20:26 awt I saw that echo
20:26 asciilifeform i see its echo in its log (where of course it will appear) but not in my console
20:27 awt could be the timestamp problem
20:27 asciilifeform yea if timestamp is being used as a dupe indicator, would readily explain the random msg loss
20:28 asciilifeform doesn't explain why i haven't received even 1 packet from PeterL tho
20:29 awt /AT asciilifeform 71.191.220.241 50725 -- this command could end up setting port to ""
20:30 awt should be 71.191.220.241:50725
20:30 billymg PeterL: i updated your at entry
20:30 PeterL hmm, still not seeing anything from billymg or asciilifeform
20:31 billymg PeterL: likewise, those two and shinohai still showing up as None for last timestamp
20:32 asciilifeform so far my only working peerings are with awt and shinohai
20:32 billymg my only working peerings are with awt and bitbot (according to output of /at)
20:33 awt PeterL can you paste your at from sqlite? select * from at;
20:34 awt want to see if I can tell what is wrong with your port field
20:34 PeterL how do I get it out of sqlite?
20:34 billymg .quit
20:34 awt perhaps also paste the command you used to add asciilifeform to at
20:35 billymg oops, sorry, i thought you said how do i get out of sqlite lol
20:35 awt sqlite3 blatta.db
20:35 asciilifeform all of this was the stimulus behind http://logs.nosuchlabs.com/log/asciilifeform/2021-11-14#1065718 thrd
20:36 PeterL I just did /at asciilifeform 71.191.220.241:50725
20:36 * asciilifeform still not received a single packet from PeterL's station
20:37 PeterL 1|200.122.181.26|55000|2021-11-15 20:29:00|2021-11-15 20:29:00
20:37 PeterL 3||7778||
20:37 PeterL did that show up ok?
20:37 asciilifeform that aint mine
20:37 awt you could paste in the pastebin
20:37 PeterL http://paste.deedbot.org/?id=HXbm
20:37 PeterL yeah, probably works better that way
20:38 asciilifeform hmm weird, PeterL's is sending to mine ?
20:38 PeterL what did it do, only show the first line?
20:38 asciilifeform or rather, mine to his
20:38 asciilifeform (if AT display is correct, that is)
20:38 awt peterl that first line 3 as the handle id looks pretty bad!
20:39 PeterL I think that was because in my config I had a key for billymg but no address?
20:41 awt PeterL that could be causing the exception, which could be causing the message not to be sent to subsequent recipients
20:43 awt must bbl
20:43 PeterL right, is there a way to get rid of that?
20:43 awt you could stop blatta and delete it with an sql query
20:43 awt delete from at where .... etc
20:44 awt must bbl
20:45 PeterL ok, I will return shortly
20:49 PeterL ok, back now, maybe it will work?
20:56 PeterL OK, so the logging bot sees me, that is good
21:03 PeterL looks like jonsykkel is one bounce too far from the logging bot to get recorded in the log?
21:04 PeterL ^ peer (join as equals), not pear (fruit)
21:05 PeterL I will peer into the depths of logic to figure this out
21:06 PeterL lol, to the bot it just looks like I am talking to myself
21:07 PeterL maybe we should consider increasing the max jumps by one?
21:09 * asciilifeform still not seen 1 packet from PeterL ftr
21:09 asciilifeform or from bitbot
21:10 asciilifeform (the latter sees mine via hearsay, but i see nuffin outta it)
~ 2 hours 12 minutes ~
23:23 awt PeterL 162.247.151.243:55565 2021-11-15 23:24:52
23:32 asciilifeform still nuffin from his station here btw
23:33 asciilifeform PeterL 162.247.151.243:55565 None
23:47 asciilifeform summary of asciilifeform's current puzzlers : 1) wai no packets from PeterL's station 2) wai no hearsay msgs ~from~ bitbot (despite the latter seeing asciilifeform's msgs, as it evidently does)
23:48 asciilifeform btw bitbot ignored last ln from asciilifeform
← 2021-11-14 | 2021-11-16 → ↑

Random(pest) | Download hourly DB snapshot | Get Source Code

Theme: Light | Dark | System Default