Is your feature request related to a problem? Please describe.

May we make the Jaeger configuration maxTagValueLength be configureable for ory/x/tracing tracer.go ?
The default length 256 isn't enough for we observe the query.

Describe the solution you'd like

Configuration in yaml like

tracing:
  service_name: or

Describe the bug

I registered an account but did not verify the email address. I received an verification email every time I change my password. This seems unexpected.
Is this intentional? Is there a way to stop this?

Reproducing the bug

Steps to reproduce the behavior:

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

As of bitcoin 0.21.0, a default wallet is no longer automatically created (bitcoin/bitcoin#15454).

This change causes the tests in neon_integrations.rs to fail with the following message:

ERRO [1617206434.490494] [testnet/stacks-node/src/burnchains/bitcoin_regtest_controller.rs:589] [ThreadId(13)] Bitcoin RPC failure: error listing utxos Network("Bitcoin RPC: stat

cc @jcnelson from this forum post.

There should be a setting added that allows the user to adjust the URL for the transaction broadcaster in regards to acquiring names. Should be fairly simple to implement unless it is tied within blockstack.js, in which case an issue would need to

See the original issue: microsoft/Git-Credential-Manager-Core#286

Logs and Network traces

Which Version of MSAL are you using ?
4.3.0

Platform
netcoreapp3.1

What authentication flow has the issue?

• Desktop / Mobile
  • Interactive - system browser

Is this a new or existing app?
b. The app is in production, I haven't upgraded

We should add telemetry calls to the following areas:

• outgoing tcp start and end connection
• TCP.Listener.Handler start (because a connection was established)
• TCP.Listener.Handler :tcp_closed, data received, exception raised
• UDP.Listener send, receive, decode success, decode failure

Describe the bug
Currently all side effects or catchError functions use this.router.navigate() function to redirect to one of the predefined routes
This works great but fails when users enter URL with query params.
(i.e http://example.com?foo=5&bar=10)

This actually is a known bug in Angular Router
(see angular/angular#28917)

The workaround would be to

Describe the issue:
The links not show hover states on hover on the getting started page.

How to reproduce:

1. Navigate to getting started page
2. hover over any link

Expected behavior:
Should indicate hover state for links