Load time point from `expected`, but if it's infinite, return a large timeout instead (otherwise overflow can occur in libstdc++, which results in no

You'll need this to derive your own client-side span. `opentelemetry::trace::SpanContext` is a value type. An invalid context (`SpanContext::GetInval

Get stack size.

Get trivial FLS by its index. Trivial FLSes are always zero-initialized.

Copied from `common/base/binary_version.cc`.

Shamelessly copied from https://stackoverflow.com/a/57556517

`membarrier()` is not usable until Linux 4.3, which is not available until tlinux 3 is deployed. Here Folly provides a workaround by mutating our pag

Initialization of timer is delayed until first call to `Report()` to avoid static initialization order fiasco.

Initialize those global variables.

Insert a new correlation. Were duplicate found, we crash. (TODO(luobogao): Maybe we can fail more gracefully.)

Returns: scheme, address.

Per spec, `charset` is allowed for `application/json`. This method tests if the given type string represents `application/json` with UTF-8 `charset`.

Tests if `port` is unsafe to be used as a serving port.

Slow but works.

Allocate new ID for connection. Each connection has a dedicated ID. This is necessary to distinguish ID duplicates on different connections.

'.' / '..' is not handled by this method. They're valid node name in `ExposedVarGroup`.

Handle the difference between URI scheme difference between our old framework and Flare. This method is only used by `RpcChannel`, so we can assume P