[cli-tools-test] [CLI exploratory testing] Windows deprecated missing-tool key fails strict dry-run gate

Đang mở Phù hợp với người mới
  • Có gì không ổn?
#74,755 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
2/5
Thời gian dự kiến
1-3 giờ
Mức phù hợp với người mới
70/100
Loại issue
Lỗi
Độ rõ ràng
Đặc tả rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
github-actions, go
Lĩnh vực
ci-cd

Hướng nghiên cứu

Đọc .github/workflows/windows.md quanh dòng 54 và kiểm tra cách các mẫu workflow đáng tin cậy cấu hình đầu ra an toàn. Chuyển khóa đã lỗi thời missing-tool sang report-missing-tool, sau đó biên dịch workflow Windows với các thiết lập dry-run nghiêm ngặt và xem lại tệp windows.lock.yml được tạo lại. Hoàn tất khi cổng cảnh báo theo lô vượt qua và tệp lock phản ánh workflow đã cập nhật.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

automation cli-tools testing
Overview

Bounded testing on 2026-11-04 found that .github/workflows/windows.md:54 uses the deprecated missing-tool safe-output key. Its strict dry-run compile emits a lock but fails the overall warning gate. Severity: Low; observed once. This is a repository workflow compatibility issue, not evidence that the safeguard should be weakened.

Reproduction
  1. On github/gh-aw, invoke agenticworkflows MCP compile with workflows=[windows], dry_run=true, strict=true.
  2. Inspect both workflow and batch results.
  3. The workflow result is valid and identifies windows.lock.yml, but the compiler batch is invalid and dry_run.gate is failed.

Expected: the maintained trusted sample uses current settings and passes the strict gate. Actual diagnostic: The missing-tool safe-output key is deprecated. Use report-missing-tool instead.

Proposed correction: migrate the setting through normal workflow maintenance, then compile and review the regenerated lock. No workflow source was edited by this tester.

Diagnostics and bounded coverage

Passed checks

  • Discovery returned 356 workflows, all marked compiled. Sampled triggers and imports matched the selected sources; freshness was not independently established.
  • Five logs queries, always count=3: last day; daily-workflow-security-model over seven days; copilot engine over one day; nonexistent-workflow-xyz; future date 2099-01-01. Exposed JSON summaries were readable. Nonempty results had at most three runs and consistent IDs, workflow names, engines, statuses and timestamps. Unknown workflow returned actionable guidance; future date returned zero runs. Count-limited results warned about partial coverage.
  • Two completed-run audits: failed Daily Workflow Security Model and successful PR Finisher. Metadata agreed with logs. Reports exposed job timing, metrics and safe-output summaries; the success sample exposed bash and safeoutputs.noop calls, MCP health, and 24 network requests. Its noop described unfinished task work, so workflow success is not task completion. Neither sample created GitHub resources. Invalid audit ID 0 returned clear guidance.
  • Windows emitted a local lock with frontmatter/body hashes, strict/dry-run metadata, expected job sections and staged safe outputs; ShellCheck passed with zero added findings. This was structural inspection, not independent complete Actions validation.
  • Logs took approximately 7.5–9.7 seconds for nonempty queries and 1.5 seconds for the future date. Audits took 11.0 and 9.4 seconds. Compiles took 0.9–2.7 seconds. These are single observations.

Observed problems

Windows failed the batch warning gate on the deprecated key. A per-workflow valid result must not be interpreted as an overall gate pass. The tool also warned that cached model inventory may be stale.

Blocked or unfinished required checks

All three targeted compiles used dry_run=true and strict=true; zero passed the overall gate. Archie was rejected for pre-agent steps and custom MCP servers. Daily Workflow Security Model was rejected for custom steps. These safeguard denials were not retried or worked around. Passing complex/import compilation, corresponding generated-lock inspection, and compile-to-existing-run integration remain unverified. The failed existing run used SHA f3dc4385203cb61f4ebc410546ee91822538e884; it does not validate a newly generated lock.

Not tested (expected exclusion)

  • Malformed YAML, invalid tool configuration and missing imports: synthetic fixtures prohibited.
  • Private raw logs, raw directory structure and independent artifact completeness: outside scope.
  • Execution of newly compiled locks: dispatch prohibited.
  • Historical/retention and in-progress audit variants: outside the two completed-run sample.
  • Redundant date variants and incremental recompilation: optional variants omitted after failed compile gates.
  • Created-resource links and failed sub-agent attribution: not exercised by these samples.
Next actions

Migrate the Windows setting and review which trusted samples satisfy the existing safeguards. Required compile coverage is incomplete and is being reported separately. No locks were published, pushed or executed. This sample does not establish repository-wide CLI health.

References:

Generated by 🧪 Daily Cli Tools Tester · codex · gpt60 · ~155 AIC · ⌖ ~57 AIC · ⊞ 21.2K · ◷

  • expires on Nov 10, 2026, 9:23 PM UTC-08:00
Ngôn ngữ chính
Go
Star
5.6k
Fork
615
Merge trung bình
5 giờ 19 phút
Pull request đã merge (30 ngày)
798

Chuẩn bị môi trường

Mở trong Codespaces

Khởi chạy dev container của dự án ngay trên trình duyệt, bằng tài khoản GitHub của bạn.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của github/gh-aw

Tất cả issue của github/gh-aw

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.