identity

The upstream issues got closed. It is referenced in:

• client/manager_test_helpers.go#L235

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

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my [Ory Cl

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

Similar to how Bitcoin has a prune=1 option that removes old blocks, Stacks should have this too to save storage space on nodes.

Describe the solution you'd like

An option in the config to prune chaindata via RPC or limiting it to a certain number of MiB

Describe alternatives you've considered

None

In implementations/rust/ockam/ockam_transport_ble/src/driver/packet.rs:104:

// TODO Currently we only support packet lengths up to 2^16
// bits long.
//
// The reason for this is that I'm too lazy right now to setup
// a control channel for this BLE UART implementation and
// instead rely on the probability of receiving an 8 byte long
// packet consisting of 6 zero bytes followed b

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

Version: MSAL.NET @ 4.42
Platform: Windows 11, net5.0-windows10.0.17763.0
Auth flow: Broker and Interactive Web auth (embedded web view only)

Repro
@bgavrilMS - we have an easy repro internally and a current bugfix in the auth CLI.

private class MsalHttpClientFactoryAdaptor : IMsalHttpClientFactory
        {
            private HttpClient instance;

            public

Describe the bug
If the environment (in my case the stage environment) is not setup as a a secure origin the library break up cause of the crypto library is not in window object

To Reproduce
Steps to reproduce the behavior:

1. A server work on http that is setup as 'insecure origin'
2. Start the login sequence

Expected behavior
Warning on library loading that check secure or

infra users edit incorrectly mentions that --password sets the users' one time password, when it sets their permanent password.

# Set a user's password
$ infra users edit janedoe@example.com --password

Flags:
      --password   Set password

Related:

• #2145

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