The watchdog should work based on ping events
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Basically, the watchdog ensures that bots are not stuck in some weird state. Currently it works like this:
https://github.com/perl6/whateverable/blob/7f79d1d1d4cf4d791ad1fca0c0db0e41b6fc36fb/lib/Whateverable.pm6#L181-L185
In other words, someone must send a message to the channel every so often, otherwise bots commit mass suicide thinking that they're disconnected. One of the motivations for this feature is this bug: https://github.com/zoffixznet/perl6-IRC-Client/issues/40
Currently there's no way to handle pings in IRC::Client, so there's no better way to do that. I filed a feature request here:
https://github.com/zoffixznet/perl6-IRC-Client/issues/50
That said, the issue is that sometimes nobody says anything for relatively long periods of time (more than 30 minutes). This forces us to have high timeouts, which is again less than awesome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the watchdog logic in lib/Whateverable.pm6 at lines 181-185, then review the linked IRC::Client issues about handling IRC ping events. Done means the watchdog remains healthy during quiet channels by using ping events instead of requiring periodic channel messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100