Florian Bernd
Florian Bernd
@karniemi Well, I reported that issue nearly 2 days ago. The notice in the readme is new (12 days ago).
I re-created the issue in the new repository, but judging from 4000 open issues, they seem to have just as nice community management as in this repo. So maybe in...
It's "funny" that it's still not fixed after 3 years.
Hi @MichaelDamsgaard, is there anything specific you need from the new version of Zydis (e.g. specific instruction sets that are currently not supported by the Zydis version in this repo)?...
Hi @Coldzer0 ! This is really great to see and gives me motivation to look into it again as well 🙂 If you don't mind, you could create a pull...
@Coldzer0 No worries, the PR does not have to be complete 🙂 We can work on it incrementally. I think the easiest way is using the "fork" button in the...
Hi @andersosthus, the `IndexSettings` are not completely modelled in the specification at the moment. This is how it currently looks for these 2 fields: ```ts /** @server_default 1 */ number_of_shards?:...
Some additional context [here](https://github.com/elastic/elasticsearch-specification/issues/2238). Sadly, there won't be a fix for this before the above mentioned feature is implemented.
I think the fields are all `nullable` at the moment, to make sure some of the other clients don't break if a field is not present. The Java client e.g....
Hi @recoules, good catch! This could be a potential fix, but we have to check all VSIB instructions first to be sure this doesn't break anything (aka making sure that...