Florian Bernd

@cjlotz We planned to release `Elastic.Transport` 1.0 last week, but a few final pieces are still missing. I assume we will be ready in the beginning of April.

Hi there, very sorry for the delay. We recently released Elasticsearch 9 which took more time than expected. Besides that, we have a lot of PTO and maternity/paternity leave at...

We still did not release 1.0.0 of the transport library, but at this point chances of breaking interface changes are very very low. I would recommend to update to the...

UNEXPECTED seems to be the same as the existing FAILED status. Both are used to signal generic failures. Contrary to exceptions, unexpected errors should not exist with status codes as...

Mhh, what would be the benefit of using UNEXPECTED stats code vs the ZYAN_UNREACHABLE macro? IMO unreachable code should really be unreachable. If it is executed, this is clearly a...

It might be right. We are using: ```c #pragma pack(push, 1) ``` for these structs.

As a workaround we could as well "unpack" the array and add width16 width32 and width64 as separate fields. As long as there is no pointer access, the unaligned fields...

Not a dumb question at all, but probably something you should as the iced dev 😅 I never looked at the iced architecture, but yes, I assume it's largely because...

Hi @jonyadamit, Uh, this is a confusing one. The call to `b.Index(string)` does _not_ set a global index for the bulk operations in this case, but instead adds an operation...

Hi @shaneqld , thanks for reporting. I'll check! The `Percentiles` type will most likely get a custom / handcrafted implementation since usability of the nested unions is not very great...