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
WATCHMAN_CHECKS = (
'xyxy.health.xyxy_check'
)
If I have a single check like the above, WATCHMAN_CHECKS variable is taken as a string and thus when frozenset is applied in get_checks method, the output is a set of characters and thus I get the below error in import_string method:-
{"error": 500, "message": "h doesn't look like a module path"}
This problem doesn't occur when there are multiple checks.
If I change the round brackets to square brackets, It works in every case since it takes the input of WATCHMAN_CHECKS as an array.
I think the documentation needs to be changed because this warning has to be added
The text was updated successfully, but these errors were encountered:
("foo.bar") is not a valid iterable for Python. It's same as "foo.bar". For tuples, correct syntax should be ("foo.bar", ). ["foo.bar"] is a valid list but ("foo.bar") is not a tuple. I think this has nothing with django-watchman.
Edit: It's an itarable, sorry. But it's a string and iteration will be ["f", "o", "o"...]
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
WATCHMAN_CHECKS = (
'xyxy.health.xyxy_check'
)
If I have a single check like the above, WATCHMAN_CHECKS variable is taken as a string and thus when frozenset is applied in get_checks method, the output is a set of characters and thus I get the below error in import_string method:-
{"error": 500, "message": "h doesn't look like a module path"}
This problem doesn't occur when there are multiple checks.
If I change the round brackets to square brackets, It works in every case since it takes the input of WATCHMAN_CHECKS as an array.
I think the documentation needs to be changed because this warning has to be added
The text was updated successfully, but these errors were encountered: