petreeftime

Sorry, got a little busy with some other things and this fell off my immediate to do list. I think keeping it here for the time being and getting permission...

Looking at a fix in #486, but I'm considering making the output an array for `nitro-cli terminate-enclave --enclave-id ...` and `nitro-cli terminate-enclave --enclave-name ...` to make the output consistent.

However, this is an output change, so it will require a minor version bump at least, to make sure it doesn't break workflows.

@jellybobbin did you manage to figure it out? Or what exactly are you stuck ok?

This is likely an issue with BlueZ. You should try to open a ticket with them. http://www.bluez.org/contact/

This is likely an issue with BlueZ. The only thing TinyB is doing in this case is reading data from it. You should try to open a ticket with them....

Yes. I used a modified version of gdbus which I didn't get to upstream, as it needed some extra changes to not break compatibility of other programs. At the time...

`gchar*` doesn't work because BlueZ transfers binary data over DBus, which might contain zeroes. Since `gchar *` doesn't actually contain length information, the transfer function stops when it finds the...

@impala454 Awesome find. Should make it a lot easier to update TinyB, and it should be possible to remove the generated-code.c altogether if this works reliably.

I am fine with having C++ only functionality.