-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Issue: Boolean Values Interpreted as 1/0 in RTDS Configuration #35762
Comments
any chance you can dump an actual RTDS update? My guess is you're sending the value "true" in quotes at which point it'd be parsed as a string not a boolean |
@gordon-wang-lyft was able to reproduce this issue in a unit test and is working on a patch. |
Thanks, @alyssawilk! We are sending boolean true or false instead of string "true" and "false". We performed a dump of an actual RTDS update with a boolean value and observed the same result. We identified the root cause:
Regarding the suggestion to use "true" and "false" strings, our preference is to avoid this. Envoy's direction, as per issue #27434, is to pass correct data types directly instead of using strings for booleans and numbers. We’ve already adapted our implementation to pass in booleans directly, aligning with this approach. Since true and false are initially loaded correctly as strings, onConfigUpdate should maintain that format rather than convert them to "0" and "1". I will create a PR to address this behavior and update the ticket accordingly. |
Commit Message: Load RTDS boolean config correctly as true/false instead of 1/0 Additional Description: Currently, RTDS boolean values are being loaded as `1` or `0`, which is inconsistent with the expected `true` or `false` values. This discrepancy needs to be corrected so that boolean values are consistently loaded and represented as `true` or `false`. For further details, please refer to the [issue comment](#35762 (comment)) where this inconsistency is discussed. Risk Level: Low (to be consistent with initially loaded true/false value) Testing: new Unit Test Docs Changes: n/a Release Notes: n/a Platform Specific Features: n/a [Optional Fixes #Issue] #35762 --------- Signed-off-by: Gordon Wang <gordonwang@lyft.com>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.
Title: Issue: Boolean Values Interpreted as 1/0 in RTDS Configuration
Description:
Repro steps:
Admin and Stats Output:
Config:
Expected Behavior:
Actual Behavior:
The boolean values are being converted to 1/0 in the final layer configuration seen by the Envoy sidecar.
Additional Context:
The text was updated successfully, but these errors were encountered: