02:02 |
awt |
asciilifeform: unclear if jonsykkel is running updated blatta, so might still be creating dupes |
02:02 |
awt |
it is possible not to get the full dump if certain conditions arise |
02:03 |
awt |
ie currently chain considered repaired if the tip is up to date, even if the chain is broken further up. so once the latest message gets out of the order buffer and into the long buffer, chain is "repaired" |
02:04 |
awt |
signpost: ^ |
02:04 |
signpost |
2022-02-28 02:04:35: got ya |
02:04 |
signpost |
2022-02-28 02:04:40: appears to be working fine over here. |
02:05 |
awt |
excellent |
02:07 |
* |
awt messages |
02:08 |
awt |
at least from asciilifeform's client |
02:11 |
* |
awt messages with a timestamp prepended |
| |
~ 40 minutes ~ |
02:52 |
asciilifeform |
irssi ftr |
| |
~ 8 hours 56 minutes ~ |
11:49 |
jonsykkel |
not updated, will have oportunity tomorow |
| |
~ 6 hours 43 minutes ~ |
18:32 |
awt |
Blatta update: commencing work on partial support for PROD packets. Should help with missing messages in some cases. |
| |
~ 2 hours 13 minutes ~ |
20:45 |
awt |
I might have to move here permanently. For whatever reason verisimilitude both bores the hell out of me and drives me nuts |
20:55 |
PeterL |
2022-02-28 20:52:46: is vex better or worse? at least with vex it is usually a big block of text in the middle of the night, so easy to skip over in the log |
20:57 |
awt |
PeterL: sometimes vex is funny |
20:58 |
signpost |
2022-02-28 20:58:20: awt: yeah, but keep in mind that tmsr failed first at assimilation, then at everything else. |
20:58 |
signpost |
2022-02-28 20:58:30: I'm not arguing with him because he's making me upset. |
20:59 |
* |
asciilifeform wonders why sees timestamps in almost erry msg |
20:59 |
* |
signpost messages |
21:00 |
* |
asciilifeform messages' << moar bug? |
21:00 |
asciilifeform |
2022-02-28 21:00:38: hmm and billymg's bot also recv'd barf? |
21:00 |
asciilifeform |
2022-02-28 21:00:41: http://paste.deedbot.org/?id=tTDv << what was sent |
21:01 |
asciilifeform |
2022-02-28 21:01:16: awt: with all due respect the current ver. of blatta imho inedibly buggy |
21:02 |
asciilifeform |
2022-02-28 21:01:52: a good %% of what asciilifeform threw in, thus far, didn't come out on any end, or came out mangled beyond recognition |
21:02 |
signpost |
2022-02-28 21:02:32: might want to get everyone up to date first, iirc that was a hypothesis on cause |
21:02 |
asciilifeform |
2022-02-28 21:02:40: aite |
21:04 |
asciilifeform |
awt: asciilifeform is thinking, for next spec rev., that timestamps in playbacks oughta be emitted outta band (e.g. wallop to irc client) rather than inband (i.e. chomping away part of space avail. for msg text) |
21:05 |
asciilifeform |
that way also could handle'em in a log bot appropriately (or not) |
| |
~ 20 minutes ~ |
21:25 |
awt |
asciilifeform: how do you know everyone but the bot didn't get your message? |
| |
↖ ↖ |
21:25 |
awt |
Which message is missing? |
21:29 |
awt |
asciilifeform: read log re: timestamps: http://logs.bitdash.io/pest/2022-02-26#1003810 |
21:29 |
bitbot |
Logged on 2022-02-26 21:46:49 awt[asciilifeform|billymg]: if your clock is far enough ahead of the speaker, blatta may think your last received message is newer than a message just sent, and will apply the timestamp. |
21:29 |
awt |
asciilifeform: read log re: timestamps: http://logs.bitdash.io/pest/2022-02-26#1003810 |
21:29 |
bitbot |
Logged on 2022-02-26 21:46:49 awt[asciilifeform|billymg]: if your clock is far enough ahead of the speaker, blatta may think your last received message is newer than a message just sent, and will apply the timestamp. |
21:33 |
* |
awt messages with a timestamp prepended |
21:36 |
awt |
I have this in my log going to your client: INFO 2022-02-27 18:18:44,597: [71.191.220.241:10628 asciilifeform] <- BROADCAST a hrm actually the issue... Did you receive? |
21:37 |
awt |
how do you know that bot received barf and isn't just producing barf? Why assume that? |
21:39 |
awt |
asciilifeform: I can't debug missing messages from you if you don't tell me what messages are missing |
21:39 |
awt |
signpost: yes - it's mostly my issue. |
21:39 |
awt |
signpost: yes - it's mostly my issue. |
21:45 |
awt |
asciilifeform: also if you belive others are not getting your messages, you can verify through the debug log which I have shared: http://share.alethepedia.com/blatta/logs/ |
21:46 |
awt |
asciilifeform: roger re: timestamps out of band |
| |
~ 35 minutes ~ |
22:22 |
awt |
pestbot: echo hello |
22:36 |
asciilifeform |
http://logs.bitdash.io/pest/2022-02-28#1003876 << good point awt |
22:36 |
bitbot |
Logged on 2022-02-28 21:25:24 awt[asciilifeform|billymg]: asciilifeform: how do you know everyone but the bot didn't get your message? |
22:36 |
asciilifeform |
http://logs.bitdash.io/pest/2022-02-28#1003876 << good point awt |
22:36 |
bitbot |
Logged on 2022-02-28 21:25:24 awt[asciilifeform|billymg]: asciilifeform: how do you know everyone but the bot didn't get your message? |
22:36 |
asciilifeform |
hm and still receiving self-echos, e.g. just nao 'asciilifeform[jonsykkel|awt|signpost] ...' |
22:36 |
asciilifeform |
and bot logged twice |
22:39 |
awt |
as per several previous comments asciilifeform we will be getting echos when there is whitespace at the end as long as jonsykkel is running 9983 |
22:39 |
asciilifeform |
2022-02-28 22:39:35: hmm |
22:40 |
awt |
at least, that's the best explanation I have for now |
22:40 |
asciilifeform |
2022-02-28 22:39:53: dunthink i put a whitespc at the end there tho |
22:40 |
awt |
if you tab complete, you'll get whitespace after the name |
22:40 |
asciilifeform |
2022-02-28 22:40:26: a |
22:41 |
* |
asciilifeform recalls nao |
22:41 |
asciilifeform |
2022-02-28 22:40:44: ty awt |
22:44 |
PeterL |
2022-02-28 22:39:53: awt: do I need to do anything to migrate the db from 9983 to 9982, or does that just happen automatically when I run 9982 the first time? |
22:44 |
awt |
PeterL: the migration happens automatically. Do back up your db, however. |
22:45 |
PeterL |
2022-02-28 22:41:10: I don't need no stinking backups, bonzai! (j/k) |
22:45 |
awt |
lol |
22:45 |
PeterL |
2022-02-28 22:41:33: brb, upgrading |
22:50 |
PeterL |
2022-02-28 22:46:26: hi again? |
22:51 |
awt |
wb PeterL |
22:51 |
awt |
pestbot: echo hello |
22:52 |
PeterL |
2022-02-28 22:47:59: awt: maybe change the example start script to not use --log-level since it is not an option anymore? |
| |
↖ |
22:52 |
awt |
PeterL: will do |
22:53 |
awt |
pestbot: echo hello |
22:59 |
pestbot |
2022-02-28 22:28:56: hello from pestbot |
22:59 |
PeterL |
2022-02-28 22:54:41: test |
23:02 |
awt |
lol finally |
23:02 |
PeterL |
2022-02-28 22:54:41: test |
23:02 |
awt |
pestbot: echo hello |
23:03 |
PeterL |
2022-02-28 22:57:25: finally? |
23:03 |
PeterL |
2022-02-28 22:57:59: is it normal to get a wall of text a couple minutes after connecting? |
23:04 |
awt |
PeterL: yeah |
23:04 |
pestbot |
2022-02-28 22:56:54: hello |
23:05 |
PeterL |
2022-02-28 23:00:14: I feel like with the new version there is a lot more lag than the previous version? |
23:07 |
awt |
PeterL: finally was wrt pestbot's echo |
23:07 |
awt |
PeterL: what I'm seeing with pestbot right now is that everything is going into the order buffer, which gets cleared out every 5 min. by default. |
23:09 |
awt |
PeterL: what I'm seeing with pestbot right now is that everything is going into the order buffer, which gets cleared out every 5 min. by default. |
23:11 |
pestbot |
2022-02-28 23:11:31: hello |
23:11 |
pestbot |
2022-02-28 23:11:31: hello |
23:16 |
awt |
PeterL: you can verify be looking for "message received out of order" in the debug log. |
23:17 |
awt |
Yep, I'm seeing way too many GETDATA messages from people that have not been offline |
23:19 |
awt |
I think message order is, tragically, getting messed up in the order queue and the chain tips are getting updated to the wrong messages. |
23:25 |
awt |
pestbot: echo hello |
23:25 |
pestbot |
2022-02-28 23:25:16: hello |
23:25 |
awt |
Oh looks like pestbot is finally up to date. |
23:32 |
jonsykkel |
2022-02-28 23:31:15: 123 |
23:32 |
signpost |
2022-02-28 23:32:09: 456 |
23:40 |
jonsykkel |
indeed |
23:41 |
awt |
pestbot: echo 789 |
23:42 |
pestbot |
2022-02-28 23:41:38: 789 |
23:50 |
awt |
pestbot: echo 10 11 12 |
23:50 |
pestbot |
10 11 12 |
23:58 |
jonsykkel |
getdataspam seems to have run its course, 24min |
23:59 |
awt |
jonsykkel: was just about to say I see your GETDATA packets |
23:59 |
awt |
Seeing a lot fewer timestamps now that my clock is not almost 10 minutes fast. |