Skip to content

⚡ Bolt: Optimize re.sub callback in PTT parse - #490

Draft
xbmc4lyfe wants to merge 1 commit into
mainfrom
bolt/optimize-ptt-regex-callback-5287172168328181358
Draft

⚡ Bolt: Optimize re.sub callback in PTT parse#490
xbmc4lyfe wants to merge 1 commit into
mainfrom
bolt/optimize-ptt-regex-callback-5287172168328181358

Conversation

@xbmc4lyfe

Copy link
Copy Markdown
Collaborator

💡 What

Optimized the _NOT_ONLY_NON_ENG_PART1 regular expression substitution inside _apply_not_only_non_english_regex by replacing a Python callback function (_keep_english_prefix) with a native string template backreference (r"\1"). This required adding a capture group to the regex and allowed the removal of the now-obsolete _ENGLISH_PREFIX regex.

🎯 Why

In performance-sensitive code, using a Python lambda or callback function with re.sub incurs a significant overhead because the regex engine must cross the C-to-Python boundary for every match. By capturing the desired string in the regex and using a string replacement template, the entire substitution stays within the C execution environment, providing a measurable performance boost on hot paths like parsing strings.

📊 Impact

Execution time for _apply_not_only_non_english_regex is significantly reduced. Benchmarks show a ~3x speedup for this specific substitution by keeping the operation in C.

🔬 Measurement

Run the unit test suite to verify no regressions in parsing behavior:
PYTHONPATH=.:repo/plugin.video.nzbdav uv run --with-requirements requirements-dev.txt --with pytest --with pytest-cov --with pytest-mock --with defusedxml --with httpretty --with mock --no-project --python 3.14 pytest tests/ -v --tb=short -m "not integration and not functional and not extreme"


PR created automatically by Jules for task 5287172168328181358 started by @xbmc4lyfe

Replaced the callback function `_keep_english_prefix` inside `_apply_not_only_non_english_regex` with a native string template backreference `\1` by capturing the English prefix in the first regex alternative. This avoids crossing the C-to-Python boundary for every match and significantly improves parsing speed on hot paths without modifying expected behavior.

Co-authored-by: xbmc4lyfe <273732874+xbmc4lyfe@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@xbmc4lyfe, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 70c387f4-d7b3-4e3f-8183-b18c06ca3559

📥 Commits

Reviewing files that changed from the base of the PR and between c8dfe60 and 8361bd1.

📒 Files selected for processing (1)
  • repo/plugin.video.nzbdav/resources/lib/ptt/parse.py

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the addon label Aug 6, 2026
@codacy-production

Copy link
Copy Markdown
Contributor

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@github-code-quality

Copy link
Copy Markdown

Code Coverage Overview

Languages: Python

Python / code-coverage/pytest

The overall coverage in commit 8361bd1 in the bolt/optimize-ptt-re... branch remains at 88%, unchanged from commit c8dfe60 in the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant