Firmware, GPAD_API, Version 46-48, Debug Messages like: Wire.cpp:422] beginTransmission()

Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior: Boot with out Wire.cpp messages.

Short Summary of the buggy behavior:
I did not expect to see this in the Wire.cpp ?debug? messages below in Serial Monitor during what I assume is the setup()

==================================
[ 162][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 170][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 175][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 181][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 188][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 193][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 199][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 205][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 210][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 216][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 222][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 228][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 234][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 240][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 245][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 251][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 257][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 263][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer
[ 269][E][Wire.cpp:422] beginTransmission(): could not acquire lock
[ 275][E][Wire.cpp:526] write(): NULL TX buffer pointer
[ 280][E][Wire.cpp:448] endTransmission(): NULL TX buffer pointer

To Reproduce
Steps to reproduce the behavior:

1. Load GPAD_API into Krake.
2. Watch Serial Monitor after reset

Screenshots
If applicable, add screenshots to help explain your problem.

Hardware description
Model: Krake Rev 2
Serial Number: SN0014
Other:

Start by loading GPAD_API into the Krake Rev 2 and watching the Serial Monitor after reset, as described in the reproduction steps. Use the reported Wire.cpp locations—422, 526, and 448—to investigate the repeated lock and NULL TX buffer messages during setup. Done means boot completes without these Wire.cpp messages.