Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

catchpoint: use read connection for data retrieval for spver hash calculation #5592

Merged
merged 1 commit into from
Jul 21, 2023

Conversation

cce
Copy link
Contributor

@cce cce commented Jul 21, 2023

Summary

#5579 was merged a few minutes before I had a chance to push this commit to address @AlgoAxel's PR feedback in #5579 (comment) about using read vs write scopes for getting the SP verification context. This is that change

Test Plan

Existing tests should pass.

@codecov
Copy link

codecov bot commented Jul 21, 2023

Codecov Report

Merging #5592 (c106a05) into master (0e0b26d) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5592      +/-   ##
==========================================
- Coverage   55.82%   55.75%   -0.07%     
==========================================
  Files         446      446              
  Lines       63482    63482              
==========================================
- Hits        35437    35395      -42     
- Misses      25675    25712      +37     
- Partials     2370     2375       +5     
Impacted Files Coverage Δ
ledger/catchpointtracker.go 59.58% <100.00%> (-0.12%) ⬇️

... and 12 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@algorandskiy algorandskiy changed the title catchpoint: address feedback from #5579 catchpoint: use read connection for data retrieval for spver hash calculation Jul 21, 2023
@algorandskiy algorandskiy merged commit 0c6a328 into algorand:master Jul 21, 2023
19 of 20 checks passed
@cce cce deleted the checkpoint-hash-fix-5579 branch August 4, 2023 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants