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 application crashing without Sentry being configured #246

Merged
merged 1 commit into from
Dec 29, 2021

Conversation

pixeldesu
Copy link
Member

Fixes #242

If Sentry.init is not called, Sentry is still defined, but nothing inside it works properly, making checks outside hardly possible. Letting Sentry initialize without a DSN still works fine, as it just has nothing to report to.

Checked the logs and there are no exceptions etc.

@codecov
Copy link

codecov bot commented Dec 29, 2021

Codecov Report

Merging #246 (afece56) into master (4008d2f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   62.32%   62.32%           
=======================================
  Files          92       92           
  Lines        2121     2121           
=======================================
  Hits         1322     1322           
  Misses        799      799           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4008d2f...afece56. Read the comment docs.

@pixeldesu pixeldesu merged commit 66638ca into master Dec 29, 2021
@pixeldesu pixeldesu deleted the bugfix/sentry-init branch December 29, 2021 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not configuring Sentry breaks the application
3 participants