summaryrefslogtreecommitdiff
path: root/raven/contrib
Commit message (Collapse)AuthorAgeFilesLines
* Fix simple typo: postitively -> positively (#1358)Tim Gates2020-01-081-1/+1
| | | | There is a small typo in raven/contrib/tornado/__init__.py. Should read `positively` rather than `postitively`.
* fix: Flake8 updatesMarkus Unterwaditzer2018-12-153-9/+9
|
* Use correct kwarg in handle_exception() for Flask (#1300)Lars Mikkelsen2018-09-251-1/+10
| | | | | | | | | | | | | | | | | | | | * Use correct kwarg in handle_exception() for Flask The handle_exception() method is registered as a receiver of the got_request_exception signal. According to both the [documentation][1] and [source code][2] of Flask the got_request_exception signal passes the exception as `exception` rather than a `exc_info`. This is likely to have gone unnoticed since captureException() calls sys.exc_info() in the absence of an exception. On Python 3 we can use `__traceback__` to explicitly construct the `exc_info`. [1]: http://flask.pocoo.org/docs/1.0/api/#flask.got_request_exception [2]: https://github.com/pallets/flask/blob/1.0.2/flask/app.py#L1732 * doc: Add changelog
* fix: Keep user in log data if it came from django (#1246)Armin Ronacher2018-05-301-6/+8
|
* [FIX] TypeError on LambdaClient(transport=...)Alan Justino da Silva2018-05-191-1/+1
| | | | | TypeError: __init__() got multiple values for keyword argument 'transport' Because it has `get()`ing the 'transport' keyword, instead of `pop()`ing it.
* fix django sql hookAnton Shurashov2018-05-101-13/+17
|
* feat: Add a client for SanicArmin Ronacher2018-03-291-0/+224
|
* Fix Typo in docstring (#1195)Davide Muzzarelli2018-02-081-1/+1
|
* Corrected commentTomer Chachamu2018-01-241-1/+1
|
* fix(lambda): Process requestContext only if presentAshley Camba Garrido2018-01-021-3/+7
|
* allow subclasses of SentryHandler to be modified by the celery logging ↵Michael Pistrang2017-12-121-1/+1
| | | | signal, resolves #961
* fix error django VERSION remark (#1154)WeizhongTu2017-12-051-1/+2
| | | | | | | | | | * fix error django VERSION remark Applications New in Django 1.7. https://docs.djangoproject.com/en/1.8/ref/applications/#module-django.apps
* fix(django): Add support for Django 2.0 UrlresolverAshley Camba Garrido2017-12-051-5/+15
| | | | Fixes:#1127
* fix(django): Avoid deprecation warnings when calling is_authenticated (#1112)Ashley Camba2017-10-261-9/+12
|
* AWS Lambda Integration (#1107)Ashley Camba2017-10-131-0/+173
| | | | | | | | | | | | | | * Initial lambda integration * feature(lambda): Add lambda tests and client * Add D107 to ignore flake8 docs * Initial lambda integration * feature(lambda): Add lambda tests and client * Add reference to raven-python-lambda
* add application/octet-stream to non-cacheable typesDillon Dixon2017-09-281-6/+11
|
* fix(django): Fix django command with data option (#1078)Ashley Camba Garrido2017-09-261-1/+8
|
* fix(flask): Use request.remote_addr as fallback for flask too, fix testsAshley Camba Garrido2017-09-261-4/+7
|
* fix(django): Remove second user_info and fix testsAshley Camba Garrido2017-09-261-2/+1
|
* Always supply a user.ip_address valueMatt Robenolt2017-09-262-18/+26
| | | | | | | | | | | | | | | | | This is explicitly choosing to also parse the X-Forwarded-For header to yank out this value. Otherwise, the Sentry server relies only on the REMOTE_ADDR value which will always be wrong when when someone is behind a reverse proxy. This logic already exists in some other clients, and this has been brought up a number of times with users via tickets and support. Worth noting that it's potentially possible for this value to now be forged from a user, but the ramification of doing so is so low, it's not worth putting this behavior behind a feature flag IMO. The worst someone could do is make some data inside Sentry inaccurate and possibly confusing. No worse than the current state of the world where the data is completely inaccurate.
* Fix initialize import for Django < 1.7Alex Tomkins2017-09-162-7/+5
| | | | Fixes #1013 (honest!)
* Added Django setting to ignore expected Celery errorsdhoffman2017-09-161-1/+7
|
* Fix unavailable request data while using with REST framework #591 (#1061)eprikazc2017-09-122-10/+28
| | | | | | | | | | | | | | | | * Add DjangoRestFrameworkCompatMiddleware * Update DjangoRestFrameworkCompatMiddleware to not require get_response in constructor This is for compatibility with Django 1.10 and earlier * Add unit tests for DjangoRestFrameworkCompatMiddleware * Update docstring in install_middleware function * Convert DjangoRestFrameworkCompatMiddleware to be backwards-compatible * Make sure that middlewares are not set in test_request_data_unavailable_if_request_is_read
* Enable breadcrumbs in Celery (#1068)Václav Slavík2017-09-041-0/+2
|
* fix(flask): Add app.logger instrumentation (#1069)Ashley Camba2017-09-041-1/+3
| | | | | | | | | | | | | | * fix(flask): Add app.logger instrumentation Older versions of flask set app.logger.propagate to False, and it's reasonable to expect that users except app.logger to be instrumented if explictly setting logger=True in the sentry client. Fixes: PY-RAVEN #1030 app.logger log call messages are not send to sentry * Fix indentation
* Fix issue #1064: Resource leak when register_signal=FalseBijan Vakili2017-08-221-1/+1
|
* Cleanup for green doc8 testsAshley Camba Garrido2017-08-0910-12/+18
|
* Fix import locking to avoid recursion (fixes GH-1032)David Cramer2017-06-301-11/+15
|
* Make the logging_configured signal flask-onlyArnav Kumar2017-06-281-1/+5
|
* Fire signal after setup_logging is called for Flask usageArnav Kumar2017-06-271-1/+6
|
* Added tests and refactored.Jim Fulton2017-06-122-15/+29
| | | | | The first stab at this was cribbed off the zope integration. This is now a bit cleaner.
* added __future__ import that test runner wantsJim Fulton2017-06-071-0/+1
|
* fixed docstring title and formattingJim Fulton2017-06-071-2/+3
|
* Added support for logging integreation via ZConfig:Jim Fulton2017-06-072-0/+47
| | | | | | | http://zconfig.readthedocs.io/en/latest/using-logging.html (Note that the Zope integration also uses ZConfig, but adds lots of Zope-specific machinery that won't work elsewhere.)
* Ensure consistent fingerprint for SoftTimeLimitExceeded exceptionsAdam Charnock2017-05-241-1/+1
| | | | | | | I've been finding that ``SoftTimeLimitExceeded`` exceptions have not been grouped in the Sentry UI as I would have expected. I believe I have traced it down to the line changed in this pull request. They seemed to occasionally stop form new groups for non-obvious reasons. After looking around, it seems that ``sender`` (presumably a task instance) includes an object ID in its string representation. As a result, the fingerprint would be different for every celery worker process. This change will attempt to use the full task name (i.e. ``"my.app.tasks.do_it"``) before falling back to the original implementation.
* Merge pull request #964 from noirbizarre/gh-963-handle-exception-inheritanceDavid Cramer2017-03-051-4/+1
|\ | | | | Handle ignore_exceptions values being class or string
| * Handle both class and string for ignore_exceptions parameters (fix #963)Axel Haustant2017-02-181-4/+1
| |
* | Add lock around initializationfix/django-sys-hookDavid Cramer2017-02-211-22/+31
| |
* | [django] fix registration of hooksDavid Cramer2017-02-213-5/+17
|/ | | | | | | - utilize app.ready() for Django 1.7+ - ensure client is instantiated upon initialization (fixes sys.except_hook) Fixes GH-884
* fix recursive behavior of resolverDavid Cramer2017-02-171-2/+2
|
* [django] improve various request behaviorref/tastypie-testsDavid Cramer2017-02-151-10/+12
| | | | | | - expand tests to cover basic tastypie - correct leaking of request local in middleware - improve django test fundamentals
* Unused get_option helperDavid Cramer2017-02-151-6/+0
|
* [django] fix shared request not being available in thread contextfix/django-requestDavid Cramer2017-02-152-18/+5
|
* Kill bare exceptsArmin Ronacher2017-02-151-1/+1
|
* Move get_transaction_from_request to client to allow overrides (#933)Jon Ferreira2017-01-172-9/+6
|
* Support release and environment tags for Zope (#930)Fred van Dijk2016-12-191-0/+2
| | | In zope.conf's configuration spec, which will be passed on and processed by Raven.
* Remove six entirely and unify _compat into utils.compat (#812)Matt Robenolt2016-12-146-8/+8
|
* django: use our _compat.iterlistsiterlistsMatt Robenolt2016-11-261-3/+2
| | | | | | `six` wasn't vendored into Django until 1.5, so this explicitly is breaking support for 1.4. We already have this function vendored, so might as well use our copy instead.
* In Django HTTP request data, multiple values for same key are listsFrankie Dintino2016-11-211-0/+7
| | | | | | | | | | | | In a Django HttpRequest object, the request data is a QueryDict object, which is a dictionary-like class that supports multiple values for the same key. This is used, for instance, with <select multiple> form elements. In order to have the request data serialize into JSON correctly when there are multiple values, it is necessary to use QueryDict.iterlists() / QueryDict.lists() (python 2 and 3, respectively). Otherwise, the value passed to Sentry will contain only the last value in the query string.
* Improve matrix builds; Drop Python 2.6ref/improve-travisDavid Cramer2016-11-101-1/+1
| | | | | | | | | | | | - Add Flask-specific builds - Add Celery-specific builds - Restore Django dev build - Reduce Django builds to only focus on subset of versions - Expand norecursedirs - Drop Python 2.6 support (as deps are starting to) - Update pytest-django - Limit django-celery exposure - Correct django-celery 3.1 behavior
View Lorry Controller Status