Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Shell constructs that still do not parse after beta.17 (48 recorded Netclaw commands)

未關閉
#227 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp
領域
compilers

研究方向

Start by locating the parser entry point and reproducing the relevant rows from the Netclaw corpus. The issue identifies a redirect after done and ${x:-literal} / ${x%/} as the cheapest candidates, while warning that the redirect needs a planned public API. Done means the selected constructs parse correctly without changing the intentional fail-closed behavior for assignments or exports of PATH, TMPDIR, HOME, or LC_ALL.

由索引模型根據 Issue 內容生成。

描述

Summary

Netclaw keeps a corpus of real shell commands that it recorded from live sessions. Netclaw uses the corpus to test shell approval. A row is one entry in the corpus.

After ShellSyntaxTree 0.4.0-beta.17, 48 corpus rows (6,912 calls) still do not parse. These rows are candidates for a later release.

Rows by cause

  • 9 rows: a redirect after a compound command (done 2>/dev/null | head). This needs a planned public API. Otherwise a new property could hide write targets from consumers that do not know it.
  • 9 rows: arithmetic $((…)). Bash can run code through an array subscript, so this needs its own bounded grammar.
  • 8 rows: complex parameter expansion (${d%/}, ${x:-y}). ${x:-literal} and ${x%/} are the likely first candidates.
  • 3 rows: process substitution <(…). This needs a new occurrence role or region.
  • 4 rows, one cause each: a function definition, reserved execution syntax, bash -c 'set -e …', and an unbalanced quote.
  • 15 rows: assignment or export of PATH, TMPDIR, HOME, or LC_ALL. These fail closed on purpose. Keep them that way.

Status

Backlog. The cheapest wins are the redirect after done and the two common expansions.

主要語言
C#
星號
15
分支
0
平均合併
9 小時 8 分鐘
30 天內合併 PR
46

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Aaronontheweb/ShellSyntaxTree 的其他 Issue

查看 Aaronontheweb/ShellSyntaxTree 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。