In reference to getsentry/docker-sentry#210 (comment) it would be great to get a better and more complete documentation on how to work with the getsentry/sentry docker images

• 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

I saw this: https://github.com/errbit/errbit/blob/master/docs/deployment.md

Since the server already hosts cpanel I want to provide its own subdomain cert &key and let errbit serve itself over HTTPS on some non-conventional port. I didn't find a way to specify that in environment config, tough.

I propose to add an entrypoint script that checks for a SERVE_HTTPS=1 and runs the appropriate

We need to look into this and possibly file a bug as the event's end point isn't returning a sample json model for events.

The doc for captureException says:

If exc_info is not provided, or is set to True, then this method will perform the exc_info = sys.exc_info() and the requisite clean-up for you.

From the direct code however there appears to be no cleanup being done here?

https://github.com/getsentry/raven-python/blob/03559bb05fd963e2be96372ae89fb0bce751d26d/raven/base.py#L804-L824

It would be ni

Trying to upgrade to 1.1 from the old 0.11 is a nightmare because you don't provide any documentation. I finally found #185 which contains a link to this upgrade guide for the parent sentry-php library which, while helpful, is still woefully inadequate.

Specifically, the following options I was using just say "Removed" in th

(moved from #128)

as per discussion on rq/rq#1003, the following would be very useful (and I think aren't implemented at present):

• time since the job started
• job queue time

You should be able to get the required data from enqueued_at and started_at.

It's easy to get overwhelmed by the messages. Docs should demonstrate how to filter out transport failures which don't matter to you (e.g. sentry filtering out web-crawler errors).

Can you guys update your example to include a custom express.js server? The Next.js example you have is too trivial for real world situations so it'd be much more helpful to show how to use bugsnag in cases where you'd have custom routes being served by express. (I know that API routes exist now. but they didn't exist before so it'd be nice to show case common use cases within Next.js)

We're cu

Because first JDK 1.8 release was published 5.5 years ago and now I don't know any libraries, which work incorrect with JDK 1.8, maybe you can migrate your adapter to JDK 1.8?

If you do this, you could use Java 8 features, like java.time and could migrate to Spring Boot 2.2.0

Dependencies

{
    "@babel/runtime": "^7.1.2",
    "add": "^2.0.6",
    "axios": "^0.18.0",
    "babel-plugin-transform-flow-strip-types": "^6.22.0",
    "lodash": "^4.17.10",
    "mobx": "^4.3.1",
    "mobx-react": "^5.1.0",
    "moment": "^2.22.2",
    "native-base": "^2.8.1",
    "numeral": "^2.0.6",
    "react": "16.6.0-alpha.8af6728",
    "react-native": "0.57.1",
   

Description

A lot of console.warn yellow warning message when the data pass to leaveBreadcrumbs contains functions.

Describe the solution you'd like