Ian Young
Ian Young
> a lot changed in the past few months! No joke. I don't know what it was like before, but 6.0.x seems to check the `--driver-name` option and then completely...
Hi @mockitoguy, wondering if there is any progress on this? As well as still not having a documented link between the key and the project, I noticed while reviewing this...
I'm still hoping that we can get (a) a KEYS file documenting the keys used to sign Maven Central artifacts generated by this project and (b) signatures using a non-expired...
Turns out there is a PR already: #35.
Per https://github.com/EverythingSmartHome/everything-presence-lite/issues/304 it looks like this PR is not compatible with the ESPHome 2025.2 release.
>I don't understand what you mean. The referenced PR seems unrelated and the CI tests for this PR are passing. What is the specific issue? @nkinnan I believe the issue...
Can confirm, that other project is now compiling and running again under 2025.2. Thanks for the update.
>it'd really be great if they could actually merge this thing into dev... It really would. Or, you know, solved the problem some other way, that would be fine too....
Development build fixes the problem I was seeing too (another NPE in `jdk.internal.platform.CgroupInfo.getMountPoint()`).
I've been having a similar issue. I found a workaround for it which you might try. I'm using the 15.2.1 beta though, so this may only work for that specific...