• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package

Description

OSX build notes have the following line
brew install automake berkeley-db4 libtool boost --c++11 miniupnpc openssl pkg-config protobuf python3 qt libevent

However, the boost --c++11 isn't a valid command anymore. Need to update it

Currently this is the source of a potential memory leak (see #50), since Raven will continue to hold a reference our original dataCallback which has the store implicitly bound into it.

Additionally, we hard code where in the context we put the state, (data.extra.state), so the second call will cause any context provided by the first call to be overwritten.

I can foresee a possible us

I'm a scheme novice, but I would happy to donate some time to the more tedious tasks associated with managing the Raven project (e.g., reviewing documentation, testing functionality, reviewing package submissions, etc.). Please let me know if you see opportunities for me to contribute. Thanks.

https://github.com/damiencaselli/ember-cli-sentry/blob/07139303b395858009a0c23a0078c587064d3cf5/README.md#L132-L140

I don't think that this section is entirely accurate.

AFAIK:

• cdn.ravenjs.com is only required, if the user chooses to load Raven.js from the CDN.
• app.getsentry.com is not required for on-premise setups and should be replace

Basic strategies:

• Exponential backoff in case of server/connection errors
• N retries in case of quote exceeded limit

Possibly using retriable.cr shard.

as suggested by @dcramer in https://github.com/getsentry/sentry/pull/16116/files#diff-aa34cb9acf9a36938078d3c80d01a25a
it might be a good pattern to mock sentry TOGETHER with the testkit

jest.mock('@sentry/browser', () => {
    ...Sentry,
   testkit,
   init: options =>
       SentryBrowser.init({ ...options, transport: sentryTransport  })
})

The --chroot flag isn't mentioned in nest-cli's help.

$ nest --help
nest [FLAGS] SUBCOMMAND [SUBCOMMANDS'S FLAGS]

Raven-OS's package manager.

FLAGS
    -h, --help       Prints help information
    -v               Sets the level of verbosity
    -V, --version    Prints version information

SUBCOMMANDS
    help         Prints this message or the help of the given subcomma