The upstream pull got closed. It is referenced in:

• driver/registry_base.go#L246

This issue was created by the ORY Closed Reference Notifier GitHub action.

The upstream pull got closed. It is referenced in:

• go.mod#L22

This issue was created by the ORY Closed Reference Notifier GitHub action.

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.

Describe the bug
Currently if stacks-node has a problem parsing properties in a given config toml file, it will immediately abort due to a panic and dump a stacktrace. The error doesn't direct the user that the problem exists in the config file, nor does the stack trace. This can lead to confusion and generally make the user experience more difficult when trying to understand the problem.

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 #2583 for details

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

We experienced anomalous behavior with our localStorage['redirect'] value being "randomly" cleared out. Further investigation found the culprit was the angular-auth-oidc-client code:

auto-login-service.js

const STORAGE_KEY = 'redirect';

I'm not familiar with the code base. My initial scan only found this usage. But it might be a good idea to use something like a library wi

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