Earlier quoted context omitted.
Clearly the issue is real and not imaginary
There are no imaginary numbers insolved in this bug, however.
Tell that to the compiler.
Math.Pow(-1, 2) == -1 in Windows 11 Insider build
111–120 of 142 posts
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#112Earlier quoted context omitted.
“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.
Sounds very human. I experienced some junior devs who grew up with TDD and would often just tweak their code to pass their tests without stopping to understand their code at a fundamental level - essentially development through trial and error. Since they were also the ones writing the tests the core assumptions went into both and because they did so without thinking they were more likely to have errors. The test bei…
Because AI is learning from humans and half of coders suck.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#113I 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…
Just posting to say everything is fine. It works to report this way too, via .NET maintainers. It is very common to do this as well.
https://github.com/dotnet/runtime/issues/117233#issuecomment...
You’re quoting a community contributor and this is not a firm stance held by MS themselves. He should probably not have posted that because it’s misleading. They even have a tag to triage these kinds of issues.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#114Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#115Earlier quoted context omitted.
If your software has a bug, it’s your bug. If the root cause of the bug in your software comes from a direct call into some dependency, that’s immaterial to the users of your software. Your software is incorrect, so your software has a bug. How you choose to resolve it is up to you. You might implement a fix in your code to handle the bug case until the dependency is fixed.
Of course. They chose to resolve it by saying the underlying software should be fixed. That seems perfectly fine to me.
The responsible thing to do would be to report the bug to the upstream project and keep the issue open pending the underlying issue's resolution.
This is a broader cultural thing. In large organizations there is a tendency toward deflecting as much responsibility as possible onto other teams. In part it's a lack of resources, but it's also a result of individual contributors not being willing to take ownership of the product they work on.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#116Earlier quoted context omitted.
That's not a resolution, that's ignoring the bug.
No, it isn't. It's directing the bug to the people who are able to fix it.
You can fix it by handling the erroneous output from your dependency, or switching out your dependency, or submit a fix to the dependency, or asking them to fix it.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#117Earlier quoted context omitted.
In theory and definitely how it should be for commercially backed projects. For volunteer OSS though (and commercially backed) maintainers are frequently not going to do that in my experience.
I don't think being commercial or volunteer affects this. The end user shouldn't report it upstream, not just because that's putting more burden on the user than is called for, but because the end user likely doesn't know enough about how the component is used in order to make a good bug report or answer questions the upstream component may have. That some OSS devs don't work that way isn't really important in terms…
In this specific case I absolutely agree with you, but if going outside the thread on GPs point, I am way more lenient towards (non commercially backed) OSS projects. I'm usually using the product because no one other than the volunteers are doing it, and if I want something fixed, I might have to put in some work to dig and pinpoint the issue to help a fix along, put in a PR myself, or accept it being broken for a while until someone makes the (unpaid) time. And that's ok, or at least a reality for a lot of OSS.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#118How does the OS still function with a basic bug like this?
There was an article some time ago where someone ran doom with progressively more incorrect value of pi
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#119Earlier quoted context omitted.
It's going to be interpreted, and is probably meant, as saying that the person who filed the bug should close this report and open a new one in the right place.
Since the comment you responded to already complained about use of passive voice... It's going to be interpreted BY WHOM to say that? Other .NET developers? Yeah, maybe, at least some of them. By the submitter of the original bug? No idea, I can't read their mind.
Apply the "reasonable person" standard.
> No idea, I can't read their mind.
Mind-reading is not necessary to predict how people will react to certain patterns of behavior.
Re: Math.Pow(-1, 2) == -1 in Windows 11 Insider build
#120Side 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.
Yup, definitely has felt that way for years, they do try to consolidate but it takes years. When I was trying to setup something for customer support I was navigating all of their redundant products, Teams, Skype, Skype for Business (different thing), Lync.
But that is way more normal for microsoft, because it's about redundant products that get merged eventually. What's not typical is internal dependencies being exposed, the case above were many MSFT teams/products in the same tier, the case in this article is many MSFT teams/products in a single vertical, at different tiers of the supply chain.
It's possible that this is more a feature of open source, this being an open source MSFT product (.NET core) and the report having been filed through an open source channel (github issues). I think that if the issue were submitted to some account manager or customer service rep through a channel linked to a paying customer account, the response would have been very different.
But you cannot expect a quality customer service response if there's no $ being paid to the maintainers. Whether it be Microsoft or whatever FOSS project.