Alexis Hildebrandt

After digging through Ledger's tests I've understood what parts are involved to run the tests and I assume the error may surface in the Python interface, though I'm not sure...

Thanks @bremner, that's helpful. I've installed Debian 12 (stable) in a virtual machine and am unable to reproduce the issue so far. I'll look to switching to debian unstable tomorrow....

After an update to Debian unstable all ledger tests continue to succeed for me and I am unable to reproduce the reported issue. Here is how I set up my...

ℹ️ Tested with `clang` instead of `g++` and got the same results as above ☝️

Thanks for confirming, @bremner. I am now able to reproduce the issue in my Debian unstable VM 🎉 I'll have a closer look at newer versions of [utfcpp](https://github.com/nemtrif/utfcpp) and what...

If I've tested properly the issue first appears when using utfcpp [v3.2.5](https://github.com/nemtrif/utfcpp/releases/tag/v3.2.5) and disappears again when using utfcpp [v4.0.1](https://github.com/nemtrif/utfcpp/releases/tag/v4.0.1). Anyone see what could be the cause for the issue when...

That's good news, @bremner and thanks for asking the Debian maintainer of utfcpp. Any specific reason why the request is to update utfcpp in Debian to 4.0.1 instead of the...

The author of [nemtrif/utfcpp](https://github.com/nemtrif/utfcpp) suggests: > Instead of using `utf8::unchecked::utf16to8()`, use `utf8::utf16to8()`. It is safer anyway and just a bit slower. @jwiegley what was the initial motivation for using the...

@bremner if I remember correctly Debian does maintain its own patches for some of its packages. Is this still the case and would it be feasible for Debian to apply...

Hi @hosiet, welcome to the conversation and thanks for chiming in 👋🙂 Downgrading Debian's utfcpp 3.2.4 for testing and adressing any build failures with utfcpp 4.0.x later down the line...