New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script.reload while script is running #25419
Comments
Hey there @home-assistant/core, mind taking a look at this issue as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
Still an issue with 0.99.0dev0 System Health
Example script: dummy:
sequence:
- wait_template: "{{ is_state('binary_sensor.updater', 'on') }}"
timeout: '00:05:00'
continue_on_timeout: 'false' Traceback when reloading scripts:
Traceback when triggering the script after reloading:
|
Same here with 0.100.x:
|
Same here with 0.101.3 :
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Duplicate: #29493 |
@Santobert this is not a duplicate. It is #29493 that is a duplicate of this Issue, since this issue was created first. |
@dlashua obviously. That's what I meant. Sorry for being imprecise 🙂 |
I'm working on some new scripting features and became aware of this issue. I added new tests to check for it, and sure enough, they fail. Here is the results of one that tests the scenario described in this issue:
I'm pretty sure I know what the problem is and will address it as part of the scripting improvements. |
For "the record", there were four bugs:
The first two resulted in a delayed state update, causing the script's entity ID being added back to the state machine. (You can see this as the second That caused the first exception ( The third bug prevented that exception from being propagated to the script integration. The fourth bug meant that the script integration registered a service for a script that wasn't properly loaded. (Of course, the previous bug prevented it from knowing the script wasn't properly loaded, even if it had been "listening" for it.) That caused the second exception ( |
Hi Phil, Following your progress in the script domain closely, and am impressed. Hope scripting wil get even better. Just filed this issue, but thought a quick question would be allowed in this thread.. if not, never mind, and thanks again. |
I think that's a separate issue. |
@dlashua @Santobert @hollow @rt400 I believe this issue should be resolved now. Some other changes addressed items 1 & 2 in my description above, which should be enough to allow running scripts to be properly stopped so the reload can succeed. Can you verify the issue has been resolved for you? |
I can't reproduce the issue with 0.111.2. Thanks @pnbruckner ! |
Home Assistant release with the issue:
0.96.3
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
arch | x86_64
dev | false
docker | true
hassio | false
os_name | Linux
python_version | 3.7.4
timezone | America/Chicago
version | 0.96.3
virtualenv | false
Component/platform:
script
Description of problem:
If script.reload is called while a script (with a delay) is running, that script breaks.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
Issue #15795 was closed because it is "stale", however, it is still an issue.
The text was updated successfully, but these errors were encountered: