From 7c5e6a77be7dab1fba0edb55dcb30b195d36e727 Mon Sep 17 00:00:00 2001 From: Nic Volanschi Date: Thu, 28 Nov 2024 10:06:03 +0100 Subject: [PATCH 1/3] doc: update and extend copyright --- docs/conf.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/conf.py b/docs/conf.py index 2a16993c35d0..89afd3945a46 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -61,8 +61,8 @@ master_doc = 'index' # General information about the project. project = 'Tezos' -copyright = '2018-2023, Nomadic Labs ' -author = 'Nomadic Labs ' +copyright = '2018-2024' +author = 'Contributors to the Octez & Tezos protocol documentation' # The version info for the project you're documenting, acts as replacement for # |version| and |release|, also used in various other places throughout the -- GitLab From 7b801649e9f8de6651c623026d0329cae8ecd1e0 Mon Sep 17 00:00:00 2001 From: Nic Volanschi Date: Thu, 28 Nov 2024 11:34:28 +0100 Subject: [PATCH 2/3] doc: fix checking rights in dal_run.rst --- docs/shell/dal_run.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/shell/dal_run.rst b/docs/shell/dal_run.rst index c462c9b94bfd..f79053e29520 100644 --- a/docs/shell/dal_run.rst +++ b/docs/shell/dal_run.rst @@ -81,13 +81,15 @@ Follow these steps to run a DAL node along with a layer 1 node and a baker. The baker daemon connects to the DAL node and attests to the availability of DAL data as well as its usual layer 1 baking function. -#. In a new terminal window, verify that your baking daemon has attestation rights allocated, by running this command: +#. In a new terminal window, verify that your baking daemon has attestation rights allocated for the current cycle, by running: .. code-block:: shell - octez-client rpc get "/chains/main/blocks/head/helpers/attestation_rights?delegate=$MY_ADDRESS" + octez-client rpc get "/chains/main/blocks/head" | jq '.metadata.level_info.cycle' + octez-client rpc get "/chains/main/blocks/head/helpers/attestation_rights?delegate=$MY_ADDRESS&cycle=" - If the previous command reports no attestation rights (``[]``), first check that you do have attestation rights during the current cycle (by adding the ``"&cycle="`` argument). If that is not the case, you may have to register as a delegate or re-activate your delegate and wait for a few cycles to get some rights (see :ref:`DelegateRegistration`). + Be aware that the last command may take several minutes to execute if it returns a long list of rights. + In turn, if the previous command reports no attestation rights (``[]``), you may have to register as a delegate or re-activate your delegate and wait for a few cycles to get some rights (see :ref:`DelegateRegistration`). #. Verify that the DAL node is running properly: -- GitLab From 6b0f643602f0f8a362660b3f65be6bbd8fc3e7f8 Mon Sep 17 00:00:00 2001 From: Julien Sagot Date: Thu, 28 Nov 2024 13:01:04 +0100 Subject: [PATCH 3/3] doc: fix wrong exit code --- docs/user/exits.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/user/exits.rst b/docs/user/exits.rst index e02f964c77cf..f5cd2fa5c8e1 100644 --- a/docs/user/exits.rst +++ b/docs/user/exits.rst @@ -35,8 +35,8 @@ Signals ------- Upon receiving ``SIGINT`` (e.g., via Ctrl+C in an interactive session) or -``SIGTERM`` (e.g., via ``systemctl stop``) the process will exit (with code 64 or -255, see details below). Note that sending the same signal a second time (after +``SIGTERM`` (e.g., via ``systemctl stop``) the process will exit with code 127 if the cleanup happens normally. However, +sending the same signal a second time (after a one (1) second grace period) will terminate the process immediately, -interrupting the normal clean-up functions of clean-up (in this case the exit -code will be 255). +interrupting the normal clean-up functions, and in this case the exit +code will be 255. -- GitLab