What's Changed

Full Changelog: v6.0.0...v6.0.1

miquelbeltran

Assets 2

26 May 06:13

v6.0.0

docs: Update README.rst by @ardinusawan in #86
ci: GitHub setup by @miquelbeltran in #112
refactor: fix static analysis errors by @miquelbeltran in #114
feat: Add set_customdata to RaygunSender, apply process level custom data w… by @turtlespin in #106
chore(deps): jsonpickle to >=4.0.4 by @miquelbeltran in #117
fix(provider)!: RaygunMessage object in on_grouping_key method by @miquelbeltran in #118
feat(provider)!: positioned wildcard matching by @miquelbeltran in #119
chore: Prepare for release 6.0.0 by @miquelbeltran in #121

New Contributors

Full Changelog: v5.0.0...v6.0.0

turtlespin, miquelbeltran, and ardinusawan

Assets 2

28 Feb 00:38

ProRedCat

5.0.0 Release

Breaking changes:

Bug Fixes:

Removes largest local/global variables in crash payload to ensure payload size limit is not breached (optional)
- We now provide enforce_payload_size_limit and log_payload_size_limit_breaches as configuration options, both enabled by default
- These control whether the provider will attempt to remove variables if there is an oversized payload and log which variables were removed

Assets 2

14 Aug 02:41

redJ4y

4.4.0 Release

Added RaygunHandler.from_sender() factory to construct a RaygunHandler instance using an existing RaygunSender. This allows for additional configuration of the sender.
Added a config parameter the to Flask and WSGI middleware provider constructors. This also allows for additional configuration of the sender.
The RaygunHandler now adds tags corresponding to the logging level, which now defaults to logging.ERROR.
Errors/exceptions sent via the RaygunHandler now have their message overriden by the logged message.

The RaygunHandler now attempts to capture exc_info from the record. This can be obtained if logger.exception() is used or if exc_info=True is set in the logger call.
- If exc_info cannot be obtained by the RaygunHandler, it no longer attempts to construct a RaygunErrorMessage with None values. Instead, it generates a fallback error message using information gathered from the record. This is essentially an error with a single stack frame representing the call to the logger.