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 小时 54 分钟
30 天内合并 PR
40

环境准备

  • 没有 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 摘要。