Wasmtime GitHub notifications bot (Apr 01 2026 at 01:10): Wasmtime GitHub notifications bot (Apr 01 2026 at 01:10):pchickey opened PR #12922 from pchickey:fix_12913 to bytecodealliance:main:
…racterDevice
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Apr 01 2026 at 01:42):pchickey updated PR #12922.
Wasmtime GitHub notifications bot (Apr 01 2026 at 01:43):pchickey edited PR #12922:
- in p1, get_seekable fails with Errno SPIPE for Fifo. Fixes https://github.com/bytecodealliance/wasmtime/issues/12913
- in p2 and p3, plumb through cap_std::fs::FileTypeExt::is_fifo to DescriptorType::Fifo
TODO: tests
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Apr 01 2026 at 01:45):pchickey edited PR #12922:
- in p1, get_seekable fails with Errno SPIPE for Fifo. Fixes https://github.com/bytecodealliance/wasmtime/issues/12913
- in p2 and p3, plumb through cap_std::fs::FileTypeExt::is_fifo to DescriptorType::Fifo
TODO: tests
Related: #515 #10713
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Last updated: Apr 12 2026 at 23:10 UTC