Merge #1343

1343: Introduce SomeMnemonic as source of root keys (instead of entropy) r=Anviking a=Anviking

Issue Number

#1316, preliminary work to unblock #1321

Overview

• Add SomeMnemonic as return type of fromMnemonic
• Make e.g. unsafeGenerateKeyFromSeed take a SomeMnemonic instead entropy. This is more similar to Icarus.generateKeyFromHardwareLedger
• Add genMnemonic helper in a shared location

Comments

Co-authored-by: Johannes Lund [email protected]

New translations en-US.md (Portuguese, Brazilian)

New translations en-US.md (Portuguese, Brazilian)

Merge #1649

1649: Disable the on-demand start of mini-protocol threads for now r=dcoutts a=dcoutts

Fixes issue #1646.

This is an alternative to #1648. This PR simply disables on-demand start. That PR tries to fix it. However this bit of code is in the middle of being refactored so it is simpler to disable it for now and include the fix in the refactoring.

The problem, we realised, is that which peer initiates the overall mux bearer is actually independent from whether protocol threads should be started on-demand or started eagerly. What it really depends on is which peer has agency in the initial protocol state. For most mini-protocols it is the peer that initiated the bearer that has agency in the initial state, but that is not true for all protocols, and in particular for the TxSubmission protocol in ouroboros-network.

The solution will be to make the on-demand vs eager distinction independent of the initiator vs responder distinction, and have it be specified in the MuxMiniProtocol.

We missed this in the network-mux and ouroboros-network tests because we did not have bundles of mini-protocols with mixed initial agency. This should be corrected.

Co-authored-by: Duncan Coutts [email protected]

New translations en-US.md (Portuguese, Brazilian)

try to fix windows

buildkite pipeline updates

Disable the on-demand start of mini-protocol threads for now

Fixes issue #1646

The problem, we realised, is that which peer initiates the overall mux bearer is actually independent from whether protocol threads should be started on-demand or started eagerly. What it really depends on is which peer has agency in the initial protocol state. For most mini-protocols it is the peer that initiated the bearer that has agency in the initial state, but that is not true for all protocols, and in particular for the TxSubmission protocol in ouroboros-network.

The solution will be to make the on-demand vs eager distinction independent of the initiator vs responder distinction, and have it be specified in the MuxMiniProtocol.

We missed this in the network-mux and ouroboros-network tests because we did not have bundles of mini-protocols with mixed initial agency. This should be corrected.

Disable the on-demand start of mini-protocol threads for now

Fixes issue #1646

The problem, we realised, is that which peer initiates the overall mux bearer is actually independent from whether protocol threads should be started on-demand or started eagerly. What it really depends on is which peer has agency in the initial protocol state. For most mini-protocols it is the peer that initiated the bearer that has agency in the initial state, but that is not true for all protocols, and in particular for the TxSubmission protocol in ouroboros-network.

The solution will be to make the on-demand vs eager distinction independent of the initiator vs responder distinction, and have it be specified in the MuxMiniProtocol.

We missed this in the network-mux and ouroboros-network tests because we did not have bundles of mini-protocols with mixed initial agency. This should be corrected.

Correct peer information in bootstrap logs

Remove Topology::list_available_limit

The functionality is implemented by the view method, and the size limit that was used is larger than what view gives out.

Fall back to self as the bootstrap peer

If the other peers are not available, give the address of this node as the bootstrap peer.

benchmarks

add latest version

CSC0

Merge pull request #3 from grahamc/patch-1

keypair: don’t use ec2_utils

Merge pull request #4 from grahamc/patch-2

keypair: upgrade keys from rsa (whew) to ed25510

Merge pull request #15 from input-output-hk/cpr-support

Cpr support

Merge pull request #13 from grahamc/nix2py-if-provsystem-none

Don’t nix2py provSystem if it is None

Add to nixpkgs map (#447)

• pkgconf-nixpkgs-map: Add nix dependencies

• system-nixpkgs-map: Add boost

Update Hackage and Stackage

Automatic update for Sat Feb 15 02:32:19 UTC 2020

Bump yarn from 1.21.1 to 1.22.0 in /examples/wallet

Bumps yarn from 1.21.1 to 1.22.0.

• Release notes
• Changelog
• Commits

Signed-off-by: dependabot[bot] [email protected]

use iohk-nix and haskell.nix as overlays

use iohk-nix and haskell.nix as overlays

[DDW-1145] Fixes Undelegation issues

fixup! Stylish Haskell.

[DDW-[DDW-1145] Fixes Undelegation issues]

[DDW-[DDW-1145] Fixes Undelegation issues]

wip

Use peers retrieved during bootstrap

Merge pull request #773 from Emurgo/fix-debug-wallet-warning

potential fix to warning for debug wallets in ios

Fix Flow issues

Fix console error

wip

Fix eslint warnings

potential fix to warning for debug wallets in ios

packet-python: use v1.42.0 after upstream merged my PRs

Improve wallet delegation data parsing

Merge branch ‘feature/ddw-1145-pending-delegation-preferences’ of github.com:input-output-hk/daedalus into feature/ddw-1145-pending-delegation-preferences

Logic fix

fix ouroboros-network tests

demo-connections random delay

Permit responders to be started eagerly.

Stylish Haskell.

wip

Merge branch ‘gh-pages-deploy’ into gh-pages

6d1beb5d1b25f9f00e31df2dee6f0310d11dd26d

Merge branch ‘master’ into avieth/p2p-integration

Merge #1499

1499: Snockets r=coot a=coot

This PR introduce snockets which abstract the interface for Berkeley sockets and named pipes (windows).

The PR consist of smaller reviewable and mostly buildable patches.

Highlight of changes:

Win32-network

A bug fixed in System.Win32.Async.connect

network-mux

• runMuxWithPipes handles named pipes as well
• new tests which include posix pipes, named pipes and queues
• mux-demo - windows named pipe demo using mux: an echo server and client

ouroboros-network

• IOManager - system indepdendent IO manager. On Windows using System.Win32.Async.withIOManager, on posix it’s a no-op
• Snockets - abstraction which handles both Berkeley sockets and Windows named pipes, together with smart constructors for both.
• Snocket shim layer with type alliases for different paltforms (posix / win32)
• demo-chain-sync - can now run on Windows with named pipes

future work

• NodeToClient and NodeToNode which are using named pipes for local clients on windows.

Co-authored-by: Marcin Szamotulski [email protected]