Fix a pylint disable comment - #1205
Conversation
This stopped working with pylint 4.0.7 which is probably a pylint regression, but the correct location for the comment is always on the same line where the error occurs (disable-next can be used to supress the warning on the following like) so this worked only by acciddent anyway.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe ChangesErrorProxy lint suppression
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a narrowly scoped fix to the placement of a lint-disable comment, with no actionable merge-blocking risk remaining beyond normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
49f2be9
into
storaged-project:master
This stopped working with pylint 4.0.7 which is probably a pylint regression, but the correct location for the comment is always on the same line where the error occurs (disable-next can be used to supress the warning on the following like) so this worked only by acciddent anyway.
Summary by CodeRabbit