Make sure total timeout is less than ping timeout or parallelize bots
Open
Nobody has claimed this yet.
testneeded
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
According to http://irclog.perlgeek.de/perl6/2016-08-30#i_13119980, if a bot is working for more than ~250 seconds it could get disconnected from a channel. We need to make sure that bots will stop any work before they hit the ping timeout, or parallelize them so they can respond to pings while still doing real work.
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
The issue names no files, tests, or entry points. Start by locating the bot work loop and IRC ping handling, then compare stopping work before the timeout with parallelizing ping responses; done means bots remain connected while real work runs.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100