Broken message expiry edits
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The bot no longer declines chat join requests after 30 minutes because https://docs.deno.com/deploy/migration_guide/#queues leads to [the callback](https://github.com/grammyjs/guard-bot/blob/25ccf6830665f7528a9f2f9452909efa808af118/bot.ts#L113) never being triggered. We have to either adopt a different queuing solution or maybe poll the database or just move off of deno deploy entirely.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading bot.ts around line 113 and the linked Deno Deploy queues migration guide to understand why the expiry callback is no longer triggered. Compare the issue's possible queue, database-polling, and hosting directions, then verify that chat join requests are declined after 30 minutes with the chosen approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, typescript
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100