fix/recover from webhook goroutines

[motatoes]

• handle crashes in goroutine events
• include stacktrace in errors

Summary by CodeRabbit

• Bug Fixes

  • Enhanced error handling and logging for pull request and issue comment events.

• New Features

  • Improved logging for installation and issue comment events to aid in monitoring and debugging.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces improvements to error handling and logging in the backend/controllers/github.go file. By adding the runtime/debug package, the code now provides more robust panic recovery mechanisms in GitHub webhook event handlers. The changes focus on capturing detailed error information, including stack traces, which will help developers diagnose and troubleshoot unexpected issues during event processing.

Changes

File	Change Summary
backend/controllers/github.go	- Added runtime/debug import - Enhanced panic recovery in handlePullRequestEvent and handleIssueCommentEvent - Improved logging for GitHub webhook events

Possibly related PRs

• handle crashes in goroutine events #1857: Enhances error handling and includes panic recovery in the same GitHub event handler functions

Poem

🐰 A Rabbit's Log of Code Delight

In GitHub's webhooks, errors take flight
With stack traces clear and logging bright
Debug and recover, our code's new might
No silent failures shall dim our light! 🕵️‍♀️

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6b2ee65 and 93a6920.

📒 Files selected for processing (1)

• backend/controllers/github.go (3 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to 93a6920.

Security Overview

• 🔎 Scanned files: 1 changed file(s)

Detected Code Changes

Change Type	Relevant files
Enhancement	► github.go     Add detailed panic recovery logging with stack traces for webhook handlers

Diagnostics

• Code Scan ID: 8ff57476-17cb-4dca-8136-af29a0bc7343

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.