Daniel Jour

WIP: A few more Frame tests

10

I've expanded the test suite for the `Frame` class a bit, and also corrected some (seemingly?) outdated comments in `Frame.h`. The tests still do not cover most of what a...

Second I2S on ESP32 non-working

2

### Board ESP32 NodeMCU ### Device Description (irrelevant for issue) ### Hardware Configuration (irrelevant for issue) ### Version v2.0.4 ### IDE Name Arduino IDE ### Operating System Windows 10 ###...

24 _bitsPerSample not handled in I2SClass::read()

1

### Board ESP32 NodeMCU ### Device Description Chip on "standard" dev board, doesn't matter for the issue though. ### Hardware Configuration Irrelevant for issue, but: 2 INMP441 I2S Microphones, SCK+WS+SD...

Detailed error reporting for corrupted error depth

2

I just stumbled over this (old) change of mine that helped debug an error someone on stackoverflow.com was having with sbcl. It provides a little more detailed information about which...

Allow static/dynamic library build

4

**Allow to build taskflow as a static or dynamic library and link against it.** Most of the code is not template code; so it could be compiled into a static...

`include ` is wrong, it's `include ` as used in the other parts. Variable names starting with an underscore followed by an uppercase letter are reserved for the implementation, same...

https://github.com/khvzak/bluez-tools/blob/f65321736475429316f07ee94ec0deac8e46ec4a/src/bt-obex.c#L587-L589 `device` here can be `NULL`. If it is, it causes an assertion in `device_get_address` to fail (so at least it crashes early): ~~~ (gdb) run -a "60:57:18:21:55:5B" -p "24:41:8C:A8:7D:5B"...

src/util.ts: normalizePath keep leading // on Win

3

(Hopefull, untested) fix for https://github.com/microsoft/vscode-cmake-tools/issues/2607 ## This change addresses item https://github.com/microsoft/vscode-cmake-tools/issues/2607 ### This changes path normalization on Windows The following changes are proposed: - Paths on Windows with leading `//`...

Dangling reference in SchemaValidator after garbage collection, SEGFAULT

1

https://github.com/xpol/lua-rapidjson/blob/c06b8a64a1c4173e2c38651952e0ead0372dd5e5/src/Schema.cpp#L68-L72 This creates a dangling reference if the SchemaDocument used to construct the SchemaValidator goes out of scope and is thus garbage collected. The constructor of SchemaValidator expects a **reference**...