Hide Idle (>14 d.) Chans
← 2022-06-18 | 2022-06-20 → ↓
busybot[asciilifeform]: Current BTC price in USD: $19710.1
billymg: morning shinohai
billymg: and wb busybot
shinohai[asciilifeform|signpost]: Weird busybot not working?
shinohai[asciilifeform|signpost]: heh guess the station finally received last nite's turd
shinohai[asciilifeform|signpost]: annnnnnnd son of a goddamn bitch now blatta wont start on bot station
shinohai[asciilifeform]: ok bot will have to catch back up, db barfed so nuked and started over.
shinohai[asciilifeform|signpost] sad to lose his uninterrupted uptime ....
busybot[asciilifeform|signpost]: The bot has been up for: 2 minutes and 57 seconds
asciilifeform: shinohai: was this still the very same uniturd bug as prior ?
busybot[signpost]: Current BTC price in USD: $19457.43
busybot[signpost]: Current BTC price in USD: $19457.82
busybot[signpost|asciilifeform|billymg]: Current BTC price in USD: $19449.07
billymg[signpost]: ^ hey neat, seeing "replay" annotations in my console
asciilifeform: last msg in log strangely not tip of chain
asciilifeform: somehow nao nuffing is going to dulapbot
dulapbot[asciilifeform]: Logged on 2022-06-19 11:03:25 busybot[asciilifeform]: Current BTC price in USD: $19449.07
asciilifeform: blatta imho desperately needs 'prod' mechanism
shinohai[asciilifeform|signpost]: annnnnnnnnd bot station crashed again
asciilifeform: shinohai: that's with 9976, aha ? wai no one else choked, then ?
shinohai[asciilifeform|signpost]: seems *worse* now that I updated!
asciilifeform: dulapbot not yet crashed, but seems perpetually 1msg 'behind'
shinohai[asciilifeform|signpost]: no idea and my personal station still up
asciilifeform: aand seems to have skipped a msg and not issued a getdata anywhere
shinohai[asciilifeform|signpost]: But indeed is 9976 on bot and still: UnicodeEncodeError: 'ascii' codec can't encode characters in position 6115-6117: ordinal not in range(128)
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
asciilifeform: billymg: the lack of a working reorder does mean that the indices will ~never line up
asciilifeform: billymg: the only way to have working indices would be to have a pestdb-aware logotron, rather than one using irc frontend
asciilifeform: ( and 100% working getdata )
billymg: synced indices is a really nice feature of the logger
asciilifeform: billymg: right, but how are they to sync if 2 loggers are catching msgs in ~random order
asciilifeform: would need logotron that actually eats from db and displays in netchain order.
billymg: yeah
billymg: and then which db? will depend on pest implementation one is running
asciilifeform: billymg: imho ideal logotron would be integrated into given pestron
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
asciilifeform observes that dulapbot is still continuously 1 msg 'behind'
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) ?
asciilifeform: seems to be sitting on it until n+1st, ea. time; but only since some time this morning
asciilifeform: loox like they get stuck in a buffer and only released after n+1st msg, erry time
asciilifeform: billymg's bot ~not~ behaving this way, but perhaps only because has multiple peers?
asciilifeform: ( compare the log pgs )
asciilifeform must bbl
billymg: interesting
billymg: ^ last message got there eventually, after some delay
billymg: and now instant
awt[asciilifeform|signpost|billymg]: ^ Yes, the buffer gets dumped eventually even if the requested GETDATA packet never arrives.
awt[asciilifeform|billymg]: Why response wasn't sent or received is yet a myestery
awt[asciilifeform|signpost|billymg]: Ok I think actually no GETDATA packets were not sent or received
busybot[asciilifeform|signpost]: Current BTC price in USD: $19634.02
awt[asciilifeform|signpost|billymg]: 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.
busybot[asciilifeform]: Current BTC price in USD: $19632.97
busybot[signpost|asciilifeform]: Current BTC price in USD: $19642.12
awt[asciilifeform|signpost|billymg]: The strategy I chose was to collect as many GETDATA responses as reasonably possible before dumping and considering the chain broken.
busybot[signpost|asciilifeform]: Current BTC price in USD: $19625.31
busybot[asciilifeform|billymg]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[signpost]: The bot has been up for: 1 hours 6 minutes and 25 seconds
busybot[billymg]: Current BTC price in USD: $19625.31
busybot[signpost]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[signpost]: The bot has been up for: 1 hours 6 minutes and 25 seconds
awt[signpost]: shinohai: pestbot just crashed due to an decoding error. Gonna check it out.
busybot[billymg]: The bot has been up for: 1 hours 6 minutes and 25 seconds
busybot[signpost]: Current BTC price in USD: $19625.24
busybot[asciilifeform]: Current BTC price in USD: $19625.31
busybot[billymg|asciilifeform]: The bot has been up for: 1 hours 6 minutes and 25 seconds
busybot[signpost]: Current BTC price in USD: $19588.53
busybot[asciilifeform]: Current BTC price in USD: $19596.68
busybot[billymg]: Current BTC price in USD: $19596.68
busybot[signpost]: Current BTC price in USD: $19592.35
busybot[asciilifeform|billymg]: Current BTC price in USD: $19596.45
busybot[signpost]: Current BTC price in USD: $19592.22
busybot[asciilifeform|signpost]: Current BTC price in USD: $19588.88
busybot[asciilifeform|signpost]: Current BTC price in USD: $19592.35
busybot[billymg]: Current ETH price in BTC: $0.05406
busybot[signpost]: Current BTC price in USD: $19594.06
busybot[billymg]: Current USD price in BTC: $0.00005101
busybot[signpost]: Current BTC price in USD: $19594.82
busybot[signpost]: Current ETH price in BTC: $0.05406
busybot[asciilifeform]: Current BTC price in USD: $19591.43
busybot[asciilifeform|signpost]: Current BTC price in USD: $19591.43
busybot[asciilifeform|signpost]: Current BTC price in USD: $19586.28
busybot[asciilifeform]: Current BTC price in USD: $19596.12
asciilifeform: ugh sumthing strange is happening with busybot ?
busybot[asciilifeform]: Current BTC price in USD: $19616.67
busybot[signpost]: Current BTC price in USD: $19617.45
busybot[signpost]: Current BTC price in USD: $19621.32
busybot[asciilifeform|signpost]: Current BTC price in USD: $19619.16
busybot[signpost]: Current BTC price in USD: $19611.98
busybot[asciilifeform]: Current BTC price in USD: $19623.94
busybot[asciilifeform|signpost]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[asciilifeform]: The bot has been up for: 1 hours 15 minutes and 19 seconds
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[signpost]: The bot has been up for: 1 hours 15 minutes and 19 seconds
busybot[signpost]: The bot has been up for: 1 hours 15 minutes and 19 seconds
busybot[signpost]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[signpost]: Current BTC price in USD: $19586.57
busybot[signpost]: The bot has been up for: 1 hours 15 minutes and 19 seconds
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[signpost]: The 24-Hour VWAP for BTC is $ 19275.21 USD
busybot[billymg]: Current BTC price in USD: $19588.55
asciilifeform: shinohai: any chance thing could shit out 'current x price at $time...' rather than simply 'current x price..' ?
asciilifeform wonders whether we finally have our 1st circular getdata, lol
busybot[asciilifeform]: Current BTC price in USD: $19589.59
busybot[asciilifeform]: Current BTC price in USD: $19588.99
busybot[asciilifeform]: The bot has been up for: 1 hours 17 minutes and 46 seconds
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[asciilifeform]: The bot has been up for: 1 hours 18 minutes and 29 seconds
busybot[asciilifeform]: The next difficulty adjustment for BTC will occur in appx.
busybot[signpost]: The bot has been up for: 1 hours 18 minutes and 30 seconds
busybot[signpost]: Current BTC price in USD: $19615.3
billymg: i'll take the blame, all the problems started after i posted this
bitbot: (asciilifeform) 2022-06-16 billymg: ^ no major problems really, works well enough for daily use for months now
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[signpost]: Error! Requires 2 parameters - Please see `man ticker` for usage
busybot[asciilifeform]: Current BTC price in CRC: $14270540.91
busybot[asciilifeform]: Current BTC price in USD: $19611.02
busybot[asciilifeform]: Current BTC price in USD: $19606.09
billymg: !down busybot
busybot[asciilifeform]: The 24-Hour VWAP for BTC is $ 19584.80 USD
busybot[signpost]: The 24-Hour VWAP for BTC is $ 19584.80 USD
asciilifeform: awt: i take it you didn't trap circular getdata, lol
dulapbot[asciilifeform]: (asciilifeform) 2022-03-10 PeterL: thimbronion: apparently you can't give the knobs a non-integer?
dulapbot[signpost|billymg]: (asciilifeform) 2022-03-11 scoopbot: New article on Thimbron: 9980-9978 - presence, bug fixes
dulapbot[asciilifeform]: Logged on 2022-06-18 23:50:21 asciilifeform: helloworld
dulapbot[signpost|billymg]: Logged on 2022-06-19 12:36:57 asciilifeform: helloworld
busybot[billymg]: The 24-Hour VWAP for BTC is $ 19584.80 USD
asciilifeform: there's no limit on how old msgs get replayed to console, is there, lol
busybot[billymg]: Error! Requires 2 parameters - Please see `man ticker` for usage
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
asciilifeform: http://logs.nosuchlabs.com/log/pest/2022-06-19#1000367 << behold the ocean of liquishit surrounding this
asciilifeform: aaand of course the replays aint marked in any useful way
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
awt[asciilifeform|billymg]: http://logs.bitdash.io/pest/2022-06-19#1007606 << not a lot of information for me to work with here
bitbot: Logged on 2022-06-19 16:46:30 asciilifeform: aaand of course the replays aint marked in any useful way
asciilifeform[billymg]: awt: look at the current dulapbot log
dulapbot[asciilifeform]: Logged on 2022-06-19 12:37:52 asciilifeform: awt: 9982 seems to work
awt[asciilifeform|billymg]: asciilifeform: what am I looking for?
asciilifeform: awt: it's shitting firehose of ancient replay straight into log
awt[asciilifeform|billymg]: asciilifeform: why is this unexpected?
awt[asciilifeform]: Spell it out for me if you will
asciilifeform: awt: it's arguably entirely expected, but makes the log into fucking unusable soup!!
asciilifeform: it's coupla months of msg in ~random order!! intermixed with current convo.
awt[asciilifeform|signpost|billymg]: asciilifeform: no trap for circular getdata. I considered that an adversarial case so not yet handled.
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
asciilifeform: ... evidently took place in orderbuffer
dulapbot[asciilifeform]: helloworld (via handcranked client...)
dulapbot[asciilifeform] noticed that after disconnection from bot, could not issue helloworld via irssi to running blatta, had to restart the latter
asciilifeform must bbl
awt[asciilifeform|signpost|billymg]: Ran into about 3 GETDATA responses that caused a decoding crash since the initial smiley incident.
awt[asciilifeform|billymg]: kind of a random outburst from deedbot there.
awt[asciilifeform|signpost|billymg]: Ah oops - pestbot was on an old version.
awt[asciilifeform|billymg|signpost]: 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.
awt[asciilifeform|signpost|billymg]: Not entirely sure how to tackle this problem
awt[asciilifeform|signpost|billymg]: incidentally asciilifeform my pestbot station syncs continuously w/out the bot being connected to the station.
awt[asciilifeform|billymg|signpost]: Ok pestbot fully resynced, no crashes. Syncs fine without the irc client ever having been connected.
awt[signpost|asciilifeform|billymg]: Also not persuaded re: circular GETDATA requests - if this were true syncing would never end.
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.
shinohai[asciilifeform|signpost]: guess sync will take time, bbiab!
busybot[asciilifeform|signpost]: Current BTC price in USD: $19642.2
billymg: !c net-summary
crawlerbot[billymg]: Bitcoin Network (IPv4 Nodes Active Within the Last 48 hours) Global: 7714; TRB-Compatible: 28; TRB: 14
crawlerbot[billymg]: 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;
crawlerbot[billymg]: TRB by Country: United States: 8; Canada: 1; Romania: 1; Lithuania: 1; France: 1; New Zealand: 1; Norway: 1;
billymg: !c trb-status
crawlerbot[billymg]: 75.106.222.93 (Alive), h=741474, v=99999, United States - peers: 217 - last probed: 21m ago
crawlerbot[signpost]: 205.134.172.4 (Alive), h=741474, v=70001, United States - peers: 78 - last probed: 23m ago
crawlerbot[asciilifeform]: 54.38.94.63 (Alive), h=741474, v=88888, France - peers: 72 - last probed: 24m ago
crawlerbot[signpost]: 208.94.240.42 (Alive), h=741474, v=99999, United States - peers: 58 - last probed: 23m ago
crawlerbot[asciilifeform]: 54.39.156.171 (Alive), h=741474, v=99999, Canada - peers: 57 - last probed: 23m ago
crawlerbot[signpost|asciilifeform]: 85.164.243.42 (Alive), h=741474, v=99999, Norway - peers: 47 - last probed: 18m ago
crawlerbot[asciilifeform]: 71.114.46.117 (Alive), h=741474, v=99999, United States - peers: 38 - last probed: 19m ago
crawlerbot[billymg]: 82.79.58.192 (Alive), h=741474, v=99999, Romania - peers: 31 - last probed: 23m ago
crawlerbot[asciilifeform]: 103.6.212.28 (Alive), h=735091, v=99999, New Zealand - peers: 27 - last probed: 21m ago
crawlerbot[asciilifeform]: 205.134.172.28 (Alive), h=741474, v=99999, United States - peers: 24 - last probed: 24m ago
crawlerbot[billymg]: 205.134.172.26 (Alive), h=741474, v=99999, United States - peers: 17 - last probed: 23m ago
crawlerbot[billymg]: 94.176.238.102 (Busy? (No answer in 15 sec.)), h=740874, v=99999, Lithuania - peers: 15 - last probed: 23m ago
crawlerbot[billymg]: 205.134.172.6 (Alive), h=741474, v=99999, United States - peers: 18 - last probed: 24m ago
crawlerbot[billymg]: 205.134.172.27 (Alive), h=741474, v=99999, United States - peers: 5 - last probed: 23m ago
busybot[asciilifeform|signpost]: The bot has been up for: 56 minutes and 54 seconds
busybot[asciilifeform|signpost]: The bot has been up for: 57 minutes and 36 seconds
crawlerbot[billymg]: 75.106.222.93 (Alive), h=741475, v=99999, United States - peers: 217 - last probed: 20m ago
crawlerbot[signpost]: 205.134.172.4 (Alive), h=741475, v=70001, United States - peers: 78 - last probed: 22m ago
crawlerbot[billymg]: 54.38.94.63 (Alive), h=741475, v=88888, France - peers: 72 - last probed: 22m ago
crawlerbot[signpost]: 208.94.240.42 (Alive), h=741475, v=99999, United States - peers: 58 - last probed: 22m ago
crawlerbot[asciilifeform]: 54.39.156.171 (Alive), h=741475, v=99999, Canada - peers: 57 - last probed: 22m ago
crawlerbot[billymg]: 85.164.243.42 (Alive), h=741475, v=99999, Norway - peers: 47 - last probed: 17m ago
crawlerbot[asciilifeform]: 71.114.46.117 (Alive), h=741475, v=99999, United States - peers: 36 - last probed: 17m ago
crawlerbot[billymg]: 82.79.58.192 (Alive), h=741475, v=99999, Romania - peers: 31 - last probed: 22m ago
crawlerbot[asciilifeform]: 103.6.212.28 (Busy? (No answer in 15 sec.)), h=735091, v=99999, New Zealand - peers: 27 - last probed: 20m ago
crawlerbot[billymg]: 205.134.172.28 (Alive), h=741475, v=99999, United States - peers: 21 - last probed: 22m ago
crawlerbot[billymg]: 205.134.172.6 (Alive), h=741475, v=99999, United States - peers: 20 - last probed: 22m ago
crawlerbot[billymg|asciilifeform]: 205.134.172.26 (Alive), h=741475, v=99999, United States - peers: 17 - last probed: 22m ago
crawlerbot[signpost]: 94.176.238.102 (Busy? (No answer in 15 sec.)), h=740874, v=99999, Lithuania - peers: 15 - last probed: 22m ago
crawlerbot[billymg]: 205.134.172.27 (Alive), h=741475, v=99999, United States - peers: 5 - last probed: 22m ago
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.
awt[signpost|asciilifeform|billymg]: When another packet was received from another station with a closer clock time, triggered a GETDATA.
busybot[asciilifeform|signpost]: The bot has been up for: 1 hours 21 minutes and 24 seconds
asciilifeform: http://logs.bitdash.io/pest/2022-06-19#1007650 << indeed, looking (with naked eye) asciilifeform did not find a circle
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.
asciilifeform: (so possibly bug in bitbot ? but wai nao?)
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
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.
asciilifeform: (which was already in db)
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.
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?
bitbot: Logged on 2022-06-19 21:13:02 asciilifeform: (so possibly bug in bitbot ? but wai nao?)
bitbot: Logged on 2022-06-19 16:21:57 busybot[signpost|asciilifeform]: Current BTC price in USD: $19625.31
asciilifeform: and lol, busybot, rather than bitbot
billymg: ah ok
asciilifeform not in top condition, will bbl
billymg: feel better
busybot[asciilifeform|signpost]: Current BTC price in USD: $19974.91
← 2022-06-18 | 2022-06-20 → ↑
Random(pest) | Download hourly DB snapshot | Get Source Code