Show Idle (>14 d.) Chans


← 2022-06-18 | 2022-06-20 →
00:08 awt Current BTC price in USD: $18945.25
~ 3 hours 18 minutes ~
03:26 phf if anybody's awake, can please get a message
~ 25 minutes ~
03:52 asciilifeform helloworld
03:55 phf well well well looks like we gut ourselves a packet
03:58 asciilifeform wb phf . i take it, yer pestron 2way nao ?
03:59 * asciilifeform plugged an awt pestron into asciilifeform's logotron earlier today
03:59 asciilifeform still needs massage tho
~ 7 hours 34 minutes ~
11:33 shinohai $ticker btc usd
11:34 busybot Current BTC price in USD: $19710.1
~ 2 hours 6 minutes ~
13:40 shinohai Updated to 9976
~ 56 minutes ~
14:37 billymg morning shinohai
14:37 billymg and wb busybot
14:42 shinohai Weird busybot not working?
14:43 shinohai $ticker btc usd
14:43 shinohai heh guess the station finally received last nite's turd
14:48 shinohai meh still getting error on 9976 http://paste.deedbot.org/?id=xPY8
14:56 shinohai annnnnnnd son of a goddamn bitch now blatta wont start on bot station
14:58 shinohai $ticker btc usd
15:00 shinohai ok bot will have to catch back up, db barfed so nuked and started over.
15:00 * shinohai sad to lose his uninterrupted uptime ....
15:01 busybot The bot has been up for: 2 minutes and 57 seconds
15:03 asciilifeform shinohai: was this still the very same uniturd bug as prior ?
15:03 busybot Current BTC price in USD: $19457.43
15:03 busybot Current BTC price in USD: $19457.82
15:04 busybot Current BTC price in USD: $19449.07
15:05 asciilifeform meanwhile in odd backlog mechanics
15:05 billymg ^ hey neat, seeing "replay" annotations in my console
15:06 asciilifeform last msg in log strangely not tip of chain
15:08 asciilifeform somehow nao nuffing is going to dulapbot
15:08 shinohai Yeah same uniturd
15:08 dulapbot Logged on 2022-06-19 11:03:25 busybot[asciilifeform]: Current BTC price in USD: $19449.07
15:09 asciilifeform blatta imho desperately needs 'prod' mechanism
15:09 shinohai annnnnnnnnd bot station crashed again
15:10 asciilifeform shinohai: that's with 9976, aha ? wai no one else choked, then ?
15:10 shinohai seems *worse* now that I updated!
15:12 asciilifeform dulapbot not yet crashed, but seems perpetually 1msg 'behind'
15:13 shinohai no idea and my personal station still up
15:13 asciilifeform aand seems to have skipped a msg and not issued a getdata anywhere
15:14 shinohai But indeed is 9976 on bot and still: UnicodeEncodeError: 'ascii' codec can't encode characters in position 6115-6117: ordinal not in range(128)
15:16 billymg asciilifeform: now that your logger is up i'm noticing that relying on the message idx is not reliable for line refs between the two
15:16 asciilifeform awt et al: http://paste.deedbot.org/?id=mv4g
15:16 asciilifeform billymg: the lack of a working reorder does mean that the indices will ~never line up
15:17 asciilifeform billymg: the only way to have working indices would be to have a pestdb-aware logotron, rather than one using irc frontend
15:17 asciilifeform ( and 100% working getdata )
15:18 billymg synced indices is a really nice feature of the logger
15:18 asciilifeform billymg: right, but how are they to sync if 2 loggers are catching msgs in ~random order
15:19 asciilifeform would need logotron that actually eats from db and displays in netchain order.
15:19 billymg yeah
15:20 billymg and then which db? will depend on pest implementation one is running
15:20 asciilifeform billymg: imho ideal logotron would be integrated into given pestron
15:21 billymg asciilifeform: right, that does seem like the only option, i'm just thinking of how to salvage parts of this one and retrofit to read from pest db
15:22 * asciilifeform observes that dulapbot is still continuously 1 msg 'behind'
15:23 asciilifeform which makes 0 sense per asciilifeform's understanding of the protocol -- wtf is it doing with ea. nth msg from asciilifeform (its only peer currently) ?
15:24 asciilifeform seems to be sitting on it until n+1st, ea. time; but only since some time this morning
15:25 asciilifeform loox like they get stuck in a buffer and only released after n+1st msg, erry time
15:26 asciilifeform billymg's bot ~not~ behaving this way, but perhaps only because has multiple peers?
15:26 asciilifeform ( compare the log pgs )
15:27 * asciilifeform must bbl
15:27 billymg interesting
15:40 billymg ^ last message got there eventually, after some delay
15:40 billymg and now instant
~ 29 minutes ~
16:10 awt ^ Yes, the buffer gets dumped eventually even if the requested GETDATA packet never arrives.
16:11 awt Why response wasn't sent or received is yet a myestery
16:11 awt *mystery
16:14 awt Ok I think actually no GETDATA packets were not sent or received
16:15 busybot Current BTC price in USD: $19634.02
16:16 awt Simply, message that triggered GETDATA not dumped until timeout - which is rather long due to a bias towards a potentially long sync for spinning up new stations.
16:16 busybot Current BTC price in USD: $19632.97
16:16 awt asciilifeform: ^
16:17 busybot Current BTC price in USD: $19642.12
16:18 awt The strategy I chose was to collect as many GETDATA responses as reasonably possible before dumping and considering the chain broken.
16:20 awt pestbot: ping
16:21 busybot Current BTC price in USD: $19625.31
16:23 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:23 busybot The bot has been up for: 1 hours 6 minutes and 25 seconds
16:24 busybot Current BTC price in USD: $19625.31
16:24 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:25 busybot The bot has been up for: 1 hours 6 minutes and 25 seconds
16:25 awt shinohai: pestbot just crashed due to an decoding error. Gonna check it out.
16:26 busybot The bot has been up for: 1 hours 6 minutes and 25 seconds
16:26 busybot Current BTC price in USD: $19625.24
16:26 busybot Current BTC price in USD: $19625.31
16:26 busybot The bot has been up for: 1 hours 6 minutes and 25 seconds
16:26 busybot Current BTC price in USD: $19588.53
16:26 busybot Current BTC price in USD: $19596.68
16:27 busybot Current BTC price in USD: $19596.68
16:27 busybot Current BTC price in USD: $19592.35
16:27 busybot Current BTC price in USD: $19596.45
16:27 busybot Current BTC price in USD: $19592.22
16:27 busybot Current BTC price in USD: $19588.88
16:27 busybot Current BTC price in USD: $19592.35
16:27 busybot Current ETH price in BTC: $0.05406
16:27 busybot Current BTC price in USD: $19594.06
16:27 busybot Current USD price in BTC: $0.00005101
16:28 busybot Current BTC price in USD: $19594.82
16:28 busybot Current ETH price in BTC: $0.05406
16:28 busybot Current BTC price in USD: $19591.43
16:28 busybot Current BTC price in USD: $19591.43
16:28 busybot Current BTC price in USD: $19586.28
16:28 busybot Current BTC price in USD: $19596.12
16:28 asciilifeform ugh sumthing strange is happening with busybot ?
16:30 busybot Current BTC price in USD: $19616.67
16:30 busybot Current BTC price in USD: $19617.45
16:30 busybot Current BTC price in USD: $19621.32
16:31 busybot Current BTC price in USD: $19619.16
16:32 busybot Current BTC price in USD: $19611.98
16:32 busybot Current BTC price in USD: $19623.94
16:32 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:32 asciilifeform wtf
16:32 busybot The bot has been up for: 1 hours 15 minutes and 19 seconds
16:32 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:32 busybot The bot has been up for: 1 hours 15 minutes and 19 seconds
16:33 busybot The bot has been up for: 1 hours 15 minutes and 19 seconds
16:33 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:34 busybot Current BTC price in USD: $19586.57
16:34 busybot The bot has been up for: 1 hours 15 minutes and 19 seconds
16:34 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:34 busybot The 24-Hour VWAP for BTC is $ 19275.21 USD
16:34 busybot Current BTC price in USD: $19588.55
16:34 asciilifeform shinohai: any chance thing could shit out 'current x price at $time...' rather than simply 'current x price..' ?
16:34 * asciilifeform wonders whether we finally have our 1st circular getdata, lol
16:35 busybot Current BTC price in USD: $19589.59
16:35 busybot Current BTC price in USD: $19588.99
16:35 busybot The bot has been up for: 1 hours 17 minutes and 46 seconds
16:36 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:36 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:36 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:36 busybot The bot has been up for: 1 hours 18 minutes and 29 seconds
16:36 busybot The next difficulty adjustment for BTC will occur in appx.
16:36 busybot The bot has been up for: 1 hours 18 minutes and 30 seconds
16:36 busybot Current BTC price in USD: $19615.3
16:37 billymg i'll take the blame, all the problems started after i posted this
16:37 bitbot (asciilifeform) 2022-06-16 billymg: ^ no major problems really, works well enough for daily use for months now
16:37 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:37 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:37 asciilifeform lol
16:37 busybot Error! Requires 2 parameters - Please see `man ticker` for usage
16:38 busybot Current BTC price in CRC: $14270540.91
16:38 busybot Current BTC price in USD: $19611.02
16:38 busybot Current BTC price in USD: $19606.09
16:38 billymg !down busybot
16:38 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:39 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:40 asciilifeform http://logs.nosuchlabs.com/log/pest/2022-06-18#1000033 << dupe >> http://logs.nosuchlabs.com/log/pest/2022-06-19#1000185
16:40 asciilifeform awt: i take it you didn't trap circular getdata, lol
16:41 asciilifeform http://logs.nosuchlabs.com/log/pest/2022-06-19#1000187 << wtf
16:42 dulapbot (asciilifeform) 2022-03-10 PeterL: thimbronion: apparently you can't give the knobs a non-integer?
16:42 dulapbot (asciilifeform) 2022-03-11 scoopbot: New article on Thimbron: 9980-9978 - presence, bug fixes
16:42 dulapbot Logged on 2022-06-18 23:50:21 asciilifeform: helloworld
16:42 dulapbot Logged on 2022-06-19 12:36:57 asciilifeform: helloworld
16:42 busybot The 24-Hour VWAP for BTC is $ 19584.80 USD
16:42 asciilifeform there's no limit on how old msgs get replayed to console, is there, lol
16:44 busybot Error! Requires 2 parameters - Please see `man ticker` for usage
16:44 * asciilifeform suspects the logotron-plugged-into-irc-frontend-of-pestron scheme is entirely unworkable, only seemed usable w/ billymg's because his was up moar or less continuously since kickoff
16:45 asciilifeform http://logs.nosuchlabs.com/log/pest/2022-06-19#1000367 << behold the ocean of liquishit surrounding this
16:46 asciilifeform aaand of course the replays aint marked in any useful way
16:47 awt http://logs.bitdash.io/pest/2022-06-19#1007605 << don't know what you mean here
16:47 bitbot Logged on 2022-06-19 16:45:43 asciilifeform: http://logs.nosuchlabs.com/log/pest/2022-06-19#1000367 << behold the ocean of liquishit surrounding this
16:48 awt http://logs.bitdash.io/pest/2022-06-19#1007606 << not a lot of information for me to work with here
16:48 bitbot Logged on 2022-06-19 16:46:30 asciilifeform: aaand of course the replays aint marked in any useful way
16:48 asciilifeform awt: look at the current dulapbot log
16:48 dulapbot Logged on 2022-06-19 12:37:52 asciilifeform: awt: 9982 seems to work
16:50 awt asciilifeform: what am I looking for?
16:50 dulapbot Logged on 2022-06-19 12:39:45 asciilifeform: http://logs.nosuchlabs.com/log/pest/2022-06-18#1000033 << dupe >> http://logs.nosuchlabs.com/log/pest/2022-06-19#1000185
16:50 dulapbot Logged on 2022-06-19 12:39:45 asciilifeform: http://logs.nosuchlabs.com/log/pest/2022-06-18#1000033 << dupe >> http://logs.nosuchlabs.com/log/pest/2022-06-19#1000185
16:51 asciilifeform awt: it's shitting firehose of ancient replay straight into log
16:52 awt asciilifeform: why is this unexpected?
16:52 asciilifeform http://logs.nosuchlabs.com/log/asciilifeform/2022-06-19#1107582 and plox to reply there
16:53 awt Spell it out for me if you will
16:53 asciilifeform awt: it's arguably entirely expected, but makes the log into fucking unusable soup!!
16:55 asciilifeform it's coupla months of msg in ~random order!! intermixed with current convo.
16:57 awt asciilifeform: no trap for circular getdata. I considered that an adversarial case so not yet handled.
16:58 asciilifeform awt: asciilifeform is rather puzzled how could even get a circular getdata. i.e. why would it at any point issue a getdata for a msg already present in the longbuffer
17:00 asciilifeform ... evidently took place in orderbuffer
17:04 dulapbot helloworld (via handcranked client...)
17:05 * dulapbot noticed that after disconnection from bot, could not issue helloworld via irssi to running blatta, had to restart the latter
17:05 * asciilifeform must bbl
~ 20 minutes ~
17:26 awt pestbot: ping
17:28 awt pestbot: ping
17:36 awt pestbot: ping
17:39 pestbot pong
17:41 deedbot http://deedbot.org/help.html
17:41 pestbot pong
17:41 pestbot pong
17:46 awt Ran into about 3 GETDATA responses that caused a decoding crash since the initial smiley incident.
17:47 awt kind of a random outburst from deedbot there.
17:48 awt 我不明白
17:51 awt 再一次
17:52 awt Ah oops - pestbot was on an old version.
17:52 awt pestbot: ping
17:52 awt pestbot: ping
17:52 pestbot pong
17:55 awt pestbot: ping
~ 22 minutes ~
18:18 awt Currently resyncing pestbot from scratch - sync does seem too slow, and I'm noticing dupes being logged and thrown out - which should never happen between just two pest stations.
18:18 awt Not entirely sure how to tackle this problem
18:22 awt incidentally asciilifeform my pestbot station syncs continuously w/out the bot being connected to the station.
18:26 awt pestbot: ping
18:26 pestbot pong
18:26 awt Ok pestbot fully resynced, no crashes. Syncs fine without the irc client ever having been connected.
~ 16 minutes ~
18:43 awt Also not persuaded re: circular GETDATA requests - if this were true syncing would never end.
18:45 awt Also, messages are not presented in random order. Messages are dumped periodically IN ORDER as they are received. Currently the full sync takes longer than the message dump interval.
18:50 shinohai $ticker btc usd
18:51 shinohai guess sync will take time, bbiab!
18:54 busybot Current BTC price in USD: $19642.2
~ 16 minutes ~
19:11 billymg !c net-summary
19:11 crawlerbot Bitcoin Network (IPv4 Nodes Active Within the Last 48 hours) Global: 7714; TRB-Compatible: 28; TRB: 14
19:11 crawlerbot TRB-Compatible by Country: United States: 8; Germany: 4; Romania: 3; Russia: 3; Singapore: 2; Brazil: 1; Australia: 1; Italy: 1; United Arab Emirates: 1; Sweden: 1; Belgium: 1; Venezuela: 1; Bulgaria: 1;
19:11 crawlerbot TRB by Country: United States: 8; Canada: 1; Romania: 1; Lithuania: 1; France: 1; New Zealand: 1; Norway: 1;
19:11 billymg !c trb-status
19:11 crawlerbot 75.106.222.93 (Alive), h=741474, v=99999, United States - peers: 217 - last probed: 21m ago
19:12 crawlerbot 205.134.172.4 (Alive), h=741474, v=70001, United States - peers: 78 - last probed: 23m ago
19:12 crawlerbot 54.38.94.63 (Alive), h=741474, v=88888, France - peers: 72 - last probed: 24m ago
19:12 crawlerbot 208.94.240.42 (Alive), h=741474, v=99999, United States - peers: 58 - last probed: 23m ago
19:12 crawlerbot 54.39.156.171 (Alive), h=741474, v=99999, Canada - peers: 57 - last probed: 23m ago
19:12 crawlerbot 85.164.243.42 (Alive), h=741474, v=99999, Norway - peers: 47 - last probed: 18m ago
19:12 crawlerbot 71.114.46.117 (Alive), h=741474, v=99999, United States - peers: 38 - last probed: 19m ago
19:12 crawlerbot 82.79.58.192 (Alive), h=741474, v=99999, Romania - peers: 31 - last probed: 23m ago
19:13 crawlerbot 103.6.212.28 (Alive), h=735091, v=99999, New Zealand - peers: 27 - last probed: 21m ago
19:13 crawlerbot 205.134.172.28 (Alive), h=741474, v=99999, United States - peers: 24 - last probed: 24m ago
19:14 crawlerbot 205.134.172.26 (Alive), h=741474, v=99999, United States - peers: 17 - last probed: 23m ago
19:14 crawlerbot 94.176.238.102 (Busy? (No answer in 15 sec.)), h=740874, v=99999, Lithuania - peers: 15 - last probed: 23m ago
19:14 crawlerbot 205.134.172.6 (Alive), h=741474, v=99999, United States - peers: 18 - last probed: 24m ago
19:14 crawlerbot 205.134.172.27 (Alive), h=741474, v=99999, United States - peers: 5 - last probed: 23m ago
~ 23 minutes ~
19:37 shinohai $uptime
19:42 busybot The bot has been up for: 56 minutes and 54 seconds
19:43 awt $uptime
19:43 busybot The bot has been up for: 57 minutes and 36 seconds
19:46 awt !c trb-status
19:46 crawlerbot 75.106.222.93 (Alive), h=741475, v=99999, United States - peers: 217 - last probed: 20m ago
19:46 crawlerbot 205.134.172.4 (Alive), h=741475, v=70001, United States - peers: 78 - last probed: 22m ago
19:46 crawlerbot 54.38.94.63 (Alive), h=741475, v=88888, France - peers: 72 - last probed: 22m ago
19:46 crawlerbot 208.94.240.42 (Alive), h=741475, v=99999, United States - peers: 58 - last probed: 22m ago
19:46 crawlerbot 54.39.156.171 (Alive), h=741475, v=99999, Canada - peers: 57 - last probed: 22m ago
19:46 crawlerbot 85.164.243.42 (Alive), h=741475, v=99999, Norway - peers: 47 - last probed: 17m ago
19:47 crawlerbot 71.114.46.117 (Alive), h=741475, v=99999, United States - peers: 36 - last probed: 17m ago
19:47 crawlerbot 82.79.58.192 (Alive), h=741475, v=99999, Romania - peers: 31 - last probed: 22m ago
19:47 crawlerbot 103.6.212.28 (Busy? (No answer in 15 sec.)), h=735091, v=99999, New Zealand - peers: 27 - last probed: 20m ago
19:47 crawlerbot 205.134.172.28 (Alive), h=741475, v=99999, United States - peers: 21 - last probed: 22m ago
19:48 crawlerbot 205.134.172.6 (Alive), h=741475, v=99999, United States - peers: 20 - last probed: 22m ago
19:48 crawlerbot 205.134.172.26 (Alive), h=741475, v=99999, United States - peers: 17 - last probed: 22m ago
19:49 crawlerbot 94.176.238.102 (Busy? (No answer in 15 sec.)), h=740874, v=99999, Lithuania - peers: 15 - last probed: 22m ago
19:50 crawlerbot 205.134.172.27 (Alive), h=741475, v=99999, United States - peers: 5 - last probed: 22m ago
19:58 awt Noticed an interesting behavior. Recently started seeing messages as replays that shouldn't be - then noticed the machine the station is on's clock was off by several minutes. Seems that the station was dropping a packet that was out of the time range.
19:58 awt When another packet was received from another station with a closer clock time, triggered a GETDATA.
20:07 awt $uptime
20:07 busybot The bot has been up for: 1 hours 21 minutes and 24 seconds
~ 1 hours 5 minutes ~
21:12 asciilifeform http://logs.bitdash.io/pest/2022-06-19#1007650 << indeed, looking (with naked eye) asciilifeform did not find a circle
21:12 bitbot Logged on 2022-06-19 18:43:39 awt[signpost|asciilifeform|billymg]: Also not persuaded re: circular GETDATA requests - if this were true syncing would never end.
21:13 asciilifeform (so possibly bug in bitbot ? but wai nao?)
21:14 asciilifeform http://logs.bitdash.io/pest/2022-06-19#1007651 << makes sense. tho still wondering why it getdata'd last night's 'hello world' from asciilifeform
21:14 bitbot Logged on 2022-06-19 18:45:00 awt[asciilifeform|signpost|billymg]: Also, messages are not presented in random order. Messages are dumped periodically IN ORDER as they are received. Currently the full sync takes longer than the message dump interval.
21:14 asciilifeform (which was already in db)
21:15 asciilifeform http://logs.bitdash.io/pest/2022-06-19#1007693 << possibly reason for above, hm
21:15 bitbot Logged on 2022-06-19 19:58:36 awt[asciilifeform|signpost|billymg]: Noticed an interesting behavior. Recently started seeing messages as replays that shouldn't be - then noticed the machine the station is on's clock was off by several minutes. Seems that the station was dropping a packet that was out of the time range.
~ 1 hours ~
22:16 billymg http://logs.bitdash.io/pest/2022-06-19#1007699 << i was not following closely, what was the indication of a potential bug in bitbot?
22:16 bitbot Logged on 2022-06-19 21:13:02 asciilifeform: (so possibly bug in bitbot ? but wai nao?)
~ 55 minutes ~
23:11 asciilifeform billymg: the oddball repeated output from earlier
23:11 bitbot Logged on 2022-06-19 16:21:57 busybot[signpost|asciilifeform]: Current BTC price in USD: $19625.31
23:12 asciilifeform and lol, busybot, rather than bitbot
23:13 billymg ah ok
23:14 * asciilifeform not in top condition, will bbl
23:15 billymg feel better
23:15 asciilifeform ty
← 2022-06-18 | 2022-06-20 →