timespan | Golang package to manipulate time intervals | Date Time Utils library

We finally found the reason for this. Windows did not have the required cypher suites enabled. We have used IISCrypto to enable the corresponding cypher suites and all is ok now.

It looks like it's possible to force .NET to TLS 1.2, even though it was not enabled on the server itself.

You're wanting to works with times of day. The TimeSpan data type works with time spans (somewhat obvious to say). These are distinct concepts.

Times of day are precisely what motivated the creation of the new TimeOnly type in .NET 6. It has an IsBetween method:

Determines if a time falls within the range provided. Supports both "normal" ranges such as 10:00-12:00, and ranges that span midnight such as 23:00-01:00.

Note that IsBetween use the more sensible convention of inclusive start, exclusive end which means that you'd use 01:00 as the to moment and not accidentally exclude e.g. 00:59:17 from your period

For older versions, I'd suggest you realise that if To is less than From (e.g. it's representing a period that crosses midnight) you should check:

The command timeout is the time a query / command is allowed to execute on the database server. The timer starts when the database server receives the request. Your end-to-end round trip time may be higher than the command timeout due to network throughput or other constraints - including resource exhaustion on your web server.

Command Timeout: The time to wait (in seconds) while trying to execute a command before terminating the attempt and generating an error. Source

You could get your IsVisible values with something like this:

Well this should be an improvement to your function and also should solve the problem of jumping an extra second back. I personally do not agree with using $host and would use Clear-Host instead so the function is compatible with PowerShell ISE too but you can change that as you please.

Your policy is defined against the HttpClient not against the HttpResponseMessage.

So, the response.EnsureSuccessStatusCode() will not trigger retry even if you receive for example 428.

The HandleTransientHttpError will trigger retry if you receive 408 or 5XX status codes from the downstream system. And when the SendAsync throws the HttpRequestException

Because your exception StackTrace looks like this:

System.Net.Http.HttpRequestException: Error while copying content to a stream.

System.IO.IOException: The server returned an invalid or unrecognized response.

that's why my educated guess is that this exception is thrown by the HttpContent class while you try to read the response body (ReadAsStringAsync).

This will not trigger retry since you have defined your policy on the HttpClient.

If you want to retry in those cases as well when either the response.EnsureSuccessStatusCode() throws HRE or when the response.Content.ReadAsStringAsync() does then you have to wrap your whole http communication and response processing logic into a retry policy.

Let me show you how to do that.

First use a PolicyRegistry instead of AddPolicyHandler:

New-TimeSpan sucks. I almost always get the same error. It's reported that the issue stems from a mismatch of the culture (language) settings on your OS, the format your OS is configured to use for dates and times, and the format the DateTime object is actually in. I live in the US, use the English language, and use our standard format for dates and I still have this problems with getting New-TimeSpan to function. I've long-since given up on getting this cmdlet to work consistently.

Fortunately there's an easy workaround; just subtract two datetimes to get a System.TimeSpan instead. Works every time.

is exists any way to increase "Maximum blob size via single write operation (via Put Blob)" limit for BLOB storage?

The limits can not be change because its designed.

Based on the Microsoft document :

Azure Storage standard accounts support higher capacity limits and higher limits for ingress and egress by request. To request an increase in account limits, contact Azure Support.

As you said , here is the table describes the maximum block and blob sizes permitted by service version.

For more information please refer this Azure Blog: Run high scale workloads on Blob storage with new 200 TB object sizes

I suggest to left self-join your table to get the close time in the next day. I assume each row has zero or one child row. I don't use table but array, but the query should be the same. I code in LINQPad.