Alexander Galibey

It turned out, that the fix is much more complicated than it was supposed to be. The absolute offset received by `FetchOffsetsRequest` is used by (among other things) records filtering...

> How about this? https://crates.io/crates/console_error_panic_hook This is just a panic hook that forwards a message to JS native function. In theory, we could use a hook to store a message...

Created an issue in `wasmtime` https://github.com/bytecodealliance/wasmtime/issues/4054

For WASI targeted modules we can capture `stderr` and in case of `Trap` returned from WebAssembly function invocation we can report the output to the user as an error. Example:...

@vrrashkov yes, sure, go ahead. The PR is ready to merge, let's wait for release(planned for today) and then do the rebase, and hopefully, all checks will be green.

> @galibey, this issue says it's ready to merge after the release (back in November). I assume it should be merged? That was regarding another PR. The PR that corresponds...

IIUC, we will introduce a new `consumer_id` identifier (not `stream_id,` right?) which can be user-defined or random. This id will be added to 3 requests: 1. `FetchOffsetsRequest` - to read...

> should be `consumer_id` rather than `customer_id`. Should add to `ConsumerConfig` Right, thanks! I edited my comment.

Sounds good to me