From 56d4f8b9ee4e9aae3c04bdb32e41ba877e4c4f5e Mon Sep 17 00:00:00 2001 From: "fuder.eth" <139509124+vtjl10@users.noreply.github.com> Date: Sun, 15 Dec 2024 13:08:57 +0100 Subject: [PATCH 1/2] Update test_dsl_spec.md --- docs/test_dsl_spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/test_dsl_spec.md b/docs/test_dsl_spec.md index aec6865e730..8e926d926c4 100644 --- a/docs/test_dsl_spec.md +++ b/docs/test_dsl_spec.md @@ -192,7 +192,7 @@ DSL.List.iter (left_partition @ right_partition) ~f:destroy ALTERNATIVE TEST: keep two partitions separate with a fixed topology, with 1-2 intermediate nodes bridging the networks, then take the other bridge offline temporarily and then have them -rejoin the network without topologoical restrictions and see if the chains reconverge +rejoin the network without topological restrictions and see if the chains reconverge ##### Basic Hard Fork Test From 97bbbfee424969ca94abf0ae4942fb1a91493bf0 Mon Sep 17 00:00:00 2001 From: "fuder.eth" <139509124+vtjl10@users.noreply.github.com> Date: Sun, 15 Dec 2024 13:09:45 +0100 Subject: [PATCH 2/2] Update README.md --- src/lib/mina_networking/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib/mina_networking/README.md b/src/lib/mina_networking/README.md index 33c3c00951d..42be4901a60 100644 --- a/src/lib/mina_networking/README.md +++ b/src/lib/mina_networking/README.md @@ -2,7 +2,7 @@ ## Typing Conventions -In the context of this document, we will describe query and response types using a psuedo type-system. Tuples of data are in the form `(a, ..., b)`, lists are in the form `[a]`, and polymorphic types are represented as functions returning types. For example, we use the standard polymorphic types `optional :: type -> type` and `result :: type -> type -> type` throughout this document. The `optional` type constructor means that a value can be null, and a `result` type constructor means that there is 1 of 2 possible return types (typically a success type and an error type). For example, `optional int` might be an int or null, where as `result int error` is either an int or an error. +In the context of this document, we will describe query and response types using a pseudo type-system. Tuples of data are in the form `(a, ..., b)`, lists are in the form `[a]`, and polymorphic types are represented as functions returning types. For example, we use the standard polymorphic types `optional :: type -> type` and `result :: type -> type -> type` throughout this document. The `optional` type constructor means that a value can be null, and a `result` type constructor means that there is 1 of 2 possible return types (typically a success type and an error type). For example, `optional int` might be an int or null, where as `result int error` is either an int or an error. ### Relevant types @@ -136,4 +136,4 @@ Returns the best tip block along with the root block of the frontier, and a merk **Response**: `result node_status error` -This acts as a telemetry RPC which asks a peer to provide invformation about their node status. Daemons do not have to respond to this request, and node operators may pass a command line flag to opt-out of responding to these node status requests. +This acts as a telemetry RPC which asks a peer to provide information about their node status. Daemons do not have to respond to this request, and node operators may pass a command line flag to opt-out of responding to these node status requests.