You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 61b8157
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(scan): always end with exactly one EventDone
scan.Run returned without EventDone on five early-exit paths and when
cancelled during preflight or the wildcard probe, so the CLI, the TUI and
pkg/subenum each handled a channel that could close without a final
event. It now always sends one EventDone, with Stopped set (and the
checks' query count) when nothing was scanned. The CLI treats Stopped as
not done, the TUI maps it to stoppedMsg, and pkg/subenum drops its
synthesized KindDone and exposes Event.Stopped. EventError's doc no
longer calls it non-fatal. A test covers every early-exit path.
Fixes#99
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
### Changed
11
+
- The scan engine always ends with exactly one done event, marked `Stopped` when the scan ended before testing any candidate (out of scope, recursion ceiling, failed preflight or wildcard check, a wildcard zone without `-force`, or Ctrl+C during those checks), so the CLI, the TUI and `pkg/subenum` handle one shape of ending instead of a channel that sometimes closes without one. `pkg/subenum`'s `Event` gains `Stopped`, and a stopped scan's `Stats` now include the queries its checks sent (#99).
12
+
10
13
### Fixed
11
14
-`tools/wordlist-gen` parses flags that appear after a positional the same way `subenum` does, instead of silently ignoring both: a leftover argument is now a usage error (2) that points at `-domain`, and an invalid `-combine` value or an empty `-o` exits 2 instead of 1 (#120).
0 commit comments