search for: rfc7159

...Are you aware that Jansson can't parse all JSON generated by qemu, and that the developers of Jansson did not seem sympathetic to patches that would make it possible? Libvirt recently reverted their use of Jansson because of its inability to deal with unsigned 64-bit numbers (and sadly, RFC7159 does not define bounds for what forms valid JSON numbers, but merely leaves it up to implementations to decide for themselves). -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org

...n't parse all JSON generated by qemu, >> and that the developers of Jansson did not seem sympathetic to >> patches that would make it possible? Libvirt recently reverted >> their use of Jansson because of its inability to deal with unsigned >> 64-bit numbers (and sadly, RFC7159 does not define bounds for what >> forms valid JSON numbers, but merely leaves it up to implementations >> to decide for themselves). > > Yes, painfully aware. Not sure what to do about it however, since the > alternative (ie. switching back to yajl) as libvirt did is not goi...

Recent functionality in jsonlite allows for streaming json to a user supplied connection object, such as a file, pipe or socket. RFC7159 prescribes json must be encoded as unicode; ISO-8859 (including latin1) is invalid. Hence I would like R to write strings as utf8, irrespective of the type of connection, platform or locale. Implementing this turns out to be unsurprisingly difficult on windows. > string <- enc2utf8("Z?r...

...t Jansson can't parse all JSON generated by qemu, and > that the developers of Jansson did not seem sympathetic to patches that > would make it possible? Libvirt recently reverted their use of Jansson > because of its inability to deal with unsigned 64-bit numbers (and > sadly, RFC7159 does not define bounds for what forms valid JSON numbers, > but merely leaves it up to implementations to decide for themselves). The problematic values that qemu outputs are, at least to my knowledge, only in the some of the messages in the QMP communication, which we do not do. We parse JSO...

...that Jansson can't parse all JSON generated by qemu, > and that the developers of Jansson did not seem sympathetic to > patches that would make it possible? Libvirt recently reverted > their use of Jansson because of its inability to deal with unsigned > 64-bit numbers (and sadly, RFC7159 does not define bounds for what > forms valid JSON numbers, but merely leaves it up to implementations > to decide for themselves). Yes, painfully aware. Not sure what to do about it however, since the alternative (ie. switching back to yajl) as libvirt did is not going to be pleasant. Cur...

I rethought this again, as I think that it's a dangerous assumption to bake qemu-img measure output into our API. This patch series runs qemu-img measure behind the scenes, but then parses the output and sums it to a single number which we print. Doing that required a bit of reworking, moving the Jansson [JSON parser] bindings from virt-builder into the common directory and a couple of other