Joel Höner

Yeah, was thinking the same thing when reading the patch: let's do that! Maybe `ZYAN_64_BIT_ARCH`? `ZYAN_ARCH64` would be fine as well if ARM folks hadn't decided to call their ISA...

Same issue here with a Debian Testing aarch64 guest on Apple HV. Consistently triggers multiple times a day during regular use. Sometimes I end up with a corrupted disk and...

FWIW I'm under the impression that it got a lot better with 13.4: I was easily running into ~4 crashes on any given workday previously whereas now it's more like...

> Just curious, is this omission owing to anything in specific? How addressable is it or is there something obstructing implementation? Not really, we just haven't gotten around to porting...

> Question; what's the projected LOE to add support for other key OpenTelemetry languages (e.g., .NET)? Is this something that was roadmapped prior to the donation? It very much depends...

We could simply make both `locations_start_index` and `locations_length` `repeated` fields: this would allow implementations to de-duplicate prefixes and should be even more efficient than just listing all indices all the...

Yeah, this is definitely tree-ish: we're essentially trying to encode a flamegraph tree efficiently. For optimal density we'd probably want some sort of prefix tree structure. That being said, I'm...

I don't really have a strong opinion on this. Intuitively I'd guess that this location list may make up a significant portion of message size, but these things tend to...

Inspired by the comment above and [this blog article](https://www.sainnhe.dev/post/plasma-blur/), I came up with this config to get blur on KDE X11 without any changes in wezterm: ```lua wezterm.on("window-focus-changed", function() os.execute('xdotool...

Some thoughts of mine in response to your points: > `insert` requires that all columns in the table are passed. This requirement is clearly redundant - the clickhouse handles insertion...