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

Fixes required for mint and burn fuzzing #1743

Merged
merged 3 commits into from
Jan 24, 2025

Conversation

jalextowle
Copy link
Contributor

This PR contains some fixes required to get the mint and burn functions fuzzed

@jalextowle jalextowle enabled auto-merge (squash) January 24, 2025 23:34
@jalextowle jalextowle merged commit 0826d52 into main Jan 24, 2025
3 checks passed
@jalextowle jalextowle deleted the jalextowle/fuzz/mint-and-burn branch January 24, 2025 23:55
Copy link

codecov bot commented Jan 24, 2025

Codecov Report

Attention: Patch coverage is 17.64706% with 14 lines in your changes missing coverage. Please review.

Project coverage is 80.40%. Comparing base (f3bc4c7) to head (b06f905).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/agent0/chainsync/db/hyperdrive/convert_data.py 17.64% 14 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1743      +/-   ##
==========================================
- Coverage   80.90%   80.40%   -0.51%     
==========================================
  Files          96       96              
  Lines        7113     7128      +15     
==========================================
- Hits         5755     5731      -24     
- Misses       1358     1397      +39     
Flag Coverage Δ
unittests 80.40% <17.64%> (-0.51%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants