Rollbar

Latest version: v1.0.0

Safety actively analyzes 629639 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 17

0.14.2

- Fix bug with file-based logging config in Python 3. See [277](https://github.com/rollbar/pyrollbar/issues/277)
- Fix bug in Django middleware when request has no META attribute. See [273](https://github.com/rollbar/pyrollbar/pull/273)

0.14.1

- Add Django middlewares that differentiate between 404 and other exceptions. See [270](https://github.com/rollbar/pyrollbar/pull/270)
- Make Werkzeug request handling more general. See [271](https://github.com/rollbar/pyrollbar/pull/271)
- Fix incorrect handling rollbar.init() arguments when using LOGGER in Django. See [235](https://github.com/rollbar/pyrollbar/pull/235)
- Use thread local storage for not thead-safe requests.Sessions. See [269](https://github.com/rollbar/pyrollbar/pull/269)
- Swallow known error that happens in add_person_data. See [268](https://github.com/rollbar/pyrollbar/pull/268)
- Only write a log about a rate limit once. See [267](https://github.com/rollbar/pyrollbar/pull/267)
- Adapt Django view monkey patch to support Django 2. See [257](https://github.com/rollbar/pyrollbar/pull/257)
- Add support request objects from Django REST framework. See [18](https://github.com/rollbar/pyrollbar/pull/18)
- Add support for Falcon framework requests. See [51](https://github.com/rollbar/pyrollbar/pull/51)
- Add support for Django Channels' AsgiRequest. See [272](https://github.com/rollbar/pyrollbar/pull/272)

0.14.0

- Create the configuration options, `capture_username` and `capture_email`. Prior to this release,
if we gather person data automatically, we would try to capture the id, email, and username.
Starting with this release by default we will only capture the id. If you set `capture_username`
to `True` then we will also attempt to capture the username. Similarly for `capture_email` with
the email. (See [262](https://github.com/rollbar/pyrollbar/pull/262))
- Create the configuration option `capture_ip`. This can take one of three values: `True`,
`'anonymize'`, or `False`. This controls how we handle IP addresses that are captured from
requests. If `True`, then we will send the full IP address. This is the current behaviour and the
default. If set to the string `'anonymize'` which is also available as the constant `ANONYMIZE` on
the `rollbar` module, we will mask out the least significant bits of the IP address. If set to
`False`, then we will not capture the IP address. (See [262](https://github.com/rollbar/pyrollbar/pull/262))
- Fix `request.files_keys` for Flask [263](https://github.com/rollbar/pyrollbar/pull/263)
- If you call `init` multiple times we will update the settings at each call. Prior to
this release we emitted a warning and did not update settings. [259](https://github.com/rollbar/pyrollbar/pull/259)
- Better Tornado support [256](https://github.com/rollbar/pyrollbar/pull/256)

0.13.18

- See Release Notes

0.13.17

- Fix deprecation warning related to Logging.warn
- Fix bug where non-copyable objects could cause an exception if they end up trying to get passed to
one of the logging methods.
- Fix bug where both `trace` and `trace_chain` could appear in the final payload, which is not
allowed by the API.

0.13.16

- Fix PyPI documentation

Page 3 of 17

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.