ftc2 / interview-notify Goto Github PK

When Gatekeep kicks users for breaking the no idling rule a priority 5 notification is triggered warning of a Netsplit.

sudo python3 interview_notify.py --topic yyyy --log-dir ~/.purple/logs/irc/[email protected]/#red-invites.chat --nick yyyy --mode red

(06:15:28 PM) XXXX left the room (Kicked by Gatekeeper (No idling. You may not stay in this channel without !queueing. (expires in 14m 59s))).

2023-09-01 04:37:14 INFO: parser: using "2023-08-26.185922-0600MDT.html"
2023-09-01 06:23:20 INFO: netsplit detected ⚠️
2023-09-01 07:17:52 INFO: netsplit detected ⚠️
2023-09-01 07:20:06 INFO: netsplit detected ⚠️
2023-09-01 07:39:27 INFO: netsplit detected ⚠️
2023-09-01 07:55:43 INFO: netsplit detected ⚠️
2023-09-01 08:47:48 INFO: netsplit detected ⚠️
2023-09-01 12:22:52 INFO: netsplit detected ⚠️
2023-09-01 13:10:42 INFO: netsplit detected ⚠️
2023-09-01 17:32:26 INFO: netsplit detected ⚠️
2023-09-01 18:15:28 INFO: netsplit detected ⚠️

9/1/23, 6:20 PMPriority 5
🔌 Netsplit detected – requeue within 10min!
(06:15:28 PM) XXXX left the room (Kicked by Gatekeeper (No idling. You may not stay in this channel without !queueing. (expires in 14m 59s))).

currently, there is a single log_parse() thread parsing the newest file, and when log_scan() finds a newer file, it sends a termination signal to the old log_parse() before spawning a new one.

in mixed log dir situation, if multiple files are being frequently updated, lines can be missed if the log_scan() thread doesn't switch to the new log fast enough (rn it scans for newer file every 1s).

having log_scan() make a separate log_parse() thread for each log file present (and adding new threads as new files appear) could be better i guess?

Code:

• python .\interview_notify.py --topic []-interview --log-dir C:\Users\[name]\AppData\Roaming\mIRC\logs\ --nick []

Scenario:
[02:12] * You were kicked by Gatekeeper (No idling. You may not stay in this channel without !queueing. (expires in 14m 59s))

Problem:

• Occasionally in a certain invite channel for a music tracker, the Gatekeeper will be booted from the server and will force everyone to requeue. I was not notified of when I was kicked.

I tested the <bot> is currently interviewing message in the channel and the notifier works fine there but didn't tell me when I was booted.

Additional suggestion:

• Is there a way to detect when the bot itself is booted from a channel? This notification would help let me know when I need to requeue

Hi, Is yourscript compatible with HexChat? I have it set up, but when it run the script only gets as far as this line the stops at:

2024-02-04 19:53:16 INFO: parser: using "Gatekeeper.log"

Here is my execution command:

python interview_notify.py --topic interview --log-dir "M:\Programs\HexChatPortable\Data\settings\logs\New Network" --nick xxxxxx --check-bot-nicks

Thanks for the effort