Skip to content
This repository was archived by the owner on May 11, 2026. It is now read-only.

fix: replace silent catch with error logging#59

Closed
AmSach wants to merge 4 commits into
radiantly:mainfrom
AmSach:fix/silent-catch-error-handling
Closed

fix: replace silent catch with error logging#59
AmSach wants to merge 4 commits into
radiantly:mainfrom
AmSach:fix/silent-catch-error-handling

Conversation

@AmSach

@AmSach AmSach commented May 7, 2026

Copy link
Copy Markdown

Fixed a bug I found while browsing. Replaced the silent .catch(() => {}) with proper error logging in bot.js. Previously, when the bot failed to send a welcome message to a guild's system channel, the error was silently swallowed. Now it logs the error message for debugging.

Before:

.catch(() => {});

After:

.catch(err => console.error('Failed to send guild welcome message:', err.message));
``"

The original repo shows 16 open issues and 33 stars  this is a widely-used bot (60k+ servers), so proper error handling matters for maintainers to diagnose issues.

AmSach added 3 commits May 7, 2026 01:11
- Changed .catch(() => {}) to .catch(err => console.error(...))
- Now logs the error message instead of silently swallowing it
Signed-off-by: Aman Sachan <amansachan92905@gmail.com>
Signed-off-by: Aman Sachan <amansachan92905@gmail.com>
AmSach added a commit to AmSach/live-countdown-bot that referenced this pull request May 7, 2026
- Applied prettier --write to all JS files
- Trailing comma style was inconsistent across 12 files
- Resolves CI 'Check formatting' failure on PR radiantly#59
This fixes the Check formatting CI failure by applying consistent
Prettier formatting across all JavaScript files.

Signed-off-by: Aman Sachan <amansachan92905@gmail.com>
@AmSach AmSach force-pushed the fix/silent-catch-error-handling branch from c45e186 to b558906 Compare May 10, 2026 03:55
@radiantly

Copy link
Copy Markdown
Owner

Hi @AmSach, thank you for attempting to contribute. However:

  • I'm not a fan of AI slop, and you'll find this sentiment echoed by other maintainers.
  • Your commits show up as "Unverified". Possibly because you have vigilant mode turned on.
  • This repo is unmaintained and needs to be archived.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants