Skip to content

Improve resolver scan intelligence and budget controls#36

Open
AmirrezaFarnamTaheri wants to merge 7 commits into
WhiteDNS:mainfrom
AmirrezaFarnamTaheri:resolver-result-intelligence
Open

Improve resolver scan intelligence and budget controls#36
AmirrezaFarnamTaheri wants to merge 7 commits into
WhiteDNS:mainfrom
AmirrezaFarnamTaheri:resolver-result-intelligence

Conversation

@AmirrezaFarnamTaheri

@AmirrezaFarnamTaheri AmirrezaFarnamTaheri commented May 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add structured resolver scan result rows with resolver, status, source, server domain, latency, attempts, failure reason, observation time, and score.
  • Parse richer scan telemetry when available while preserving existing valid/rejected behavior.
  • Add recommendation summaries that favor low latency, recent success, repeated success, and success across multiple server domains.
  • Bound scan-result history by age/count so result metadata does not grow indefinitely.
  • Add scan budget controls for quick, balanced, deep, expert, high-capacity, max-capacity, and custom worker counts.
  • Normalize persisted, typed, start, and resume worker counts into the supported 1-128 range.
  • Require nonblank scan session IDs for malformed/redelivered scan service starts.
  • Keep scan budget tests near the parallel-settings model tests and keep traffic-clarity changes owned by the setup-readiness branch, so this PR remains resolver-scan scoped.

Verification

@AmirrezaFarnamTaheri AmirrezaFarnamTaheri force-pushed the resolver-result-intelligence branch from 2aa2338 to 9ed0b88 Compare May 15, 2026 23:54
Parse optional scan telemetry such as latency, attempts, and rejection reason while keeping older WD_SCAN lines compatible.

Persist structured scan observations beside the legacy plain resolver file, rank successful results by score, and write recommended_resolvers.txt for future profile selection and diagnostics.

Add focused tests for scan telemetry enrichment, resolver scoring, ranking, and JSON serialization.
@AmirrezaFarnamTaheri AmirrezaFarnamTaheri force-pushed the resolver-result-intelligence branch from 9ed0b88 to 4d79a66 Compare May 16, 2026 08:29
@AmirrezaFarnamTaheri AmirrezaFarnamTaheri changed the title Add structured resolver scan results Add structured resolver result intelligence May 16, 2026
Expose quick, balanced, deep, and expert resolver scan worker presets up to 128 workers while preserving the slider for custom values.

Clamp persisted and launched scan worker counts to the shared scan limit so UI, stored settings, and service launch requests agree.

Adjust user-facing scan guidance based on the selected worker budget and add coverage for built-in/custom budget detection.
Normalize resolver scan worker counts through shared scan defaults so persisted values, manual entry, start, and resume paths all stay within the supported 1-128 range.

Keep 64-worker runs as an explicit high-capacity tier with stronger UI guidance and cover the normalization behavior in model tests.
@AmirrezaFarnamTaheri AmirrezaFarnamTaheri changed the title Add structured resolver result intelligence Improve resolver scan intelligence and budget controls May 16, 2026
Generate a fallback scan session ID when a malformed or redelivered scan service start arrives without the session extra.

This keeps scan state, broadcasts, and failure records attributable to a concrete scan attempt instead of emitting blank-session events.
Place scan worker budget coverage beside the existing parallel-settings tests so the resolver scan PR merges cleanly with setup-readiness validation tests.

This keeps the scan branch behavior unchanged while avoiding overlap at the model-test helper boundary.
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.

1 participant