-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
Sensor raises Error when using sensor_service.list_values #5327
Comments
Introduced in #5176 |
@ytjohn sounds like a regression then since the st2 |
@armab Yes. We just ran across this Friday. This line specifically: While st2api config.py reads in api.max_page_size, this is not read in by the st2common or st2reactor. The sensor_wrapper in st2reactor appears to pass in a different config context, which doesn't include the same api options that st2common.services.datastore is expecting. |
This is still an issue (st2 3.8) Not sure why the config is not read (even when explicitly added to
fails with
Workaround
|
I have upgraded to latest Stackstorm 3.8 version and I am getting also this issue. Any fix?
My workflow_clean.py
Temporary Fix
|
Also experiencing this issue. However, I am also getting an issue where if I try to specify a 'limit' inside my sensor, I get this message:
I verified in datastore.py that 'limit' should be a valid argument, but the wrapper for list_values doesn't include the option to pass 'limit' through. sensor_wrapper.py snippet:
datastore.py snippet:
My workaround was to manually edit the sensor_wrapper.py to include all of the arguments in the upstream method in datastore.py like the following:
|
I'll be submitting a PR to fix this, but in the meantime for anyone who is experiencing this issue, I think the 'correct' fix is to include the max_page_size option in
|
SUMMARY
when the sensor tries to read from the datastore (st2KV) with
self.sensor_service.list_values(prefix'something')
, it raises this Error:STACKSTORM VERSION
v3.5.0
OS, environment, install method
using docker version
Steps to reproduce the problem
Expected Results
Actual Results
Workaround
add this code to sensor file:
Thanks!
The text was updated successfully, but these errors were encountered: