Tero Marttila
Tero Marttila
> The old behavior will not go away; it will just become unavailable without explicitly choosing the old behavior. I wouldn't be as concerned about this deprecation if were actually...
Using `ansible.cfg` `[default]` `force_valid_group_names = ignore` or `export ANSIBLE_TRANSFORM_INVALID_GROUP_CHARS=ignore` doesn't seem to work on Ansible 2.8.1. It still gives the deprecation warning. ``` $ ANSIBLE_TRANSFORM_INVALID_GROUP_CHARS=ignore ANSIBLE_VAULT_PASSWORD_FILE=vault-password.secret ansible-playbook --diff -i xyz-dev.ini...
Hi, `BUILD_UID=$UID docker-compose -f projects/esp8266/docker-compose.yml run --rm build` does work for me, but `BUILD_UID=$UID docker-compose -f projects/esp8266/docker-compose.yml run --rm build make menuconfig` does indeed fail with the same `ncurses` related...
This line is probably bad: https://github.com/espressif/ESP8266_RTOS_SDK/blob/c4634015d873c6cf86e118df9364c2fbc20d9a11/tools/kconfig/Makefile#L217 Consider https://www.gnu.org/software/make/manual/html_node/Phony-Targets.html > A phony target should not be a prerequisite of a real target file; if it is, its recipe will be run...
See https://github.com/qmsk/esp/pull/74
Unfortunately this project only supports the ESP8266 and ESP32 (base) targets. The esp-idf target is set in the [sdk/esp-idf/Dockerfile](https://github.com/qmsk/esp/blob/master/sdk/esp-idf/Dockerfile) Docker image, and it should be possible to change the `ESP_IDF_TARGETS`...
Fixed to keep local color state in the `ColorControlComponent` on changes, but that means that any external color updates from websocket events are ignored until the component is reloaded.
Simple fix for the `GET /api/hosts/test/objects/?object=SNMPv2-MIB::*` issue would be to just forget about the probed MIBs and match against all known objects... however the concept of MIB probing still sounds...
Show the `ps aux | grep tally` flags that you are using, particularly all of the `--spiled-*` ones. How have you connected the rPI SPI output?
> The /etc/systemd/system/qmsk-e2.service file was not installed with the package. I had to extract the file from the package and copy it separately. The package installs the `qmsk-e2-tally.service` unit in...