17 Commits

Author SHA1 Message Date
5b362590b7 fix use after free 2025-05-10 12:48:40 -04:00
c1b96370ba Attempt to base64 encode the connection payload
For some reason I am still getting this:

2025/05/10 16:37:06 Error decoding message: SGVsbG8gZGFya25lc3MgbXkgb2xkIGZyaWVuZA==::53475673624738675a4746796132356c63334d6762586b676232786b49475a79615756755a413d3daaaa
2025-05-10 12:37:39 -04:00
76d2c09c7d Use slice for init, and add better error sets.
The slice sets us avoid allocating within the init function.
This means init can't fail, and it also makes it easier to stack allocate messages (slice an array buffer, instead of creating a stack allocator).
2025-05-10 12:35:32 -04:00
9280fd095f 2025-04-30 17:00:12 -04:00
b575ad9094 2025-04-30 14:43:19 -04:00
73d0a80851 Remove bytesAsValueUnchecked
Callers can instead use std.mem.bytesAsValue directly.
2025-04-30 13:46:55 -04:00
fdd3f29fba Cleanup asBytes and test it 2025-04-30 13:46:55 -04:00
d0d0b83b57 Simplify init interface 2025-04-30 13:46:55 -04:00
bc3926bcca 2025-04-30 13:46:55 -04:00
6d4880fa6a Align the bytes instead of the struct 2025-04-30 13:46:54 -04:00
5e22c2b2ef 2025-04-30 13:46:54 -04:00
5530ed3d77 2025-04-30 13:46:54 -04:00
66ea478617 2025-04-30 13:46:54 -04:00
08954b9f3d 2025-04-30 13:46:54 -04:00
8d404a7c8d 2025-04-30 13:46:54 -04:00
18b04364df 2025-04-27 18:03:06 -04:00
cc8438448d Staring real connections 2025-04-27 18:03:06 -04:00

Diff Content Not Available