fix: set priority mempool logger#496
Conversation
|
The latest Buf updates on your PR. Results from workflow Protobuf / buf-build (pull_request).
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
b515a82 to
5fa9ad4
Compare
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches. Re-running this action after a short time may resolve the issue. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #496 +/- ##
==========================================
+ Coverage 38.03% 38.04% +0.01%
==========================================
Files 325 325
Lines 30765 30766 +1
==========================================
+ Hits 11701 11705 +4
+ Misses 17177 17175 -2
+ Partials 1887 1886 -1
🚀 New features to boost your workflow:
|
Summary
PriorityMempoollogger field inNewPriorityMempoolWhy
PriorityMempoolvalidated that a logger was provided but never stored it on the struct. When mempool cleanup hit an error path and calledp.logger.Debug(...), the nil logger field could panic the worker.Validation
go test ./abcipp