Skip to content

Conversation

@KaloyanTanev
Copy link
Collaborator

Prep for v1.6.1 release.

category: misc
ticket: none

KaloyanTanev and others added 2 commits September 12, 2025 17:21
When we fetch attestation data with the fetcher, we are doing this in a loop, which takes variable amount of time, based on the beacon node's performance. If the beacon node is underperforming it might be that in the middle of this loop it receives a new block. This will result some attestation datas having the up to date head, while others have an old head.

In a good scenario of well performing beacon node, the heads will be the same and the `value` and `attData.Data` will be equal. However, in the scenario explained above, their head will missmatch, resulting in inequality.

That's why we are checking here only if source and target missmatch.

category: bug
ticket: none
@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Sep 12, 2025

Codecov Report

❌ Patch coverage is 31.81818% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 55.03%. Comparing base (5f953a6) to head (479cb20).
⚠️ Report is 1 commits behind head on main-v1.6.

Files with missing lines Patch % Lines
core/dutydb/memory.go 31.81% 13 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           main-v1.6    #3975   +/-   ##
==========================================
  Coverage      55.02%   55.03%           
==========================================
  Files            225      225           
  Lines          36857    36877   +20     
==========================================
+ Hits           20282    20295   +13     
- Misses         14430    14441   +11     
+ Partials        2145     2141    -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@KaloyanTanev KaloyanTanev added the merge when ready Indicates bulldozer bot may merge when all checks pass label Sep 12, 2025
@obol-bulldozer obol-bulldozer bot merged commit 82e31db into main-v1.6 Sep 12, 2025
12 checks passed
@obol-bulldozer obol-bulldozer bot deleted the kalo/v1.6.1 branch September 12, 2025 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch-release merge when ready Indicates bulldozer bot may merge when all checks pass

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants