Skip to content

Fix typo. - #717

Merged
untitaker merged 2 commits into
getsentry:masterfrom
lmasikl:patch-1
Jun 9, 2020
Merged

untitaker merged 2 commits into
getsentry:masterfrom
lmasikl:patch-1

Conversation

@lmasikl

@lmasikl lmasikl commented Jun 9, 2020

Copy link
Copy Markdown
Contributor

No description provided.

@untitaker untitaker left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, can you run make format locally and commit the result?

@lmasikl

lmasikl commented Jun 9, 2020

Copy link
Copy Markdown
Contributor Author

@untitaker I didn't any changes in that string https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/integrations/aiohttp.py#L54, because I don't is it reasonable. I catched this exception because aiohttp has not parseable version https://github.com/aio-libs/aiohttp/releases/tag/v4.0.0a1.
But string like this can fix this exception in root
version = tuple(map(int, AIOHTTP_VERSION.split(".")[:2]))

@untitaker

untitaker commented Jun 9, 2020 •

Copy link
Copy Markdown
Member

@lmasikl I agree, can you put this change into your PR?

I am surprised that people actually use alpha versions, but so be it.

@untitaker
untitaker merged commit 1f6743c into getsentry:master Jun 9, 2020
@untitaker

Copy link
Copy Markdown
Member

Thanks, works for me!

pabloDeputter added a commit that referenced this pull request Oct 15, 2026
### Description
boto3 spans now use `sentry.op = rpc` instead of `http.client`. Service
extensions can (and will in the future) provide a more specific op with
`get_span_op()`, e.g. `db` for DynamoDB.

### Why
- boto3 span represents an AWS api call, not an HTTP request; the HTTP
request is already captured as the as the `http.client` child
- JS already also defaults AWS SDK spans to `rpc`

It also lets these spans use new name and description rules in
sentry-conventions, e.g. (getsentry/sentry-conventions#714, #717), e.g.
`Lambda.Invoke billing` instead of `POST https://lambda.…`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants