Hubert Gruszecki

- add bot issue raising when something goes wrong - improve comments in yml

When command is not handled sucessfully, print the command along with its arguments

2

Currently, if something goes wrong when command is handled, we have this print (this is example): `2024-01-22T10:04:18.487936Z ERROR server::binary::command: Command was not handled successfully, session: client ID: 4248576011, user ID:...

So we can run `iggy` on microcontrollers like `ESP32` Just TCP for start, use smoltcp, no async, can be blocking, place it in new folder like `thin-sdk` or `no_std_sdk` in...

Instead of ringbuffer or slow atomic-based global counter of used bytes.

Don't wrap in `Option`

Currently, we test only unencrypted TCP. The aim of this task is to add possibility to test encrypted TCP performance and compare it with QUIC, which is encrypted by default....

Currently, we have ubuntu + musl. I suggest checking alpine + musl and ubuntu + gnu.

Reducer number of allocations via `Vec` in messages handling from SDK/server side

1

Instead of writing: iggy/src/messages/send_messages.rs ```rust impl BytesSerializable for Message { fn as_bytes(&self) -> Vec { let mut bytes = Vec::with_capacity(self.get_size_bytes() as usize); bytes.put_u128_le(self.id); if let Some(headers) = &self.headers { let...