> A fuller explanation is that "octet sequence cannot be decoded" stems from misuse of our foreign API internals via the normal publicly accessible API.
I just pushed a change to the callback wrapper to avoid double conversion. But I guess there's still a problem with pinning by with-alien.
> A fuller explanation is that "octet sequence cannot be decoded" stems from misuse of our foreign API internals via the normal publicly accessible API.
I just pushed a change to the callback wrapper to avoid double conversion. But I guess there's still a problem with pinning by with-alien.