Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Added the regex for discarding the sentry issues #3269

Merged
merged 4 commits into from
Nov 19, 2024

Conversation

devendrafyle
Copy link
Contributor

@devendrafyle devendrafyle commented Nov 19, 2024

Clickup

https://app.clickup.com/t/86cx3rrh6

Code Coverage

Please add code coverage here

UI Preview

Please add screenshots for UI changes

Summary by CodeRabbit

  • Bug Fixes
    • Enhanced error handling by expanding the error patterns ignored by Sentry, improving clarity in error reporting.

Copy link

coderabbitai bot commented Nov 19, 2024

Walkthrough

The changes in this pull request enhance the Sentry error handling configuration in the src/main.ts file. The ignoreErrors array in the Sentry.init method has been expanded to include new error patterns, including specific string literals and regular expressions. This adjustment allows Sentry to ignore a wider range of non-critical errors, improving the clarity of error reporting while maintaining the existing functionality of the beforeSend function.

Changes

File Change Summary
src/main.ts Expanded ignoreErrors array in Sentry.init to include additional error patterns for better error handling.

Possibly related PRs

Suggested labels

size/S

Suggested reviewers

  • Aniruddha-Shriwant
  • Chethan-Fyle
  • arjunaj5

In the code, we dance and play,
Ignoring errors, come what may!
Sentry's new tricks, oh what a sight,
Clarity shines, errors take flight!
With regex and strings, we pave the way,
For smoother reports, hip-hip-hooray! 🎉


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 959c37d and 2c9c1de.

📒 Files selected for processing (1)
  • src/main.ts (1 hunks)
🔇 Additional comments (1)
src/main.ts (1)

42-51: 🛠️ Refactor suggestion

Listen here, partner! Your error patterns need some style, Thalaiva style! 🕶️

The patterns are working but let me tell you something with swag:

  1. You've mixed string literals and regex patterns like mixing rice with curry. Let's make it consistent!
  2. Those inline comments are good, but they're hiding in the shadows like a villain. Let's make them shine!
  3. Some patterns might be too specific, making them miss similar errors like missing a punch in an action scene!

Here's how we roll in style:

  ignoreErrors: [
+   // Basic error captures
    'Non-Error exception captured',
    'Non-Error promise rejection captured',
    'unhandledError',
+
+   // Geocoding and Maps related errors
-   /Could not load "geocoder"/,
+   /Could not load ["']geocoder["']/,
-   /ChunkLoadError: Loading chunk \d+ failed/,
+   /ChunkLoadError: Loading chunk/,
+
+   // Generic error patterns
    /0 Unknown Error/,
-   /The Google Maps JavaScript API could not load/,
+   /Google Maps JavaScript API could not load/,
-   /kCLErrorDomain error/,
+   /kCLErrorDomain error \d+/,
  ],

Mind-blowing changes, right? 🎭 Let me explain like a boss:

  1. Grouped related errors together for better readability
  2. Made regex patterns more flexible to catch similar errors
  3. Added section comments to explain the error categories

Let's verify if we're not missing any errors, style:


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
🪧 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 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.

@github-actions github-actions bot added the size/XS Extra Small PR label Nov 19, 2024
src/main.ts Outdated
Comment on lines 46 to 50
/Could not load "geocoder"/,
/ChunkLoadError: Loading chunk \d+ failed/,
/Http failure response for .*: 0 Unknown Error/,
/unhandledError/,
/The Google Maps JavaScript API could not load/,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added regex expression to ignore similar kind of issues

src/main.ts Outdated
'Non-Error promise rejection captured',
'Could not load "geocoder"',
/Could not load "geocoder"/,
/ChunkLoadError: Loading chunk \d+ failed/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you add example of how this error title looks like?

src/main.ts Outdated
/Http failure response for .*: 0 Unknown Error/,
/unhandledError/,
/The Google Maps JavaScript API could not load/,
/The operation couldn’t be completed\. \(kCLErrorDomain error \d+\)/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we just add kclErrorDomain error why the earlier text is needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to remove only these specific errors, yes kclErrorDomain error will also work

src/main.ts Outdated
/Could not load "geocoder"/,
/ChunkLoadError: Loading chunk \d+ failed/,
/Http failure response for .*: 0 Unknown Error/,
/unhandledError/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/unhandledError/ -> 'unhandledError' if not using any regex - also move this to top where all strings related error messages are defined

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

src/main.ts Outdated
'Could not load "geocoder"',
/Could not load "geocoder"/,
/ChunkLoadError: Loading chunk \d+ failed/,
/Http failure response for .*: 0 Unknown Error/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we just add 0 Unknown Error? since I've seen this issue occurring while fetching svgs or other files as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok we can do this, in discarded issues I found it for HTTP failure so added this

src/main.ts Outdated
Comment on lines 45 to 46
'Could not load "geocoder"',
/Could not load "geocoder"/,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's different in both?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed removing this

Copy link

Unit Test Coverage % values
Statements 95.95% ( 19187 / 19996 )
Branches 91.11% ( 10567 / 11597 )
Functions 94.35% ( 5729 / 6072 )
Lines 95.98% ( 18316 / 19082 )

@devendrafyle devendrafyle merged commit 169b43f into master Nov 19, 2024
10 checks passed
devendrafyle added a commit that referenced this pull request Nov 19, 2024
* fix: Added the regex for discarding the sentry issues

* Added missed issue to ignore

* Updated the errors

* minor comments fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Extra Small PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants