From the response it is already fixed; no details on cause unfortunately: “This uCRT bug has been already reported through another channel a week ago and it got fixed since
(OS #58189958: pow(-1, 2) returns -1). It might take a while to be available in the public insider builds”
Math.Pow(-1, 2) == -1 in Windows 11 Insider build
41–50 of 142 posts
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#42Earlier quoted context omitted.
I'm more used to hear this kind of 'it's not our fault' crap from state bureaucracies not companies that want me to pay them...
When a company has its street named after themselves and a fleet of buses to carry employees to the company, one can start considering Microsoft as a state with all the necessary bureaucracy.
Large enough companies are states - period. Apple is a state. So was Standard Oil.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#43How does the OS still function with a basic bug like this?
I don’t think there is much systems code that needs an exponent of -1, maybe none that needs exponents at all (aside from 2^n, which has opcodes, not C functions)
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#44I really want to know how this could have passed CI testing. (Comments blame it on UCRT, not .NET but… that doesn’t matter much to me.)
“Oh, I can see the test is failing. Let me fix this by adjusting the test to expect the currently returned value.”
This is unfortunately an actual quote I got from Claude Code after having it write a unit test for me.
It ended up mocking the entire method it was supposed to test, resulting in the unit test essentially only testing itself.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#45Side note. One of the advantages of using proprietary packaged software is supposed to be a unified support and product. In this case the maintainer redirects the issue to some other team and passes the ball as if it were an open source project with 50 dependencies with thin responsibilities "no, if there's an issue with a button, you should report it to GUI-button, we do GUI-form and we just pass the button generati…
Microsoft is a many headed beast. Finding the right contact even for employees inside the beast is challenging and a skill all its own.
Which is exactly why the employees need to be the ones shepherding these reports to the right place.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#46> If you need to contact us better, joining the osu! Discord server would be best
I really dislike how Discord is slowly eating up the web and being used as the primary channel for communication, when most of the community resources resides in their Discord, it makes it hard for me to find relevant information through the web thanks to Discords lock-in
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#47Side note. One of the advantages of using proprietary packaged software is supposed to be a unified support and product. In this case the maintainer redirects the issue to some other team and passes the ball as if it were an open source project with 50 dependencies with thin responsibilities "no, if there's an issue with a button, you should report it to GUI-button, we do GUI-form and we just pass the button generati…
The buck is passed all of the time, it simply happens internally and out of sight of the customer. In this case, it looks like an open source component managed by a commercial company. They could do everything out of sight, but the open source world also encourages transparency.
It's easy to have both transparency and proper handling. "Thank you for the report. This issue is actually in the underlying Whatever library. I've passed it along to that team."
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#48I really want to know how this could have passed CI testing. (Comments blame it on UCRT, not .NET but… that doesn’t matter much to me.)
[deleted]
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#49I disagree with the comment “Both Math.Pow and std::pow invokes the pow function in UCRT, which is shipped with Windows. The issue should be reported to MSVC instead” It’s not the job of a bug reporter to figure that out and to verify that nothing goes wrong in setting up stuff for invoking that function or in getting its output back into the C# world. That’s even more true because the dynamic nature of .NET code mak…
What do you disagree with, exactly? The bug is in an underlying library, so it should be reported to that library. That all seems correct to me, I don't see what there is to disagree with there. The problem with the comment is it does not make ownership of the next steps clear. The maintainer should've either taken the ball ("I will report this to...") or made it clear that the reporter should hold the ball ("We can'…
Unless the documentation says that Math.Pow just returns the result of calling some other code (it doesn't do that), the bug is both in the Math.Pow and underlying library. It should be reported and tracked in both.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#50Earlier quoted context omitted.
What do you disagree with, exactly? The bug is in an underlying library, so it should be reported to that library. That all seems correct to me, I don't see what there is to disagree with there. The problem with the comment is it does not make ownership of the next steps clear. The maintainer should've either taken the ball ("I will report this to...") or made it clear that the reporter should hold the ball ("We can'…
>The bug is in an underlying library they didn't test that they just assumed that since they call a library function the library function must be the root-cause. This is classic bug-punting.
If you can't hunt it, punt it!