Lisandro Damián Nicanor Pérez Meyer

Hi! Currently gLabels uses QR_ECLEVEL_M for the QREncode backend. I have a use case in which I would *love* to be able to set a higher error correction level. Adding...

Can not use decoder in The Tings Stack (v3)

5

If I try to use the decoder I get: ```json { "code": 3, "message": "error:pkg/applicationserver:field_value (invalid value of field `formatters.up_formatter_parameter`)", "details": [ { "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails", "namespace": "pkg/applicationserver", "name": "field_value", "message_format":...

Misc updates

1

@SokoloffA I understand you don't have much time (if any) for this project. I am willing to put some effort on it, so here I prepared some changes I would...

Won't compile with kernel >= 6.6

1

Trying to compile against a kernel >= 6.6 brings: ``` $ LANG=C make make -C /lib/modules/6.6.15-amd64/build M=/home/lisandro/damian/ics/repos/kinarm/atemsys modules make[1]: Entering directory '/usr/src/linux-headers-6.6.15-amd64' CC [M] /home/lisandro/damian/ics/repos/kinarm/atemsys/atemsys.o /home/lisandro/damian/ics/repos/kinarm/atemsys/atemsys.c: In function 'PciDriverRemove': /home/lisandro/damian/ics/repos/kinarm/atemsys/atemsys.c:4541:5:...

Extremely dangerous read methods

5

Hi! I'm afraid the code has extremely dangerous read methods: one can not differentiate a byte properly read from a wrong status byte. Example: https://github.com/sparkfun/SparkFun_Bio_Sensor_Hub_Library/blob/master/src/SparkFun_Bio_Sensor_Hub_Library.cpp#L1263 In line 1277 if he...

In https://balena-os.github.io/leviathan/pages/Getting-Started/quickstart/quickstart-autokit.html one can read "Levaithan" instead of "Leviathan"

The documentation in [this link](https://balena-os.github.io/leviathan/pages/Getting-Started/quickstart/quickstart-autokit.html) says `Add the appropriate environment variables to the device`. Now on the web interface I see "Device variables" and inside "Device Configuration" I see yet...

A suggestion for https://balena-os.github.io/leviathan/pages/Getting-Started/quickstart/quickstart-autokit.html You could add the fact that the name of the running container will be worker and not leviathan-worker. For someone new this is a tad confusing...

Documentation: quickstart-autokit: be more verbose on variables

1

Currently https://github.com/balena-os/leviathan/blob/master/documentation/quickstart-autokit.md#provision-your-autokit-into-a-leviathan-worker-fleet in it's step 5 mentions that some variables need to be set, but do not mention exactly where they should be set. Asking @vipulgupta2048 he told me this...

Maybe the code should do a preliminary test on wether tun is available and if not, let the user know it needs to load the tun module.