Benjamin Bannier
Benjamin Bannier
This was fixed by c007f1dfebb7a4239b48083efcde408d8b724d32 which first appeared with spicy-1.10.0.
This should probably be rejected since `&parse-from` only accepts bytes.
The issue seems to be due to when this event is invoked (early on). ```zeek hook Log::log_stream_policy(c: connection, id: Log::ID) { local x = c$id$orig_h; } ``` ```console $ zeek...
@JordanBarnartt, would you be able to capture and share traffic causing this behavior?
Thanks for getting back to us. This looks like it happens for QUIC traffic. I am not where such traffic is at your site, but maybe you can narrow this...
This error occurs regardless of whether the type `A` or the alias `B` are `public` or not.
Should we really introduce something like this is definitely would require extra syntax since we wouldn't have the overhead for storing and keeping the old value for every parse involving...
>Regarding the workaround, I assume get_a should be used in the &convert, right? Yepp, correct, I forgot changing that part of the example. > To be honest, instead of using...
The issue here is that we do not cleanly reject shifts beyond the width of an integer; instead this might be rejected by an assertion in SafeInt when building in...
> I'm still wondering if `