Matthew Clark

Results 49 comments of Matthew Clark
trafficstars

[@pcopissa's solution](#issuecomment-965862944) put me on the right track, except I wanted to use the MariaDB library. 1. Download [MariaDB Connector/C 3.1.13](https://mariadb.org/download/?t=connector&p=connector-c&r=3.1.13&os=source&pkg=source-zip) and unzip 2. Inside the unzip'd folder, rename the...

I have the hardware available, just haven't had a chance to touch it (been occupied with porting my existing Teensy 4.1 code). I'll whip up a test as soon as...

Update: I just realized that the manufacturer ID of the W25Q128JV is 0xF7, but Winbond is 0xEF in this library. Regardless, setting a `#define CAPACITY MB(16)` and `flash.begin( CAPACITY );`...

> When using the SparkX board, you do need to pull up the WP/2 and HLD/3 pins (if you are using standard SPI) otherwise it will fail to communicate. Duh.

After studying [lib/mqtt/client.rb](https://github.com/njh/ruby-mqtt/blob/8968969c50b0f1add8803ac442bb77aacaeeb9d4/lib/mqtt/client.rb), I wonder if after the connection drops and it is reconnected, if it's re-using the [ssl_context](https://github.com/njh/ruby-mqtt/blob/8968969c50b0f1add8803ac442bb77aacaeeb9d4/lib/mqtt/client.rb#L175) instead of instantiating a new one? As I understand it, an...

I tried using `sudo apt-key adv --keyserver hkp://pgp.mit.edu --recv-keys 11764EE8AC24832F`, but kept getting "gpg: keyserver receive failed: Server indicated a failure." Also tried port 80, same problem. I'm sure whatever...

> No need to restart the interface just upload new configuration to interface. > > how did you do that ? Change the `ExecStart` line in the unit file to...

Apparently, this is still a problem. I have tried the `@fa-font-path` suggestions listed here, but neither seem to make any difference, and I still have the funky placeholder icons as...

Wellp, it never fails; I can spend a few hours on something like this, and as soon as I post a comment, I stumble upon a resolution within minutes. In...

_After writing all of the below, I just now noticed this issue was opened by the repo owner. Thus, as he's already aware of this, my comment isn't really helping...