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
I have been testing and validating the implementation of the following PR in my project.
I am using GuzzleHttp as the client, but I noticed one breaking change.
When passing true as a request parameter (e.g., for the refresh option in an index operation), it gets converted into 1 during the request, which results in an illegal_argument_exception.
The detailed error message is:
Failed to parse value [1] as only [true] or [false] are allowed.
While options like refresh can be passed as strings (since they seem to be enums), options like require_alias are booleans, which makes this change problematic.
I believe this behavior should be corrected.
How can one reproduce the bug?
specify require_alias is true
What is the expected behavior?
collectry passing true
What is your host/environment?
mac os
Do you have any screenshots?
no
Do you have any additional context?
no
The text was updated successfully, but these errors were encountered:
What is the bug?
I have been testing and validating the implementation of the following PR in my project.
I am using GuzzleHttp as the client, but I noticed one breaking change.
When passing true as a request parameter (e.g., for the refresh option in an index operation), it gets converted into 1 during the request, which results in an illegal_argument_exception.
The detailed error message is:
Failed to parse value [1] as only [true] or [false] are allowed.
While options like refresh can be passed as strings (since they seem to be enums), options like require_alias are booleans, which makes this change problematic.
I believe this behavior should be corrected.
How can one reproduce the bug?
specify require_alias is true
What is the expected behavior?
collectry passing true
What is your host/environment?
mac os
Do you have any screenshots?
no
Do you have any additional context?
no
The text was updated successfully, but these errors were encountered: