madelson

@navba-MSFT disabling caching on the proxy or in Azure itself doesn't feel like a good long-term answer here. The proxy is just complying with the HTTP caching headers Azure is...

> Sohttps://github.com/Azure/azure-sdk-for-net/issues/31975#issuecomment-1290045858 to add the response header to disable the caching was suggested. @navba-MSFT but this is a configuration change to the Azure account, which requires access/control over that account....

What's the current status of this? We have an ASP.NET Core application with zh-CN and zh-TW resource which we need to start deploying on Linux. So far we've identified that...

Thanks for the context @tarekgh ! > This issue is open to fix this issue. When this issue is resolved, you'll be able to do so at that time. Great...

I'd love to see a fix for this. Tracking this down is not trivial.

> This issue doesn't have to do with the queues but with the fact that the test cases are defaulting to Parallel within their containing suite. That's how it's defined...

> So, in this case, NonParallelizable means that the suite itself is non-parallelizable, that is, it cannot run in parallel with any other suite or fixture. It says nothing about...

> There's no interaction at all. All fixtures are able to run in parallel, unless you make some exception on a particular fixture @CharliePoole sorry if I'm just being dense...

Given https://github.com/stesee/ClosedXML/pull/41 is there a potential path forward for merging in that fork?

My understanding is that if we do add a strong name it will be considered a binary breaking change by .NET. So any library that built against 2.0 won't be...