-
Notifications
You must be signed in to change notification settings - Fork 176
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
avoid syntax warning for "\{" and "\}" #1539
Conversation
WalkthroughThe recent update involves a minor correction in string interpolation within a Python script. This change enhances the consistency of the code formatting, ensuring that the string variables are embedded correctly and uniformly throughout the script. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Out of diff range and nitpick comments (22)
dpgen/generator/run.py (22)
Line range hint
521-521
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("continue from iter %03d task %02d" % (iter_rec[0], iter_rec[1])) + dlog.info("continue from iter %03d task %02d", iter_rec[0], iter_rec[1])
Line range hint
770-770
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("cvasp is on !") + dlog.info("%s is on !", "cvasp")
Line range hint
775-775
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
851-851
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
1004-1004
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
1117-1118
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
1950-1950
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2023-2023
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2024-2024
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2058-2058
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2665-2665
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2670-2670
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
2675-2675
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3180-3180
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3187-3187
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3191-3191
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3195-3195
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3247-3247
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
3928-3928
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
4157-4157
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
4173-4173
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Line range hint
4210-4210
: Use format specifiers instead of percent format in logging statements to ensure compatibility and consistency.- dlog.info("failed frame: %6d in %6d " % (icount, tcount)) + dlog.info("failed frame: %6d in %6d ", icount, tcount)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## devel #1539 +/- ##
=======================================
Coverage 49.49% 49.49%
=======================================
Files 83 83
Lines 14816 14816
=======================================
Hits 7333 7333
Misses 7483 7483 ☔ View full report in Codecov by Sentry. |
Avoid
SyntaxWarning: invalid escape sequence '\{'
Summary by CodeRabbit