Update raven to 6.3.0 - Githubissues

There's a new version of raven available. You are currently using 5.8.1. I have updated it to 6.3.0

These links might come in handy: PyPI | Changelog | Repo

Changelog

6.3.0

[Core] Changed default timeout on http calls to 5 seconds

[Core] Fixed relative paths for traces generated on Windows

[Django] Fixed import issues for Django projects < 1.7

[Django] Fixed django management command data option

[Django/DRF] Added application/octet-stream to non-cacheable types in middleware

[Django] Added parsing X-Forwarded-For for user.ip_address

[Flask] Added request.remote_addr as fallback for ip addresses

[Lambda] Added initial AWS Lambda support with contrib.awslambda.LambdaClient

6.2.1

[Core] Fixed requirements in setup.py

6.2.0

[Core] get_frame_locals properly using max_var_size

[Core] Fixed raven initialization when logging._srcfile is None

[Core] Fixed import locking to avoid recursion

[Django] Fixed several issues for Django 1.11 and Django 2.0

[Django/DRF] Fixed issue with unavailable request data

[Flask] Added app.logger instrumentation

[Flask] Added signal on setup_logging

[ZConfig] Added standalone ZConfig support

[Celery] Fixed several issues related to Celery

6.1.0

Support both string and class values for ignore_exceptions parameters. Class values also support child exceptions.

Ensure consistent fingerprint for SoftTimeLimitExceeded exceptions

Add sample_rate configuration

fix registration of hooks for Django

6.0.0

Strip whitespace from DSNs automatically.

Add last_event_id accessor to Client.

Do not require sys.argv to be available any more.

Tags defined on a logging handler will now be merged with individual log record's tags.

Added explicit support for multidicts in the django client.

Refactored transports to support multiple URLs. This might affect you if you have custom subclasses of those. The main change is that the URL parameter moved from the constructor into the send method.

Corrected an issue with recursive route resolvers which commonly affected things like django-tastyepie.

Corrected an issue where Django's HTTP request was not always available within events.

5.32.0

Made raven python breadcrumb patches work when librato monkey patches logging.

5.31.0

Improved fix for the Django middleware regression.

5.30.0

Keep the original type for the django middleware settings if we change them.

5.29.0

Added register_logging_handler.

Removed bad mixin from django's WSGI middleware

Removed "support for extracing data from rest_framework" because this broke code.

5.28.0

Corrected an issue that caused close() on WSGI iterables to not be correctly called.

Fixes the new Django 1.10 MIDDLEWARE_CLASSES warning.

5.27.1

Bugfix for transaction based culprits.

5.27.0

Added support for extracting data from rest_framework in Django integration

Updated CA bundle.

Added transaction-based culprits for Celery, Django, and Flask.

Fixed an issue where ignore_exceptions wasn't respected.

5.26.0

Fixed potential concurrency issue with event IDs in the Flask integration.

Added a workaround for leakage when broken WSGI middlware or servers are used that do not call close() on the iterat.r

5.25.0

Added various improvements for the WSGI and Django support.

Prevent chained exception recursion

In environments which look like AWS Lambda or Google App Engine utilize the synchronous transport.

Added Celery config option to ignore expected exceptions

Improved DSN handling in Flask client.

5.24.0

Added support for Django 1.10.

Added support for chained exceptions in Python 3.

Fixed various behavior with handling template errors in Django 1.8+.

5.23.0

Sentry failures now no longer log the failure data in the error message.

5.22.0

Fixed template reporting not working for certain versions of Django.

5.21.0

Add formatted attribute to message events

Fill in empty filename if django fails to give one for template information on newer Django versions with disabled debug mode.

5.20.0

fixed an error that could cause certain SQL queries to fail to record as breadcrumbs if no parameters were supplied.

5.19.0

remove duration from SQL query breadcrumbs. This was not rendered in the UI and will come back in future versions of Sentry with a different interface.

resolved a bug that caused crumbs to be recorded incorrectly.

5.18.0

Breadcrumbs are now attempted to be deduplicated to catch some common cases where log messages just spam up the breadcrumbs.

Improvements to the public breadcrumbs API and stabilized some.

Automatically activate the context on calls to merge

5.17.0

if breadcrumbs fail to process due to an error they are now skipped.

5.16.0

exc_info is no longer included in logger based breadcrumbs.

log the entire logger name as category.

added a enable_breadcrumbs flag to the client to allow the enabling or disabling of breadcrumbs quickly.

corrected an issue where python interpreters with bytecode writing enabled would report incorrect logging locations when breadcrumb patching for logging was enabled.

5.15.0

Improve thread binding for the context. This makes the main thread never deactivate the client automatically on clear which means that more code should automatically support breadcrumbs without changes.

5.14.0

Added support for reading git sha's from packed references.

Detect disabled thread support for uwsgi.

Added preliminary support for breadcrumbs.

Note: this version adds breadcrumbs to events. This means that if you run a Sentry version older than 8.5 you will see some warnings in the UI. Consider using an older version of the client if you do not want to see it.

5.13.0

Resolved an issue where Raven would fail with an exception if the package name did not match the setuptools name in some isolated cases.

5.12.0

Empty and otherwise falsy (None, False, 0) DSN values are now assumed to be equivalent to no DSN being provided.

5.11.2

Added a workaround for back traceback objects passed to raven. In these cases we now wobble further along to at least log something.

5.11.1

The raven client supports the stacktrace to be absent. This improves support with celery and multiprocessing.

5.11.0

Client.configure_logging has been removed, and handlers will not automatically be added to 'sentry' and 'raven' namespaces.

Improved double error check

Restored support for exc_info is True.

5.10.2

Remember exceptions in flight until the context is cleared so that two reports with the same exception data do not result in two errors being logged.

Allow logging exclusions.

5.10.1

Fixed a problem where bytes as keys in dictionaries caused problems on data sanitization if those bytes were outside of the ASCII range.

Django client no longer requires the user object to be a subclass of the base model.

Corrected an issue with the Django log handler which would cause a recursive import.

5.10.0

Restore template debug support for Django 1.9 and newer.

Correctly handle SSL verification disabling for newer Python versions.

5.9.2

Correct behavior introduced for Django 1.9.

5.9.1

Support for isolated apps in Django 1.9.

5.9.0

The threaded worker will now correctly handle forking.

The 'environment' parameter is now supported (requires a Sentry 8.0 server ).

'tags' can now be specified as part of a LoggingHandler's constructor.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

uppsaladatavetare / foobar-api

Update raven to 6.3.0 #62

Changelog

6.3.0

6.2.1

6.2.0

6.1.0

6.0.0

5.32.0

5.31.0

5.30.0

5.29.0

5.28.0

5.27.1

5.27.0

5.26.0

5.25.0

5.24.0

5.23.0

5.22.0

5.21.0

5.20.0

5.19.0

5.18.0

5.17.0

5.16.0

5.15.0

5.14.0

5.13.0

5.12.0

5.11.2

5.11.1

5.11.0

5.10.2

5.10.1

5.10.0

5.9.2

5.9.1

5.9.0

Codecov Report