Skip to content

chore: capture sentry backtraces#2166

Open
pjenvey wants to merge 1 commit intomasterfrom
chore/sentry-capture-STOR-493
Open

chore: capture sentry backtraces#2166
pjenvey wants to merge 1 commit intomasterfrom
chore/sentry-capture-STOR-493

Conversation

@pjenvey
Copy link
Member

@pjenvey pjenvey commented Mar 27, 2026

Description

(we were missing the "capture" feature)

and switch back to sentry's now longstanding default transport of reqwest+rustls, which avoids issues w/ our grpc client's included boringssl that occurred w/ reqwest+native-tls

Issue(s)

Closes STOR-493

(we were missing the "capture" feature)

and switch back to sentry's now longstanding default transport of
reqwest+rustls, which avoids issues w/ our grpc client's included boringssl
that occurred w/ reqwest+native-tls

Closes STOR-493
@pjenvey pjenvey requested review from chenba and taddes March 27, 2026 00:23
Copy link
Collaborator

@taddes taddes left a comment

Choose a reason for hiding this comment

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

lgtm, though I'll have to get brief context on this from you sometime. grpcio ftw. Is this basically where reqwest and grpcio's boringssl fight over TLS internals, so libcurl was used as a side-step since it has its own independent TLS stack that didn't clash?

// likely grpcio's boringssl
let curl_transport_factory = |options: &sentry::ClientOptions| {
Arc::new(sentry::transports::CurlHttpTransport::new(options)) as Arc<dyn sentry::Transport>
};
Copy link
Collaborator

Choose a reason for hiding this comment

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

What changed so we no longer need this? Sorry I don't have the context.

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.

3 participants