-
Notifications
You must be signed in to change notification settings - Fork 55
kwargs are empty if state_hold is used #516
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
Comments
craigbarratt
added a commit
that referenced
this issue
Aug 17, 2023
Ah - good catch. I pushed a new fix for #512 which hopefully doesn't break the hold kwargs. Still need to do more testing. |
The fix seems to work. I've deployed basic scratch kwargs tests on my instance to detect such issues early on in the future.
|
craigbarratt
added a commit
that referenced
this issue
Aug 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the recent master commit 7a81413, that was a fix for #512, kwargs of state_trigger are empty if state_hold argument is used.
This will output
{'my_kwarg': 123}
This will output
{}
Rolling back to version 1.5.0 fixes the issue.
The text was updated successfully, but these errors were encountered: