Skip to content

Filter unsafe entries from verified fallback - #25

Closed
rtwo2 wants to merge 11 commits into
mainfrom
fix/fallback-output-safety
Closed

rtwo2 wants to merge 11 commits into
mainfrom
fix/fallback-output-safety

Conversation

@rtwo2

@rtwo2 rtwo2 commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Use the existing FilterSafeLastGoodLinksAsync helper when falling back to state/verified_last.txt.
  • Filter stale/malformed or Cloudflare/WARP-related entries from the fallback instead of blindly copying the old snapshot into verified.txt.
  • If the old snapshot has no safe entries, use current-run Xray-verified nodes even below the normal replacement threshold; if neither source yields safe entries, fail before replacing the published sub/ tree.
  • Defer updating state/verified_last.txt until after the complete staged output tree has been published. A failure while generating later categories can no longer advance fallback state beyond the last successfully published output.
  • Persist the sanitized fallback after successful publication so filtered entries do not reappear every run.

Validation

  • Reviewed the current output-generation and workflow validation paths.
  • The GitHub CI run for the initial PR commit was queued; the latest commit has not yet reported a CI run.
  • A local .NET build/runtime test could not be run in this environment. Please treat CI as required before merging.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants