docs: four sentences say history snapshots stay complete inside unobserved:, and gather refuses a buffer index on a list matrix
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- c
- 领域
- documentation, testing
调研方向
Read RULING R31-2 and the four cited passages in README.md, docs/COMPARISON.md, docs/llms.txt, and docs/PREDICATES.md; compare them with the example in the issue. For gather, decide whether a buffer index vector with a nested list matrix is accepted, then update docs/BUILTINS.md or add a row under tests/phase2/ accordingly. Run tests/test_doc_examples.py and tools/docs_claims_check.sh; done means the documentation matches the ruling and the gather behavior is recorded.
由索引模型根据 Issue 内容生成。
描述
Found by the blind review of #2468 and by the runs of its fix round, outside the list of #2466. Both were seen on phase2-numbers at 05e6d6fd.
1. Four documents say history snapshots stay complete inside unobserved:; the runtime and its ruling say they are not written
README.md(near line 438): "Numeric relative/raw steps, exact flags, running-best state and history snapshots still update inside the block."docs/COMPARISON.md(near line 791): "Numeric samples, interrogation/history snapshots and D2 state remain complete"docs/llms.txt(near line 315): "Numeric samples, exact flags, running-best state and interrogation snapshots remain complete"docs/PREDICATES.md(near line 475): "Numeric value records remain complete, including exact flags, D2 state, the interrogation triple, and history snapshots."
The record: RULING R31-2 on #1758, as the fragment changes/fixed/1758-r312-runaway-contract.md states it: "Elided numeric samples inside unobserved: retain live value and running-best updates without writing line-qualified observer-history snapshots".
Shows it:
x is 3
unobserved:
x is 4
print of [when is x, where is x, why is x, how is x]
print of [where is x at 3, why is x at 3, how is x at 3]
prints [2, 4, 1, 0.00398406374501992] and then [null, null, null]. The same program with if true: in place of unobserved: prints [4, 1, 0.00398406374501992] on its second line. The live interrogatives and trajectory of x are the same in both.
So the live answers after the block are as the documents say, and the line-qualified ones at an elided line are not there. The four sentences are stale against the ruling.
2. gather refuses a buffer index vector when the matrix is a nested list
nl is [[1.0, 2.0], [3.0, 4.0]]
sb is reshape of [buf_from_list of ([1.0, 2.0, 3.0, 4.0]), 2, 2]
ib is buf_from_list of ([0.0, 1.0])
print of (type of (gather of [nl, [0, 1]]))
print of (type of (gather of [sb, [0, 1]]))
print of (type of (gather of [sb, ib]))
print of (type of (gather of [nl, ib]))
prints list, buffer, buffer, and then raises type_mismatch: gather: expected a tensor and an index or index vector. The row in docs/BUILTINS.md says "matrix may be a shaped buffer and indices a list or a buffer"; the _rows/_cols builtins take a buffer index vector with either container. Either the fourth form is accepted (it then returns a list, as every mixed call does), or the row says that a buffer index vector needs a buffer matrix.
Done when
- The four sentences of item 1 say what the ruling says (live value, running best and the live interrogatives are kept; line-qualified snapshots at an elided line are not written), each next to a run of the program above.
- Item 2 is decided on this issue (accept, or document), and the decision is in the tree: a row of
tests/phase2/for the fourth form if it is accepted, or the row's sentence if it is not. -
tests/test_doc_examples.pyandtools/docs_claims_check.shpass on the changed documents.
The bool case of the rows that name a lenient answer is #2409, not this issue.
— Claude DevBox
- 主要语言
- C
- 星标
- 3
- 派生
- 7
- 平均合并
- 3 小时 28 分钟
- 30 天内合并 PR
- 270
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
InauguralSystems/EigenScript 的其他 Issue
-
area:gates kind:gate-defect
难度 2/5 1-3 小时 新手友好度 83/100
InauguralSystems/EigenScript#2476 ·
维护者通常 1 天内回复
-
area:gates needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
InauguralSystems/EigenScript#2462 · 1 条评论 ·
维护者通常 1 天内回复
-
The hosted-RNG check refuses a clean tree that has a tracked file with a double quote in its name未关闭area:gates kind:gate-defect needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
InauguralSystems/EigenScript#2461 · 1 条评论 ·
维护者通常 1 天内回复
-
area:gates kind:gate-defect needs-triage
难度 2/5 1-3 小时 新手友好度 86/100
InauguralSystems/EigenScript#2458 · 1 条评论 ·
维护者通常 1 天内回复
-
`http_post`: `headers` text with something after its JSON value now means no headers, without a word未关闭area:http kind:silent-wrong
难度 2/5 1-3 小时 新手友好度 72/100
InauguralSystems/EigenScript#2394 · 1 条评论 ·
维护者通常 1 天内回复
查看 InauguralSystems/EigenScript 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 92/100
flipperdevices/flipperzero-firmware#4520 ·
维护者通常 1 天内回复
-
area/build-framework kind/enhancement priority/low
难度 2/5 1-3 小时 新手友好度 77/100
yugabyte/yugabyte-db#38826 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
meshcore-dev/MeshCore#3891 · 1 条评论 ·
维护者通常 1 天内回复
-
bug grammar sev-3
难度 2/5 1-3 小时 新手友好度 76/100
-
status: needs-triage type: bug
难度 2/5 1-3 小时 新手友好度 75/100