…nce (#1694)

We noticed that generating the sample format at the end of a profile can get
rather slow and this aims to improve what we can here with minimal changes. A
few things we took advantage of to accomplish this:

- Turning the extracted stack into a tuple so it is hashable so it can be used
  as a dictionary key. This let's us check if the stack is indexed first, and
  skip indexing the frames again. This is especially effective in profiles where
  it's blocking on a network request for example, since there will be many
  identical stacks.
- Using the hash of the stack as the dictionary key. Hashing the entire stack
  can be an expensive operation since a stack can have up to 128 frames. Using
  it as a dictionary key means it needs to be rehashed each time. To avoid this,
  we pre-hash the stack and use the hash as a dictionary key which is more
  efficient.
- Convert numbers to strings ahead of time if we know have to. Values like the
  tid and elapsed since start ns needs to be sent as a string. However, many
  samples share the same value for it, and we're doing the conversion each time.
  Instead, we convert them to a string upfront and reuse it as needed in order
  to minimize unnecessary calculations.

…1703)

Bumps [checkouts/data-schemas](https://github.com/getsentry/sentry-data-schemas) from `a214fbc` to `20ff3b9`.
- [Release notes](https://github.com/getsentry/sentry-data-schemas/releases)
- [Commits](getsentry/sentry-data-schemas@a214fbc...20ff3b9)

---
updated-dependencies:
- dependency-name: checkouts/data-schemas
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

#1711)

The truncation and indexes in the AnnotatedValues it's done by number of bytes
and not number of characters.

Fixes GH-1691

* Move relay to port 5333 to avoid collisions
* Ignoring type checking for .last_token because it is present in EnhancedAST...

Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

* feat(pymongo): add PyMongo integration

Adds breadcrumbs and performance traces for PyMongo queries using an
official monitoring API. Integration is similar to the one available in
OpenTelemetry, tags set to values recommended for attributes by OT as
specified in `Span Operations` guidelines.

Personal identifiable information (PII) will be stripped from all PyMongo commands. (This was tested in the PyMongo versions below, but "should" also be future proof)

PyMongo version selection explanation:
* 3.1 - introduction of monitoring API. Only Python 2.7 and 3.6
supported.
* 3.12 - latest 3.x release, support for 2.7, 3.6-3.9 (3.7-3.9 added in
various minor releases between 3.1 and 3.12).
* 4.0 - no support for 2.7, added support for 3.10.
* 4.1 - no support for 3.6.0-3.6.1.
* 4.2 - no support for any 3.6.

Co-authored-by: Szymon Soloch <ssoloch@opera.com>
Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

* Made function faster

Update actions/upload-artifact to v3.1.1

Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

This extracts a little more information around the frame that we'll use to improve the visualization/groupings including
- in_app
- module

The sleep scheduler is the most reliable of the available schedulers, make it
the default.

We currently error if profiling is already setup which can be error prone
depending on the end user's setup. This change ensures that we only setup
profiling once and once setup, it's reused.

Starlette/FastAPI is internally caching the request body if read via request.json() or request.body() but NOT when using request.form(). This leads to a problem when our Sentry Starlette integration wants to read the body data and also the users code wants to read the same data.

Solution:
Force caching of request body for .form() calls too, to prevent error when body is read twice.

The tests where mocking .stream() and thus hiding this problem. So the tests have been refactored to mock the underlying ._receive() function instead.

Co-authored-by: hasier <hasier@users.noreply.github.com>

When using the newest version of the Python SDK on the sentry backend we get the following error:

name = "partial(<function " + receiver.func.__name__ + ">)"  # type: ignore
AttributeError: __name__

This change gets the __name__ attribute in a very defensive way, to not raise any errors what so ever.