Will Rogers
Will Rogers
I have the same problem and concluded it was a problem with fzf itself, which I reported here: https://github.com/junegunn/fzf/issues/1766
A possible alternative is to just consolidate on `Microsoft.Extensions.Logging.Abstractions` for both build targets. I see in #132 you're considering bumping the full framework build to 4.6.1. That would make the...
FWIW, LibLog did a final release for .NET Core 3.1, then archived the project and declared it deprecated: > My recommend course of action for library developers is to use...
I am honestly not sure what their versioning story is. They don't do a great job documenting each library or providing release notes. (Probably a consequence of these libraries growing...
Delayed after-thought: instead of bumping the full framework build to `net461`, you could just remove it. .NET Framework 4.6.1 and higher projects are compatible with `netstandard2.0` libraries.
FYI, support for TCP keep-alive was added to `SetSocketOption()` in .NET Core 3.0. Unfortunately, the new option names were never added to .NET Standard, so supporting TCP keep-alive on Linux...
When your program stops working, do you get an error? I have a program that crashes after some time with an access violation that has no stack trace attached to...
I am having the same problem with the resource mentioned in the referenced ticket #1442, `elbv2.k8s.aws/v1beta1.TargetGroupBinding`. I imported an existing resource using this configuration: ```hcl resource "kubernetes_manifest" "beanstalkd_targetgroupbinding" { manifest...
The delegate would be more flexible because it could conditionally change the severity based on other properties of the event. The static dictionary would be okay, too, though. With either...