When Sentry goes down/offline my entire app crashes?!

[mabasic]

I have recently implemented Sentry in a next.js application. We use a self hosted version of Sentry which is very underpowered and it frequently goes down. When this happens and when an error occurs in the app, sentry is unable to send the request and it crashes the entire app

Also, sentry cli fails to upload source maps and the whole pipeline crashes I've fixed this by changing the errorHandler function per instructions found in the errorHandler comments.

/**
     * When a CLI error occurs, the plugin will call this function.
     *
     * By default, it will call `invokeErr()`, thereby stopping Webpack
     * compilation. To allow compilation to continue and log a warning instead,
     * set this to
     *   (err, invokeErr, compilation) => {
     *     compilation.warnings.push('Sentry CLI Plugin: ' + err.message)
     *   }
     *
     * Note: `compilation` is typed as `unknown` in order to preserve
     * compatibility with both Webpack 4 and Webpack 5 types, If you need the
     * correct type, in Webpack 4 use `compilation.Compilation` and in Webpack 5
     * use `Compilation`.
     */
    errorHandler?: (
      err: Error,
      invokeErr: () => void,
      compilation: unknown
    ) => void;

I assumed that when sentry goes offline my app should continue working as normal?

@vladanpaunovic We have run extensive tests and concluded that it was not Sentry at fault after all. Thank you.

[vladanpaunovic]

Hey @mabasic, this is definitely an unintended behaviour which we didn't experience yet.

Our SDK is designed to keep your app intact even when Sentry is experiencing downtime.

As I couldn't reproduce this myself, can you please create an issue with the reproduction repository? Once this is in place, someone here will help you.