Martijn Laarman

Just hit this one today would love to include benchmarkdotnet tables in our docs :cry:

+1 would love to see the console version on nuget

Not a big purist but most build related tools end up on nuget (xunit console, paket, gitlink) where as chocolatey is more for desktop app / services IMO :smile:

Hi @Henr1k80 appologies for taking forever to respond to this ticket. Definitely fell through the cracks on our end. The recommended way to deal with null updates is to either...

@kbandrew the original reservations to do this OOTB by default still stands: The situations has not changed since https://docs.microsoft.com/en-us/azure/availability-zones/az-region We would definitely be open to a PR that adds support...

Awesome! It is, your copy has to be up on github (fork) though the docs here go into how to set it up: https://github.com/elastic/azure-marketplace/tree/master/build You can add a test case...

we typically recommend `nodiscard` over continuous trimming with `discard` and doing a periodic trim through `fstrim` see also: https://www.elastic.co/blog/is-your-elasticsearch-trimmed That said we should look into automatically creating a daily trim...

@amol-wadekar sorry this flew under my radar. Can you add more information to this PR, why is it good to change these defaults will they work everywhere? that kinda thing

Windows is definitely on the backlog! We need to finish work on our MSI based installer first though. Re: documentation.,good point! We are working on putting a "how to" blog...

Hi! Yes we will be opening up a repository in the coming week that will aid with this effort. We will take a more active and more importantly open approach...