Cannot keep unresolved issues alive on Github - closed automatically

Ildar_Gabdullin · December 8, 2021, 7:47pm

Sometimes I am registering issues on Github in a “frontend” section.
After some period some issue becomes “stale” - and then I receive a letter “the issues is stale” which makes to to re-check the issue and prolong it by adding a comment - so the issue is not closed automatically.

But with my issues in a “core” section the situation is uncontrollable:
after some period I receive a letter “the issue is closed automatically” - and I am not warned that this is going to happen, not emails about “stale”.

Because of this stupid reason now two my issues (and one of them is important) are closed - and they are not resolved.
These issues:

github.com/home-assistant/core

command_line sensor with templated command: inconsistency

opened 10:01PM - 31 Oct 21 UTC

closed 06:05PM - 08 Dec 21 UTC

ildar170975

integration: command_line stale

### The problem According to the docs, the `command_line` sensor supports tem…plates for the `command` option. In fact, templating support is either limited or inconsistent: - either templates do not work; - or work in a strange way. There are examples of `command-line` sensor below (see "Example YAML snippet" section). The results: ``` command: "echo hello {{ states('sun.sun') }}" ``` This command works. Output `"hello below_horizon"`, `"hello above_horizon"`. ``` command: "echo hello 123" ``` This command has no templates and works. Output `"hello 123"` ``` command: >- {% if is_state("input_boolean.test_boolean","on") -%} {%- set KEY = "m" -%} {%- else -%} {%- set KEY = "h" -%} {%- endif -%} {{ "free -" + KEY }} ``` This command does not work. ``` command: >- free - {%- if is_state("input_boolean.test_boolean","on") -%} {%- set KEY = "m" -%} {%- else -%} {%- set KEY = "h" -%} {%- endif -%} {{ KEY }} ``` This command works only if `test_boolean` == `ON`. Output is `"free -m"`. Otherwise it does not work. ``` command: >- free - {%- if is_state("input_boolean.test_boolean","on") -%} m {%- else -%} h {%- endif %} ``` This command works only if `test_boolean` == `ON`. Output is `"free -m"`. Otherwise it does not work. ``` command: "{{ 'free -h' }}" ``` This command does not work. ``` command: "{{ free -h }}" ``` This command does not work. ``` command: "echo state is {{ states('input_boolean.test_boolean') }}" ``` The command works. Output is `"state is on"`, `"state is off"`. ### What version of Home Assistant Core has the issue? core-2021.10.6 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue command_line ### Link to integration documentation on our website https://www.home-assistant.io/integrations/sensor.command_line/ ### Example YAML snippet ```yaml sensor: - platform: command_line name: "test command line" command: "echo hello {{ states('sun.sun') }}" scan_interval: 999999 - platform: command_line name: "test command line2" command: "echo hello 123" scan_interval: 999999 - platform: command_line name: "test command line3" command: >- {% if is_state("input_boolean.test_boolean","on") -%} {%- set KEY = "m" -%} {%- else -%} {%- set KEY = "h" -%} {%- endif -%} {{ "free -" + KEY }} scan_interval: 999999 - platform: command_line name: "test command line4" command: >- free - {%- if is_state("input_boolean.test_boolean","on") -%} {%- set KEY = "m" -%} {%- else -%} {%- set KEY = "h" -%} {%- endif -%} {{ KEY }} scan_interval: 999999 - platform: command_line name: "test command line5" command: >- free - {%- if is_state("input_boolean.test_boolean","on") -%} m {%- else -%} h {%- endif %} scan_interval: 999999 - platform: command_line name: "test command line6" command: "{{ 'free -h' }}" scan_interval: 999999 - platform: command_line name: "test command line7" command: "{{ free -h }}" scan_interval: 999999 - platform: command_line name: "test command line8" command: "echo state is {{ states('input_boolean.test_boolean') }}" scan_interval: 999999 ``` ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

github.com/home-assistant/core

timestamp value in template sensor: format changes when copying from device_tracker

opened 07:43PM - 19 Oct 21 UTC

closed 12:10AM - 26 Nov 21 UTC

ildar170975

stale

### The problem There is a template binary sensor with two `timestamp` attribut…es: - `attr1` = some `timestamp` attribute of some `device_tracker` entity. - `attr2` = some `timestamp` attribute of some `sensor` entity; The code: ``` binary_sensor: - platform: template sensors: test_datetime: icon_template: mdi:clock value_template: 'ok' attribute_templates: attr1: "{{state_attr('device_tracker.life360_ildar_iphone_5s','last_seen')}}" attr2: "{{state_attr('sensor.test_datetime','attr')}}" ``` The source data: ![image](https://user-images.githubusercontent.com/71872483/137978496-604f8bd7-264f-4998-9d6c-0ad873aabab4.png) ![image](https://user-images.githubusercontent.com/71872483/137978668-9f415648-9ba2-4f6d-b3f7-655616f63265.png) Both source timestamps - ISO 8601. Now the `binary_sensor`: ![image](https://user-images.githubusercontent.com/71872483/137978998-7c32161a-d856-46f7-ac94-f34a9a5671da.png) The data taken from `device_tracker` are of different format - the format is changed while copying. Why is it crucial? All my iOS devices handle timestamp data differently if these data are not of ISO 8601. ### What is version of Home Assistant Core has the issue? core-2021.10.6 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Why the hell I am not warned about “stale” state?
Can anyone re-open these issues? I cannot do it by myself.

frits1980 · December 8, 2021, 8:26pm

Shouldn’t the question be: why is nobody reacting on those issues?

Ildar_Gabdullin · December 8, 2021, 8:32pm

Go check these issues, if you find them meaningless - add an appropriate comment.

And your post was not an answer to my question.
The basic point is - why the issue-starter is not informed as it is in case of “frontend” section?

If some issue is a double of some other one or related to some other one - this info should be added to the issue; the issue may be closed with a specified reason - not just “closed automatically”. This is how it is supposed to work.

frits1980 · December 8, 2021, 8:45pm

I wasn’t saying your issues are meaningless. I hope they get some traction soon. But you are asking the wrong question I believe. The way GitHub works is not something anybody here can help you with it is just how it works. Maybe you can ask Microsoft since it’s their property I believe.
But to keep an issue open and maybe really solved any day soon I would ask why is nobody responding to those issues?

Ildar_Gabdullin · December 8, 2021, 8:51pm

Probably because there are a few of developers, much more simple testers (like me) and lots of users…
Developers cannot react in time to many issues.

Now what we have to do is “check your issues 1-2 times a week” - if it becomes “stale”, then add a comment kind of “the issue is still present in version XXXXXX”.
If some unresolved issue as closed automatically - seems I have to open a NEW SAME issue (which adds some more chaos to the issues list).

It seems that the “core” & “frontend” sections have difference in part of life-cycle, notification rules etc.

frits1980 · December 8, 2021, 8:55pm

Ok, so maybe the founder of those sections can change this? Can you find out who that is?

Ildar_Gabdullin · December 8, 2021, 9:00pm

I am not sure, it could be balloob himself…

koying · December 9, 2021, 8:27am

Just for information, that’s not a default behaviour of github. That’s a bot put in place by HA devs themselves to do that…