fix: restore conservative source-worker default

This commit is contained in:
NotoriousRebel
2026-08-15 11:41:06 -04:00
parent f44807a046
commit 4bcf2ceae9
5 changed files with 6 additions and 6 deletions
+2 -2
View File
@@ -66,7 +66,7 @@ run_id="$(curl -s http://127.0.0.1:5000/api/v1/runs \
"target": "example.com",
"sources": ["emails", "crtsh"],
"limit": 500,
"source_workers": 6,
"source_workers": 3,
"deadline_seconds": 1800
}' \
| jq -r '.run_id')"
@@ -79,7 +79,7 @@ curl -s "http://127.0.0.1:5000/api/v1/runs/$run_id" \
Run submission is asynchronous. Lifecycle status is `queued`, `running`, `cancelling`, `cancelled`, `completed`, or `failed`. Terminal evidence status is reported separately as `complete`, `partial`, or `failed` when evidence exists.
`source_workers` is the same positive concurrency used by CLI `-j` or `--source-workers` and HarvestView. It defaults
to six, is reduced when fewer sources are selected, and never skips sources or limits their results.
to three, is reduced when fewer sources are selected, and never skips sources or limits their results.
P1 DNS and P2 direct options are fields on the same run request. The OpenAPI schema shows their current defaults, limits, and descriptions. The server uses the operator-selected target and does not impose a public-only egress policy.