Update the logic in SupportCodeLibraryBuilder so instead of using a heuristic (absence of cwd) to detect if we are trying to register support code against a non-running install, we have a specific status field that we update along the create/reset/finalize lifecycle.
β‘οΈ What's your motivation?
In #2353 we are seeing several Windows users reporting this error since 10.0.0 with a configuration that works fine in 9.x.x. This suggests the invalid install error might be a false positive and masking a different issue.
π·οΈ What kind of change is this?
:bank: Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)
:bug: Bug fix (non-breaking change which fixes a defect)
coverage: 98.387% (+0.002%) from 98.385%
when pulling 66c9bbde29c9d2a34d5d2fe8c4dcde1062a2f0f5 on fix/support-code-library-status
into 5a4f129fdb7020e1bc9c1a539a3cea93307881b8 on main.
π€ What's changed?
Update the logic in
SupportCodeLibraryBuilder
so instead of using a heuristic (absence ofcwd
) to detect if we are trying to register support code against a non-running install, we have a specific status field that we update along the create/reset/finalize lifecycle.β‘οΈ What's your motivation?
In #2353 we are seeing several Windows users reporting this error since 10.0.0 with a configuration that works fine in 9.x.x. This suggests the invalid install error might be a false positive and masking a different issue.
π·οΈ What kind of change is this?
π Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.