Patrycja
Patrycja
and, well, the same happens with the corresponding f64 functions
Binaryen 118 on Alpine with GCC 13.2.1 works as well
> which might be interpreted ambiguously well, now i realised that same RFC has actual grammar rules in section 9, which say: ``` SP = = %x20 flag-list = "("...
aaand attaching a debugger to maddy reveals that it's indeed passing an empty string to both `Flags` and `PermanentFlags`: ``` (dlv) p mbox *github.com/emersion/go-imap.MailboxStatus { Name: "INBOX", ReadOnly: false, Items:...
the same issue exists with `Message.Flags` - empty string gets serialized as an empty parenthesized list element, which later breaks parsing
(if a "rename this to something else" approach is preferred in this case, let me know)
Alpine maintainer for `py3-shodan` here - we were using git commits to fetch 1.29.1, but switched to downloading PyPI tarballs instead: https://gitlab.alpinelinux.org/alpine/aports/-/commit/6dc47a68045a7b15b6ab55a7c8f0f6c1f128eb3e nonetheless, it still would be nice to have...
Any progress? Same thing happening on Android chroot
IMHO it would be simpler to just export the field in config struct and get rid of the `IgnoreFieldBy(...)` methods.
checking the SQL database itself, there indeed is at least one record in the `flags` table where the flag itself is an empty string: ``` maddy> SELECT DISTINCT flag FROM...