Shader Key Files not being generated due to System.IO.IOException: Pipe is broken
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release/GitHub (please choose appropriate option)
Github
Version: Version number and/or git branch
4.2.0.2188 - branch #10abd2
Platform(s): Does the problem occur on Windows, Android...?
Windows
Describe the bug
Shaders keys do not get generated as a result of a broken pipe in the custom tools pipeline (I guess, I don't totally understand this)
To Reproduce
Steps to reproduce the behavior:
- Switch to the most recent release
- Find ApplyAmbientOcclusionShader.sdsl in the solutions explorer
- Right click, Run Custom Tool
Expected behavior
A shader key file to be generated (again, I don't know how this is supposed to work...)
Log and callstacks
BrokenPipeWhenGeneratingKeyFiles.txt
VSBuildToolsConfig.txt
VSCommunity2022Config.txt
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Visual Studio by running the custom tool for ApplyAmbientOcclusionShader.sdsl on the 4.2.0.2188 release branch. Start with BrokenPipeWhenGeneratingKeyFiles.txt and the supplied Visual Studio configuration files; done means the shader key file is generated without the System.IO.IOException broken-pipe failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100