fix: very-good-cli MCP field diagnostic (310 calls) — tracking issue

Đang mở
  • Có gì không ổn?
#180 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

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

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
30/100
Loại issue
Lỗi
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
dart, flutter, shell
Lĩnh vực
tooling

Hướng nghiên cứu

Read the linked findings #171, #178, #179, and #147, then follow the referenced very_good_cli issues to understand each tracked bug and its status. Start with the suggested priority and verify the listed outcomes against the sub-issues. Done means the tracked findings are resolved across both repositories, including the version bump checklist in #178 after the releases.

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

Mô tả

bug external dependency p2
Summary

Field diagnostic from 310 very-good-cli MCP calls made by Claude Code with this plugin between 2026-10-04 and 2026-10-16: 292 test and 18 create. 119 returned partial_failure. That looks like an unstable server, and mostly it isn't one.

  • About 97 of the 99 test failures were real failing tests (82) or coverage gates (15), reported faithfully but labelled transient with "check the network" advice.
  • The rest come down to a handful of small, fixable bugs in very_good_cli, this plugin's skills, and this plugin's Bash hook.
  • Running test calls in parallel in the same repo did not cause failures: 46 of 52 overlapping calls succeeded.

This issue tracks the findings across both repos. Each sub-issue is self-contained.

Outcomes
Outcome test create
Success 174 1
partial_failure / transient (exit 69 or exception) 99 17
partial_failure / validation (exit 64) 3 0
Moved to background after 120 s (hung) 16 0
MCP disconnect during a call 0 0

The 17 create exceptions: 9 unquoted YAML descriptions, 6 missing workspace roots, 2 stale-snapshot Invalid SDK hash.

Findings and where each is tracked
# Finding Repo Tracked in Status
1 Exit 69 (failing tests, coverage gate) labelled transient very_good_cli VeryGoodOpenSource/very_good_cli#1722 Fixed on main by VeryGoodOpenSource/very_good_cli#1725, not released
1b Exceptions still transient; no structured results; non-JSON payloads very_good_cli VeryGoodOpenSource/very_good_cli#1782 New
2 create writes description unquoted; half-generated project very_good_cli VeryGoodOpenSource/very_good_cli#1780 New
3 test sends --timeout / --check-ignore to runners that reject them very_good_cli VeryGoodOpenSource/very_good_cli#1779 New
3b green-gate / testing skills instruct those invalid combinations this repo #178 New
4 timeout_seconds does not kill a hung tester very_good_cli VeryGoodOpenSource/very_good_cli#1765 PR VeryGoodOpenSource/very_good_cli#1766 open
5 create with workspace: true fails when root does not list package very_good_cli VeryGoodOpenSource/very_good_cli#1781 New
6 Stale pub snapshot after a Dart upgrade; SessionStart blames PATH this repo #171 Fix promised
7 block-cli-workarounds blocks heredocs and multi-line strings this repo #179 (new mechanism), #147 (quoted |) New / open
8 One genuine Flutter tool crash (lcov.info missing) very_good_cli folded into VeryGoodOpenSource/very_good_cli#1782 New
Correction for #171

#171 attributes the _WrappedYamlException failures from create to the stale snapshot. The data says otherwise: the same exception occurred in session eed4e6dc, which started after the snapshot was rebuilt, and it follows unquoted ": " in descriptions exactly (9 of 9). Those failures are VeryGoodOpenSource/very_good_cli#1780. Only the 2 Invalid SDK hash failures came from the snapshot. The rest of #171 stands. Its optional ask, comparing the snapshot's SDK with dart --version at SessionStart and recommending dart pub global activate very_good_cli on mismatch, would have caught both field incidents (2026-09-22, Dart 3.12.2 → 3.13.4, server would not connect; 2026-10-04, 3.13.4 → 3.13.5).

Suggested priority
  1. Release very_good_cli with VeryGoodOpenSource/very_good_cli#1725, then structured results (VeryGoodOpenSource/very_good_cli#1782). This stops agents being misled on about a third of test calls.
  2. Quote YAML in create (VeryGoodOpenSource/very_good_cli#1780). A template fix that prevents half-written packages.
  3. Ship the timeout kill (VeryGoodOpenSource/very_good_cli#1766) and correct the skills that rely on it (#178). Hung testers cost the most wall-clock time.
  4. Argument validation, workspace roots, snapshot check, hook parsing: VeryGoodOpenSource/very_good_cli#1779, VeryGoodOpenSource/very_good_cli#1781, #171, #179 / #147.

Once very_good_cli releases VeryGoodOpenSource/very_good_cli#1725 and VeryGoodOpenSource/very_good_cli#1766, bump MIN_VERSION in hooks/scripts/vgv-cli-common.sh (checklist item in #178).

Environment
Item Value
Plugin 0.0.5 (project scope)
MCP launch .mcp.json → very_good mcp via the pub shim ~/.pub-cache/bin/very_good
very_good_cli 1.5.0
Flutter / Dart 3.47.6 stable / 3.13.5
OS macOS 26.5 (25F71), arm64
Client Claude Code 2.1.302, Opus 5.5

Claude Code transcript ids are cited in each sub-issue; excerpts are available on request.

Ngôn ngữ chính
Shell
Star
178
Fork
24
Merge trung bình
1 ngày 5 giờ
Pull request đã merge (30 ngày)
9

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

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 VeryGoodOpenSource/vgv-ai-flutter-plugin

Tất cả issue của VeryGoodOpenSource/vgv-ai-flutter-plugin

Issue tương tự

Thêm issue về Shell/Bash

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.