Skip to content

Xafloc/NoteFlow

v0.7.5 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 1mo Productivity & Wikis
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Fixed infinite CPU spin when archiving CSS‑heavy sites due to regex replace failure.

Changes in this release

Bugfix High

Fixes infinite CPU loop when archiving CSS‑heavy sites.

Fixes infinite CPU loop when archiving CSS‑heavy sites.

Source: llm_adapter@2026-06-04

Confidence: high

Full changelog

Fixed

  • Archiving CSS-heavy sites hung forever. inline_css_resources() used a re-scan loop with a literal str.replace to inline CSS url(...) and @import references. The regex captured URLs without their surrounding quotes, so for the common url("...") form the replace never matched — the reference stayed in the CSS, the loop's termination flag was reset on every pass, and it spun on the CPU indefinitely. (Any url() that failed to fetch caused the same non-termination.)

    In practice this hung archiving of large sites such as foxnews.com: the archive never completed, no file was written, and nothing was logged after "Found +link". Sites with little or no CSS (e.g. example.com) were unaffected, which is why the bug was intermittent.

    The function now uses re.sub with callbacks — each reference is rewritten exactly once (quotes included) with no re-scan loop — plus a recursion-depth guard for circular @imports. Archiving such sites now terminates at the archive deadline (~30s) and writes a partial archive instead of hanging.

Builds on v0.7.4 (archiving runs off the event loop) and v0.7.3 (archive_ssl_verify toggle).

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Xafloc/NoteFlow

Get notified when new releases ship.

Sign up free

About Xafloc/NoteFlow

All releases →

Related context

Beta — feedback welcome: [email protected]