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 f016c90
Browse filesBrowse the repository at this point in the historyBrowse files
Action: expose the changes file and takeover/internal counts (#311)
The Action reported how many names changed but not where the changes
were, and said nothing about takeover candidates or non-public
addresses, so a workflow could not act on them without re-reading the
report.
It now has three more outputs: changes (the path of changes.jsonl, set
only when there were previous results to compare with), takeovers and
internal. The job summary gains both counts and lists the first 50
takeover candidates. The CI action job asserts the new outputs on the
lab zone, and the monitoring guide shows opening an issue from them.
Co-Authored-By: Claude Mythos 5.2 <noreply@anthropic.com>
Fixes#311
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
31
31
-`-max-duration 20m` gives a run a time budget. When it runs out no new names are tested, lookups already under way finish, and the run ends normally: results, the `-stats` report (`stopped_by: "duration"`, untested names in `skipped_by_cap`) and a `degraded` verdict. Under `-dL` one budget covers every target. The GitHub Action gains a `max-duration` input, so a scheduled scan can stop before the job's `timeout-minutes` kills it without a report, and `pkg/subenum` gains `Config.MaxDuration` and `Stats.Expired`. With `-max-queries`, the report now says `stopped_by: "queries"` (#190).
32
32
- The progress line and the TUI status bar show an estimated time left (`| ETA 4m12s`), from the rate over the last 30 seconds, once a scan has run for 5 seconds; it disappears at 100% (#191).
33
33
-`-diff-records` makes `-diff` compare the records of names found again, so a CNAME re-pointed at an unclaimed service or a moved address is reported as `changed` (`~ name` in text; `"change": "changed"` with `previous_records` in JSON and JSONL), counted in the report's `diff.changed`, and exits 4. When either side has a CNAME only the alias targets are compared, so CDN address rotation is not a change. The previous file must be JSON, JSONL or CSV. The GitHub Action gains a `changed` output (#189).
34
+
- The GitHub Action gains three outputs: `changes`, the path of the JSONL file listing the added, removed and changed names (empty when there were no previous results to diff against), so a later step can open an issue or post them; `takeovers`, the number of takeover candidates found; and `internal`, the number of names answering with an address that is not public. The job summary table has a column for each count and lists the takeover candidates under it. `docs/monitoring.md` shows a step that opens an issue from `changes` (#311).
34
35
35
36
### Changed
36
37
- A run that `-max-duration` stopped with names untested, or that the reliability guard aborted, saves its resume state to the `-state` file like an interrupted one and prints `continue with: subenum -resume <file>`, so a time-boxed job continues where the last one stopped instead of testing the same first names again. The exit code is unchanged (0 for a spent budget). A resumed run that stops the same way saves its state again, and one that finishes no longer counts the names an earlier part skipped, so it can end `complete` (#294).
0 commit comments