ci: add discord notify job to sync workflow by Copilot · Pull Request #43 · dappnode/DAppNodePackage-besu-generic

Copilot · 2026-02-06T15:12:28Z

Adds Discord notifications to the sync workflow, mirroring the implementation from the Geth generic repository.

Changes

Added notify job to .github/workflows/sync.yml that:
- Depends on sync job completion
- Executes on all outcomes except skipped
- Calls reusable Discord notification workflow
- Passes sync result and test type

  notify:
    needs: sync
    if: always() && needs.sync.result != 'skipped'
    uses: dappnode/staker-test-util/.github/workflows/notify-discord.yml@main
    with:
      result: ${{ needs.sync.result }}
      test_type: "sync"
    secrets: inherit

Original prompt

Context

A change was already implemented in the Geth generic repo that adds a Discord notification job to the sync workflow:
dappnode/DAppNodePackage-geth-generic@7552d5b

This same change needs to be applied to this repository.

Task

Add a new notify job at the END of the .github/workflows/sync.yml file.

The job to add is:
  notify:
    needs: sync
    if: always() && needs.sync.result != 'skipped'
    uses: dappnode/staker-test-util/.github/workflows/notify-discord.yml@main
    with:
      result: ${{ needs.sync.result }}
      test_type: "sync"
    secrets: inherit
Requirements

Open the file .github/workflows/sync.yml

Add the notify job at the END of the workflow file (after all existing jobs)

Do NOT modify any other jobs

Do NOT refactor workflow formatting

Do NOT reorder existing jobs

The notify job must depend on sync

Ensure indentation remains valid YAML

Branch and Commit

Create branch: add-sync-notify-job

Commit message: ci: add discord notify job to sync workflow

Open PR to main

Do NOT merge the PR

This pull request was created from Copilot chat.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: Marketen <36164126+Marketen@users.noreply.github.com>

github-actions · 2026-02-06T15:37:07Z

✅ SYNC TEST REPORT - PASSED

This CI runs on a real DAppNode using the same RPC calls a user would make to configure a staker setup: execution client, consensus client, web3signer, MEV-boost, and relays. The self-hosted runner is pre-loaded with synced (or near-synced) execution client volumes, enabling fast sync and attestation tests with any client combination. Consensus clients use checkpoint sync, so no pre-synced volume is required.

Sync Test: Verifies that both execution and consensus clients reach a synced state. This test ensures the staker configuration is valid and clients can synchronize with the network.

📦 Clients Used

Component	DNP Name	DNP Version
Execution	`hoodi-besu.dnp.dappnode.eth`	`0.1.4`
Consensus	`teku-hoodi.dnp.dappnode.eth`	`0.1.3`
Web3Signer	`web3signer-hoodi.dnp.dappnode.eth`	`0.1.3`
MEV Boost	`mev-boost-hoodi.dnp.dappnode.eth`	`0.1.1`
Network	`hoodi`

🔖 Version Tracking

Execution Client Versions

Stage	Version
Before Install	`besu/v25.9.0/linux-x86_64/openjdk-java-21`
After Install	`besu/v25.11.0/linux-x86_64/openjdk-java-21`

Consensus Client Versions

Stage	Version
Before Install	`teku/v25.9.3/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-21`
After Install	`teku/v25.9.3/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-21`

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	1m12.048s	✅
PackageInstall	39.782s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	4m24.183s	✅
WaitForExecutionSync	2ms	✅

Total Duration: 6m35s

🔴 Container Error Logs

⚠️ Showing up to 3 error lines per container. See CI logs for complete details.

DAppNodePackage-brain.web3signer-hoodi.dnp.dappnode.eth:

2026-02-06T15:32:42.673718039Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...
2026-02-06T15:33:42.571855689Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...
2026-02-06T15:34:42.568193699Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...

DAppNodePackage-validator.teku-hoodi.dnp.dappnode.eth:

2026-02-06T15:32:54.705469190Z 2026-02-06 15:32:54.705 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73380, status = 503, message = Beacon node is currently syncing and not serving requests)
2026-02-06T15:32:54.709844267Z 2026-02-06 15:32:54.709 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73381, status = 503, message = Beacon node is currently syncing and not serving requests)
2026-02-06T15:33:06.717007690Z 2026-02-06 15:33:06.716 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73381, status = 503, message = Beacon node is currently syncing and not serving requests)

DAppNodePackage-besu.hoodi-besu.dnp.dappnode.eth:

2026-02-06T15:33:09.465407002Z 2026-02-06 15:33:09.465+0000 | nioEventLoopGroup-3-2 | ERROR | AbstractBlockProcessor | failed persisting block due to stateroot mismatch; expected 0xbe6f76ed322220e4a500ffa56266b2d62cfcaa94a31522ab5454448df293f9b5, actual 0xa95f442e3f19162cdc5a213d22c63257da730a22c0234cfc9e5f8b133a325204
2026-02-06T15:33:09.465807230Z 2026-02-06 15:33:09.465+0000 | nioEventLoopGroup-3-2 | INFO  | MainnetParallelBlockProcessor | Parallel transaction processing failure. Falling back to non-parallel processing for block #2178999 (0x96cc60f083bb4cb29813b6dabe3eb3de6d29d92918341d5ff4f87d15a9959740)
2026-02-06T15:36:00.567997437Z 2026-02-06 15:36:00.566+0000 | vert.x-eventloop-thread-1 | ERROR | VertxPeerDiscoveryAgent | Encountered error while handling packet

📋 View full CI logs

Initial plan

d463fae

Copilot AI assigned Copilot and Marketen Feb 6, 2026

Copilot started work on behalf of Marketen February 6, 2026 15:12 View session

ci: add discord notify job to sync workflow

608297c

Co-authored-by: Marketen <36164126+Marketen@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add notify job to sync workflow~~ ci: add discord notify job to sync workflow Feb 6, 2026

Copilot finished work on behalf of Marketen February 6, 2026 15:15

Copilot AI requested a review from Marketen February 6, 2026 15:15

pablomendezroyo approved these changes Feb 6, 2026

View reviewed changes

pablomendezroyo marked this pull request as ready for review February 6, 2026 15:24

pablomendezroyo merged commit 406168f into main Feb 6, 2026
1 check passed

pablomendezroyo deleted the copilot/add-notify-job-to-workflow branch February 6, 2026 15:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ci: add discord notify job to sync workflow#43

ci: add discord notify job to sync workflow#43
pablomendezroyo merged 2 commits intomainfrom
copilot/add-notify-job-to-workflow

Copilot AI commented Feb 6, 2026 •

edited

Loading

Uh oh!

Uh oh!

github-actions bot commented Feb 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

Copilot AI commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Context

Task

Requirements

Branch and Commit

Uh oh!

Uh oh!

github-actions bot commented Feb 6, 2026

✅ SYNC TEST REPORT - PASSED

📦 Clients Used

🔖 Version Tracking

⏱️ Timing Measurements

Environment Setup

Test Execution

🔴 Container Error Logs

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Feb 6, 2026 •

edited

Loading