Skip to content

Conversation

@rodrodros
Copy link
Collaborator

Fixing linting errors

@codecov
Copy link

codecov bot commented Jan 9, 2026

Codecov Report

❌ Patch coverage is 57.14286% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.27%. Comparing base (646ef43) to head (f15f598).

Files with missing lines Patch % Lines
core/trie/bitarray.go 0.00% 3 Missing ⚠️

❌ Your patch check has failed because the patch coverage (57.14%) is below the target coverage (60.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3369      +/-   ##
==========================================
+ Coverage   76.25%   76.27%   +0.01%     
==========================================
  Files         351      351              
  Lines       33340    33340              
==========================================
+ Hits        25423    25429       +6     
+ Misses       6103     6095       -8     
- Partials     1814     1816       +2     

☔ 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.

Copy link
Contributor

@EgeCaner EgeCaner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can initialize the slices with size and assign by index, but I'm not sure if it worth doing since all those are test code and difference should be negligible.

res = append(res, b.len)
res = append(res, bt[:]...)

// 1 byte to accomoaate the length and the other 32 for the data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// 1 byte to accomoaate the length and the other 32 for the data
// 1 byte to accommodate the length and the other 32 for the data


// put random 64 keys and record roots
for range 64 {
const amount = 64
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

turbo small nit: I'd rename amount to something like numKeys

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.

4 participants