You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Hi, all I kindly ask to implement in this V2 the logic present in V1 where the binding check the execution of a command monitoring the state of the typical to move on the expected value.
Maybe an improvement to have a flag in order to be able to activate, or not, this feature on a single typical base with a default at binding level.
Thanks
The text was updated successfully, but these errors were encountered:
I've many issues with the 2.0 binding because of missing command executed. I think should be a priority to implement the securesend (retry logic) as indicated by @FulvioSpelta @fazioa should have tried to implement it but I think we are stalled
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, all I kindly ask to implement in this V2 the logic present in V1 where the binding check the execution of a command monitoring the state of the typical to move on the expected value.
Maybe an improvement to have a flag in order to be able to activate, or not, this feature on a single typical base with a default at binding level.
Thanks
The text was updated successfully, but these errors were encountered: