This repository was archived by the owner on Apr 6, 2026. It is now read-only.
feat(bot): replace fixed activity cycle with weighted random rotation#267
Merged
Conversation
Swaps the deterministic `itertools.cycle` + fixed 5-minute `tasks.loop` for a plain asyncio task that picks activities via weighted `random.choices` and sleeps a random 2–7 minutes between rotations. "Use / for commands" variants carry 3× weight so they remain the most frequent status. Adds four new flavor activities for more variety. Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
itertools.cycle+ fixed@tasks.loop(minutes=5)with a plainasynciotask that owns its own sleep timingrandom.choiceswith weights — "Use / for commands" variants are 3× more likely than flavor entriesrandom.uniform(120, 420))Why asyncio task instead of
tasks.loop+change_intervaltasks.looppre-computes_next_iterationbefore invoking the callback, so callingchange_interval()inside the callback adjusts the iteration after next — not the upcoming sleep. A plainasynciotask withawait sleep(...)owns its timing completely with no framework state to fight.Test plan
on_readyguard)🤖 Generated with Claude Code