Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

fix(mcp): test passes timeout_seconds and check_ignore to runners that reject them

オープン
  • 何か問題がありますか？
#1,779 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
67/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
dart, flutter
領域
cli, testing

調査の方向性

Start with _parseTest in lib/src/mcp/mcp_server.dart, then read the runner option definitions in lib/src/commands/test/test.dart and lib/src/commands/dart/commands/dart_test_command.dart. Reproduce both argument combinations from the issue and check the MCP schema descriptions. Done when each combination either works on both runners or returns a clear validation failure naming the unsupported argument and runner.

索引モデルが issue の本文から書いたものです。

説明

bug
Description

The MCP test tool builds a command line from its arguments without checking which runner will receive it. Two arguments are accepted by the tool schema but rejected by one of the two runners, so the call fails with exit 64 before any test runs.

Tool arguments Command built Result
dart: true, timeout_seconds: 180 very_good dart test --timeout 180 -- … Could not find an option named "--timeout".
check_ignore: true on a Flutter package very_good test --coverage --min-coverage 100 --check-ignore … Could not find an option named "--check-ignore".

The cause is visible on main (8c772f3):

  • _parseTest in lib/src/mcp/mcp_server.dart appends --check-ignore and --timeout unconditionally, whichever runner dart selects.
  • --timeout is registered only on very_good test (lib/src/commands/test/test.dart).
  • --check-ignore is registered only on very_good dart test (lib/src/commands/dart/commands/dart_test_command.dart).
  • Neither the timeout_seconds nor the check_ignore schema description says it is runner-specific.

This bites agents twice: an agent told to "always set timeout_seconds" cannot test a pure Dart package, and an agent told to pass check_ignore cannot test a Flutter one. The plugin's green-gate skill currently instructs both (VeryGoodOpenSource/vgv-ai-flutter-plugin#178).

Steps To Reproduce
  1. Call the MCP test tool on a pure Dart package with {"dart": true, "timeout_seconds": 60}.
  2. Observe partial_failure / validation: Could not find an option named "--timeout".
  3. Call the MCP test tool on a Flutter package with {"check_ignore": true}.
  4. Observe partial_failure / validation: Could not find an option named "--check-ignore".
Expected Behavior

One of the following, in order of preference:

  1. Each argument works on both runners: very_good dart test gains --timeout (ideally the wall-clock kill from #1765 / #1766) and very_good test gains --check-ignore.
  2. Otherwise, the handler validates combinations before running and returns a validation failure that names the argument and the runner it applies to, and the schema descriptions say which runner each argument supports.
Additional Context

  • Seen in field use in 3 of 310 calls (sessions 2007f494 on 2026-10-07 and 493ade61 on 2026-10-14). Transcript excerpts are available on request.

  • very_good_cli 1.5.0, Dart 3.13.5, Flutter 3.47.6, macOS 26.5 arm64, Claude Code 2.1.302.

  • Related: #1765 (timeout does not kill a hung run), #1705 (MCP surface narrower than the CLI).

  • Tracking issue: VeryGoodOpenSource/vgv-ai-flutter-plugin#180

主要言語
Dart
スター
2.4k
フォーク
244
平均マージ
2日 16時間
マージ済み PR（30日）
21

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

VeryGoodOpenSource/very_good_cli のほかの issue

VeryGoodOpenSource/very_good_cli の issue をすべて見る

似ている issue

Dart の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。