search

nsiregar / pegelinux

Blog aggregator for pegelinux community
https://pegelinux.id
MIT License
10 stars 9 forks source link

Bump sentry-sdk from 0.13.2 to 0.16.2 #188

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps sentry-sdk from 0.13.2 to 0.16.2.

Release notes

Sourced from sentry-sdk's releases.

0.16.2

  • New (optional) integrations for richer stacktraces: pure_eval for additional variables, executing for better function names.

0.16.1

  • Flask integration: Fix a bug that prevented custom tags from being attached to transactions.

0.16.0

  • Redis integration: add tags for more commands
  • Redis integration: Patch rediscluster package if installed.
  • Session tracking: A session is no longer considered crashed if there has been a fatal log message (only unhandled exceptions count).
  • Breaking change: Revamping of the tracing API.
  • Breaking change: before_send is no longer called for transactions.

0.15.1

  • Fix fatal crash in Pyramid integration on 404.

0.15.0

  • Breaking change: The ASGI middleware will now raise an exception if contextvars are not available, like it is already the case for other asyncio integrations.
  • Contextvars are now used in more circumstances following a bugfix release of gevent. This will fix a few instances of wrong request data being attached to events while using an asyncio-based web framework.
  • APM: Fix a bug in the SQLAlchemy integration where a span was left open if the database transaction had to be rolled back. This could have led to deeply nested span trees under that db query span.
  • Fix a bug in the Pyramid integration where the transaction name could not be overridden at all.
  • Fix a broken type annotation on capture_exception.
  • Basic support for Django 3.1. More work is required for async middlewares to be instrumented properly for APM.

0.14.4

  • Fix bugs in transport rate limit enforcement for specific data categories. The bug should not have affected anybody because we do not yet emit rate limits for specific event types/data categories.
  • Fix a bug in capture_event where it would crash if given additional kwargs. Thanks to Tatiana Vasilevskaya!
  • Fix a bug where contextvars from the request handler were inaccessible in AIOHTTP error handlers.
  • Fix a bug where the Celery integration would crash if newrelic instrumented Celery as well.

0.14.3

  • Attempt to use a monotonic clock to measure span durations in Performance/APM.
  • Avoid overwriting explicitly set user data in web framework integrations.
  • Allow to pass keyword arguments to capture_event instead of configuring the scope.
  • Feature development for session tracking.

0.14.2

  • Fix a crash in Django Channels instrumentation when SDK is reinitialized.
  • More contextual data for AWS Lambda (cloudwatch logs link).

0.14.1

  • Fix a crash in the Django integration when used in combination with Django Rest Framework's test utilities for request.
  • Fix high memory consumption when sending a lot of errors in the same process. Particularly noticeable in async environments.

0.14.0

Changelog

Sourced from sentry-sdk's changelog.

0.16.2

  • New (optional) integrations for richer stacktraces: pure_eval for additional variables, executing for better function names.

0.16.1

  • Flask integration: Fix a bug that prevented custom tags from being attached to transactions.

0.16.0

  • Redis integration: add tags for more commands
  • Redis integration: Patch rediscluster package if installed.
  • Session tracking: A session is no longer considered crashed if there has been a fatal log message (only unhandled exceptions count).
  • Breaking change: Revamping of the tracing API.
  • Breaking change: before_send is no longer called for transactions.

0.15.1

  • Fix fatal crash in Pyramid integration on 404.

0.15.0

  • Breaking change: The ASGI middleware will now raise an exception if contextvars are not available, like it is already the case for other asyncio integrations.
  • Contextvars are now used in more circumstances following a bugfix release of gevent. This will fix a few instances of wrong request data being attached to events while using an asyncio-based web framework.
  • APM: Fix a bug in the SQLAlchemy integration where a span was left open if the database transaction had to be rolled back. This could have led to deeply nested span trees under that db query span.
  • Fix a bug in the Pyramid integration where the transaction name could not be overridden at all.
  • Fix a broken type annotation on capture_exception.
  • Basic support for Django 3.1. More work is required for async middlewares to be instrumented properly for APM.

0.14.4

  • Fix bugs in transport rate limit enforcement for specific data categories. The bug should not have affected anybody because we do not yet emit rate limits for specific event types/data categories.
  • Fix a bug in capture_event where it would crash if given additional kwargs. Thanks to Tatiana Vasilevskaya!
  • Fix a bug where contextvars from the request handler were inaccessible in AIOHTTP error handlers.
  • Fix a bug where the Celery integration would crash if newrelic instrumented Celery as well.

0.14.3

  • Attempt to use a monotonic clock to measure span durations in Performance/APM.
  • Avoid overwriting explicitly set user data in web framework integrations.
  • Allow to pass keyword arguments to capture_event instead of configuring the scope.
  • Feature development for session tracking.

0.14.2

Commits
  • 1737ba8 chore: xfail aws to get going with release
  • fc7afd5 release: 0.16.2
  • c986dca fix: pin dnspython
  • 0d02e26 doc: Changelog for 0.16.2
  • b117955 Add setup.py extra for pure_eval (#763)
  • 2b8d96d Extract additional expression values with pure_eval (#762)
  • 5c34ead Use executing to infer code qualname (#749)
  • 0ee6a25 Use sentry_init fixture in tests instead of using Hub directly (#759)
  • 7898eac Merge release/0.16.1 into master
  • 1c375fc release: 0.16.1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 4 years ago

Superseded by #195.