From 3e6b0bd0a36dfa434a779812b648d15c9e67025f Mon Sep 17 00:00:00 2001 From: Daniel Knopik <107140945+dknopik@users.noreply.github.com> Date: Mon, 7 Jul 2025 12:46:18 +0200 Subject: [PATCH] Make `notifier_service::notify` pub (#7708) Anchor wants the `notify` function to run only in certain cases - so the `spawn_notifier` function is unsuitable for us. Anchor uses it's own `notify` function, which then calls `notifier_service::notify` (in most circumstances). To enable that, `notify` needs to be `pub`. --- validator_client/validator_services/src/notifier_service.rs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/validator_client/validator_services/src/notifier_service.rs b/validator_client/validator_services/src/notifier_service.rs index 6b8ea04edb..55a583774e 100644 --- a/validator_client/validator_services/src/notifier_service.rs +++ b/validator_client/validator_services/src/notifier_service.rs @@ -35,7 +35,9 @@ pub fn spawn_notifier( } /// Performs a single notification routine. -async fn notify(duties_service: &DutiesService) { +pub async fn notify( + duties_service: &DutiesService, +) { let (candidate_info, num_available, num_synced) = duties_service.beacon_nodes.get_notifier_info().await; let num_total = candidate_info.len();