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.

The upstream issues got closed. It is referenced in:

• driver/config/config_test.go#L942

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

The puppet-chain binary doesn't seem to be used anymore -- clarinet integrate and devnet do not use it for setting up a local regtest environment, and our integration tests do not use it either.

It could still be useful for developers trying to spin up their own bitcoin regtest environment. However, I feel pretty ambivalent about supporting that use case through the puppet-chain: we don't reall

Currently:

» ockam tcp-listener create --help

ockam-tcp-listener-create 0.68.0
Create tcp listener on the selected node

USAGE:
    ockam tcp-listener create [OPTIONS] <BIND>

ARGS:
    <BIND>

OPTIONS:
    -h, --help           Print help information
    -n, --node <node>    Override the default API node [default: default]
    -q, --quiet          Do not print trace messag

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

Which version of MSAL.NET are you using?
Latest

Problem
Serialize and [Deserialize](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/blob/a2e46b12008f5244e4c4d5e21ff303292

A user should be able to use ⌘+A, ctrl+A to copy and paste commands instead of selecting other components.

Current behavior if you use keyboard shortcut:

Expected behavior:

<img width="477" alt="image" src="https://user-images.githubusercontent.com/3

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