`FileHandle.metadata` is annotated to return a file handle, but returns the `Metadata`
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 64/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript, node.js
调研方向
Start with the FileHandle.metadata annotation and the _FileSystem_fstat kernel path, using the linked reproduction as the baseline. Run the provided gren make examples, then verify that metadata exposes FileSystem.Metadata fields and that the read example no longer accepts an incompatible handle or crashes.
由索引模型根据 Issue 内容生成。
描述
Found against: gren 0.6.6, gren-lang/core 7.4.2, gren-lang/node 6.1.3, node 22
Reproduction: https://github.com/gilramir/gren-bug-reports/tree/main/2026-09-14-filehandle-metadata-type
FileSystem.FileHandle.metadata is annotated
metadata : ReadableFileHandle a -> Task FileSystem.Error (ReadableFileHandle FileSystem.Metadata)
but its kernel code, _FileSystem_fstat, succeeds with the Metadata record
itself. So reading a field of the result, the one thing metadata is for, does
not compile, and passing the result to FileHandle.read, which does compile,
crashes the program instead of failing the task.
Reproduction
gren.json dependencies: gren-lang/core 7.4.2, gren-lang/node 6.1.3. Save as src/Main.gren, which reads the size of gren.json through a file handle. Build with gren make Main --output=app:
module Main exposing (main)
import FileSystem
import FileSystem.FileHandle as FileHandle
import FileSystem.Path as Path
import Init
import Node
import Stream
import Task
main : Node.SimpleProgram a
main =
Node.defineSimpleProgram <| \env ->
Init.await FileSystem.initialize <| \fs ->
Node.endSimpleProgram
(FileHandle.openForRead fs (Path.fromPosixString "gren.json")
|> Task.andThen FileHandle.metadata
|> Task.map (\m -> "byteSize = " ++ String.fromInt m.byteSize)
|> Task.onError (\e -> Task.succeed (FileSystem.errorToString e))
|> Task.andThen (\line -> Stream.writeLineAsBytes line env.stdout)
|> Task.onError (\_ -> Task.succeed env.stdout)
)
Output:
$ gren make Main --output=app
Compiling ...-- TYPE MISMATCH ------------------------------------------------- src/Main.gren
This function cannot handle the argument sent through the (|>) pipe:
17| (FileHandle.openForRead fs (Path.fromPosixString "gren.json")
18| |> Task.andThen FileHandle.metadata
19| |> Task.map (\m -> "byteSize = " ++ String.fromInt m.byteSize)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The argument is:
Task.Task
FileSystem.Error
(FileHandle.ReadableFileHandle FileSystem.Metadata)
But (|>) is piping it to a function that expects:
Task.Task FileSystem.Error { a | byteSize : Int }
Detected problems in 1 module.
src/ReadFromMetadata.gren is the same program with Task.map (\m -> ...)
replaced by what the annotation allows:
|> Task.andThen FileHandle.read
|> Task.map (\_ -> "read from the metadata")
It compiles, and crashes:
$ gren make ReadFromMetadata --output=app && node app
node:internal/errors:540
throw error;
^
TypeError [ERR_INVALID_ARG_TYPE]: The "fd" argument must be of type number. Received undefined
at Object.read (node:fs:604:8)
at _FileSystem_readHelper (/path/to/app:3260:6)
at Object.b (/path/to/app:3239:5)
at _Scheduler_step (/path/to/app:298:25)
at _Scheduler_enqueue (/path/to/app:279:7)
at /path/to/app:300:9
at /path/to/app:3484:9
at FSReqCallback.oncomplete (node:fs:197:5) {
code: 'ERR_INVALID_ARG_TYPE'
}
Node.js v22.23.2
- 主要语言
- JavaScript
- 星标
- 13
- 派生
- 6
- 平均合并
- 4 天 10 小时
- 30 天内合并 PR
- 4
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
gren-lang/node 的其他 Issue
-
`ChildProcess.spawn` with `NoShell` looks for a program named after the program and its arguments未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
-
bug
难度 3/5 1-2 天 新手友好度 74/100
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 78/100
githubnext/gh-aw-workshop#3897 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
难度 2/5 1-3 小时 新手友好度 91/100
维护者通常 1 天内回复