asciilifeform: | apol. for noise, but must test bot : http://logs.nosuchlabs.com/log/trilema/2019-08-11#1927570 | [18:21] |
snsabot: | Logged on 2019-08-11 18:20:41 asciilifeform: lobbes, mp_en_viaje : did feedbot actually emit irc lines in #e ? cuz i'm not seeing either http://logs.minigame.biz/2019-08-03.log.html#t14:41:25 or http://logs.minigame.biz/2019-08-06.log.html#t16:55:36 or http://logs.minigame.biz/2019-08-07.log.html#t19:00:04 in mine ? | [18:21] |
mp_en_viaje: | asciilifeform, i was tuned out aug2-8. | [18:25] |
mp_en_viaje: | **** ENDING LOGGING AT Fri Aug 2 08:47:20 2019 | [18:25] |
mp_en_viaje: | **** BEGIN LOGGING AT Thu Aug 8 21:04:21 2019 | [18:25] |
asciilifeform: | right but evidently feedbot was here ? | [18:25] |
asciilifeform: | and emitted these ln | [18:25] |
mp_en_viaje: | i think so yes. since they're in the lobbesbot log. possibly diana_coman or lobbes have it in their local log ? | [18:26] |
lobbes: | asciilifeform: according to your index number scheme, this is the first line >> http://logs.nosuchlabs.com/log/eulora/2019-08-11#1000000 | [18:26] |
snsabot: | Logged on 2019-08-11 18:21:17 asciilifeform: apol. for noise, but must test bot : http://logs.nosuchlabs.com/log/trilema/2019-08-11#1927570 | [18:26] |
asciilifeform: | ( unless lobbes's item somehow puts feedbot as specialcase in all logs ? ) | [18:26] |
asciilifeform: | lobbes: i noticed earlier, hence the q | [18:26] |
snsabot: | Logged on 2019-08-11 18:21:57 asciilifeform: http://logs.nosuchlabs.com/log/eulora/2019-08-11#1000000 << bot does work. but observe, this is index 1000000 ! i.e. 1st line it ever saw ?!! | [18:26] |
lobbes: | aa odd. lemme check my logs | [18:27] |
lobbes: | http://logs.minigame.biz/2019-08-08.log.html#t17:25:29 << first record of join, at least | [18:27] |
lobbesbot: | Logged on 2019-08-08 17:25:29: *** Joins: snsabot (~snsabot@161.0.121.200) | [18:27] |
asciilifeform: | there's a whole buncha folx here, one of'em has gotta have raw e.g. znc log from 8/3, 8/6, 8/7 | [18:28] |
asciilifeform: | lobbes: find all of its joins plz ? | [18:28] |
lobbes: | and no record of anything else being said since then | [18:28] |
asciilifeform: | ( and parts ) | [18:28] |
lobbes: | that was the first that I saw http://logs.minigame.biz/search/?q=snsabot | [18:28] |
asciilifeform: | lobbes: grep plz for these, and at same time for all feedbot lines | [18:28] |
mp_en_viaje: | asciilifeform, http://logs.minigame.biz/search/?q=snsabot | [18:29] |
lobbes: | connectolade is logged in that logger | [18:29] |
mp_en_viaje: | you only joined on 8th, how could you have seen lines from before 8th ? | [18:29] |
asciilifeform: | mp_en_viaje: was supposed to have sat here from day1 of snsabot . evidently did not. currently looking in its log to see why | [18:30] |
mp_en_viaje: | aok | [18:30] |
asciilifeform: | almost certainly answer is http://trilema.com/2019/trilema-goes-dark/#comment-130820 | [18:31] |
mp_en_viaje: | ah ok | [18:31] |
mp_en_viaje: | no big deal anyways. | [18:31] |
asciilifeform: | well no this is a potentially catastrophic bugola | [18:31] |
asciilifeform: | i.e. when joining chans, there is a chance that fails | [18:32] |
asciilifeform: | will have to add routine which verifies that we're actually ~in~ the specified chans, and ring alarm if not | [18:32] |
asciilifeform: | cuz apparently the 'wait 20s after auth' does not 100\% deterministically force !! | [18:32] |
mp_en_viaje: | hm | [18:33] |
asciilifeform: | at the risk of log clutter, observe: | [18:34] |
asciilifeform: | # Auth to server | [18:34] |
asciilifeform: | send("NICK \%s\r\n" \% Nick) | [18:34] |
asciilifeform: | send("USER \%s \%s \%s :\%s\r\n" \% (Nick, Nick, Nick, Nick)) | [18:34] |
asciilifeform: | send("NICKSERV IDENTIFY \%s \%s\r\n" \% (Nick, Pass)) | [18:34] |
asciilifeform: | [18:34] | |
asciilifeform: | time.sleep(Join_Delay) # wait to join until fleanode eats auth | [18:34] |
asciilifeform: | [18:34] | |
asciilifeform: | # Join selected channels | [18:34] |
asciilifeform: | for chan in Channels: | [18:34] |
asciilifeform: | logging.info("Joining channel '\%s'..." \% chan) | [18:34] |
asciilifeform: | send("JOIN #\%s\r\n" \% chan) | [18:34] |
asciilifeform: | [18:34] | |
asciilifeform: | while connected: | [18:34] |
asciilifeform: | ... | [18:34] |
asciilifeform: | see, 1st auths, then awaits fleanode to eat the auth (so can join e.g. #t, where +r is in effect, but without waiting for any fleanode-specific messages) | [18:34] |
asciilifeform: | then operates until disconnected | [18:34] |
asciilifeform: | Join_Delay is presently 20s. | [18:34] |
asciilifeform: | (empirically derived) | [18:35] |
asciilifeform: | currently log set to 'catastrophic only' debug level, but dollars to doughnuts it was same problem as there , the delay proved insufficient | [18:37] |
asciilifeform: | there are 3 possible pills : 1) increase delay (and there is no guarantee from fleanode re what suffices) 2) do as ben's bot did, and await the fleanode-specific 'you've been authed' string when connecting 3) perform test re which chans we are in, when connected, and retry until the set of which-chans is equal to the config'd set | [18:38] |
mp_en_viaje: | asciilifeform, but #eulora is open, can join with no reg | [18:39] |
Comments feed: RSS 2.0