summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release: 6.4.0.dev0 → 6.4.06.4.0releases/6.4.0Ashley Camba Garrido2017-12-112-2/+2
|
* Update changelogAshley Camba Garrido2017-12-111-0/+5
|
* Remove tagging in bumpversion minorAshley Camba Garrido2017-12-111-1/+1
|
* Release: 6.3.0 → 6.4.0.dev0Ashley Camba Garrido2017-12-112-6/+7
|
* Extract self.fields into methodAshley Camba Garrido2017-12-111-19/+20
|
* fix processor docstringsRodrigo Guzman2017-12-111-2/+5
|
* convert_options() handles sensitive_keysRodrigo Guzman2017-12-111-0/+1
| | | | This is so that the sensitive_keys can be specified in django settings.
* Add processor that sanitizes configurable keysRodrigo Guzman2017-12-113-18/+144
| | | | | | | The logic of the new processor is almost identical to the logic of the existing SanitizePasswordsProcessor, so this commit also changes the implementation of SanitizePasswordsProcessor to avoid code-duplication. It now inherits from the new SanitizeKeysProcessor.
* 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 tests by pinning pytest for python 3.3Ashley Camba Garrido2017-12-051-0/+1
|
* Remove non-existant tox env from travisAshley Camba Garrido2017-12-051-3/+0
|
* Quickfix (dirty) for middleware testAshley Camba Garrido2017-12-051-2/+1
|
* Update travisAshley Camba Garrido2017-12-051-0/+6
|
* fix(django): Add support for Django 2.0 UrlresolverAshley Camba Garrido2017-12-054-6/+66
| | | | Fixes:#1127
* Refactored base codeMax Murashov2017-11-228-90/+56
|
* Fix flake8 errorAshley Camba Garrido2017-11-221-1/+0
|
* Fix breadcrumb log handling docs.Adam Wróbel2017-11-212-16/+22
| | | | | | | | | | | | | | | The documentation stated that handlers should return `False` to skip log recording while it is in fact the opposite any value that evaluates to true will skip recording. Additionally: 1. Added note about the useful `allow_level` param to `ignore_logger`. 2. Added info about one-callback per logger name limit. 3. Explained that callbacks need to be registered for initial logger names – that parent logger names do not influence breadcrumb recording. 4. Removed confusing note about `ignore_logger` from method __doc__. `register_special_log_handler` should be used for special handling of framework logging.
* Update travis.yml with releases - fix branch specAshley Camba2017-11-201-1/+1
|
* Add release braches to travisAshley Camba Garrido2017-11-201-1/+1
|
* Fix Code Climate linkHsiaoming Yang2017-11-201-1/+1
|
* include raven/contrib/zconfig/component.xml in manifestVincent Bernat2017-11-131-0/+1
| | | | This file is needed to run unittests.
* Remove test dependency on pytest-assumeVincent Bernat2017-11-131-1/+0
| | | | | This was added in #1056 by @ashwoods. Unless I am mistaken, this module is not used by raven tests and do not modify its behavior either.
* Update flake8 settingsAshley Camba Garrido2017-11-071-1/+1
|
* added doco for user context and tags for logging integrationsBen Fitzhardinge2017-11-071-0/+7
|
* Add raven installation instructions for python frameworksNeil Manvar2017-11-0310-0/+86
| | | | If someone lands on one of these pages (e.g. django), they should have all the relevant information (including installation instructions) to get set up.
* docs: fix PasteDeploy urlPhilippe Pepiot2017-11-031-1/+1
|
* use abspath (#1129)MeredithAnya2017-11-031-1/+1
|
* Forgot spaceluisulloa2017-11-031-1/+1
|
* Third time is the charm, trying to make flake8 pass without having the ↵luisulloa2017-11-031-0/+1
| | | | output in travisci
* Making previous push flake 8 compatibleluisulloa2017-11-031-3/+5
|
* Allow to specify user context in logging handlerluisulloa2017-11-031-1/+3
|
* ci: Fix upload directory for deployment task6.3.0Jan Michael Auer2017-10-291-1/+1
|
* ci: Fix deploy stage (#1121)Jan Michael Auer2017-10-291-3/+1
|
* Release: 6.3.0.dev0 → 6.3.0 (#1120)Ashley Camba2017-10-292-3/+4
| | | | | | * Fix doc index to lambda * Release: 6.3.0.dev0 → 6.3.0
* stacks: Fix "filename" not being relative for traces generated on WindowsChristoph Reiter2017-10-291-1/+2
| | | | Instead of hardcoding "/" use os.sep
* fix(django): Avoid deprecation warnings when calling is_authenticated (#1112)Ashley Camba2017-10-261-9/+12
|
* Changelog format (#1114)Ashley Camba2017-10-263-194/+213
| | | | | | * Fix doc index to lambda * Reformat changelog and preparing bumpversion functionality
* Add bumpversion config (#1115)Ashley Camba2017-10-263-6/+36
| | | | * Add bumpversion config
* Raise default urllib timeout to 5 seconds (#1113)Ashley Camba2017-10-221-1/+1
|
* ci: Use probot to release (#1111)Jan Michael Auer2017-10-193-11/+19
| | | | | | | | | | * ci(travis): Deploy tags to S3 * ci(release): Activate the release bot * meta(changelog): Move the changelog to the standard location * ci(travis): Set python version explicitly on deploy
* AWS Lambda Integration (#1107)Ashley Camba2017-10-137-1/+417
| | | | | | | | | | | | | | * 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 D107 to ignore flake8 docsAshley Camba Garrido2017-10-101-1/+1
|
* refactor(tests) Use marker to skip tests that depend on a git repoAshley Camba Garrido2017-10-102-8/+9
|
* 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-263-8/+10
|
* fix(django): Remove second user_info and fix testsAshley Camba Garrido2017-09-262-3/+8
|
* Always supply a user.ip_address valueMatt Robenolt2017-09-266-23/+91
| | | | | | | | | | | | | | | | | 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 repo name for future refAshley Camba Garrido2017-09-261-1/+1
|
* Prepare next release cycleAshley Camba Garrido2017-09-262-13/+16
|