chore: use pointer receivers for PebbleDB methods#282
chore: use pointer receivers for PebbleDB methods#282swift1337 merged 3 commits intocometbft:mainfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 21 files with indirect coverage changes
🚀 New features to boost your workflow:
|
094bca3 to
f6d3509
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on February 16
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
f6d3509 to
abf2e28
Compare
PR checklist
.changelog(we use unclog to manage our changelog)Note
Converts select
PebbleDBand iterator methods to use pointer receivers to avoid value copies and ensure stateful behavior.DeleteSync,Close, and iteratorNextto pointer receivers inpebble.go*PebbleDBtools/Dockerfileto addCXXFLAGS="-Wno-maybe-uninitialized"when building RocksDB to suppress compiler warningsWritten by Cursor Bugbot for commit abf2e28. This will update automatically on new commits. Configure here.