Arpad Borsos

> I am using it via `ts-node -r tsconfig-paths/register`. > It is not clear to me if it's possible via the CLI or I must now programmatically call it in...

Hm, I just tested this on our codebase, and with the following `./tools/register.js`, I see a reduction from ~2s to ~500ms with the latest update using the script ```js require('source-map-support').install()...

As you linked to basically two problems in the wider Rust ecosystem (also note that backtrace-rs is part of the rust stdlib), and I can’t really speak to those. Otherwise...

> Is this Sentry-Rust used in Android and iOS environments before? Not that I know of.

Sharing scope data between different language SDKs is always a challenge. So far, most of our Mobile focused SDKs that bundle sentry-native have implemented Scope-sync. Though nothing on the Rust...

I think this basically comes down to PR #97 which is also stalled, so I’m afraid there is no good solution for this ATM.

Note that goroutines are fundamentally different from OS level threads. What you could always do is to just use the `Hub` explicitly and pass that down to whereever you need....

> Making the scope fields public would allow reading the scope directly I wouldn’t make the fields public. Due to the real/noop scope optimization, that is impossible to begin with...

I think both have pros/cons. The reporter process looks good, but the problem stands that you only do a single `configure_scope`, so you only have updates for one of the...

if this might be related to some kind of network config, what openssl version do these systems have? and can you reproduce the deadlock when compiling with another tls provider?