Boshi Lian
Boshi Lian
Thanks for the PR the netstandard2.0/netstandard2.1 will be left uncovered if netcore3.1 was removed. lets defer the after the removal of netstandard2.1 and should find alternative runtime to cover netstandard2.0
.net will find closet library's target to the proj which depends on it for exmaple, libA(target net5 net6) when your app B (net6)->libA, the dist folder will copy dlls from...
netcore3.1 here is to cover the code path of netstandard2.0/2.1 when you are using net6, it will link the dll in net6 folder. while netcore3.1 is not net6, the complier...
do you have same problem without using nginx as a proxy?
> > Hello @tg123! > > I know it's possible to configure different upstream drivers when adding a new pipe, and was wondering if challenges and be configured the same...
@DamianEdwards any comments on the folder? i put it into `src\BenchmarksApps\TechEmpower\go-gin\TodosApi` as we discussed, but i do not it has something to do with `TechEmpower`
no validation or healthcheck i found go is far slower, trying to catch up .net8
theorical doable i will test to see if blz has some limit, typically, it requires hardware event (such as mouse click). but macro generally requires a click
I will check if I can make it work with macro
check out example of https://github.com/kubernetes-client/csharp/blob/master/examples/logs/Logs.cs it is `kubectl log -f` you will get the steam of log output, thus, everything from the stream is new