0265f6e70c
* fix: prevent Telegram polling errors from blocking container startup (#989) This fix addresses the issue where the container gets stuck in an endless loop of Telegram connection errors when the bot is configured but Telegram is unreachable during startup. Changes: - Add 10-second startup delay before initializing Telegram polling to allow the system to settle - Implement exponential backoff (5s to 5min) when Telegram connection fails - Add rate-limited error logging (max once per minute per user) to reduce log spam and prevent event loop blocking - Track error state per user to manage backoff independently - Auto-reset error state on successful connection - Update tests to account for new error state tracking Fixes #989 * fix: prevent task name truncation when creating from inbox Changes: - Change task.name from VARCHAR(255) to TEXT to prevent any potential truncation - Change inbox_items.title and cleaned_content from VARCHAR(255) to TEXT - Add integration test to verify long task names are preserved - Add unit test to verify cleaned_content doesn't truncate While investigation showed no actual truncation occurring in the codebase, this defensive fix ensures unlimited text length for task names and inbox content, eliminating any possibility of truncation at the database level. Fixes #1016 |
||
|---|---|---|
| .. | ||
| applyPerms.test.js | ||
| functional-services.test.js | ||
| inboxProcessingService.test.js | ||
| permissionsService.test.js | ||
| rolesService.test.js | ||
| telegramAuth.test.js | ||
| telegramPoller.test.js | ||
| userService.test.js | ||