-
Notifications
You must be signed in to change notification settings - Fork 163
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
Increase MAX_STRING_SIZE #487
Conversation
It's too short for string length. It occurs the error when the string field in yaml files are too long.... Signed-off-by: Hyunseok Yang <hyunseok7.yang@lge.com>
The branch name suggests you created the patch using the GitHub web interface. Before creating a PR please make sure that the proposed change builds and passes all tests successfully. In this case the test checking for the possible maximum size (https://github.com/ros2/rcl/blob/b66395dc570b5c270dd0da4a1b0b121e5617a26e/rcl_yaml_param_parser/test/max_string_sz.yaml) does fail at the moment and need to be updated accordingly. |
I think i got your point. But, I've tried like these.
Then the result was like below. Anyone knows what's the problem... here?
|
As described in the docs there is a
|
really appreciate it for guidance! 👍 BTW, I tried the test as you explained... It seems gtest was all passed.
But following test was failed... and I think those are the problems.
Am I missing any other settings...? I will try several things during wait your reply. |
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com>
I don't know why it passes for you. I updated the test to match the new limit: ef6da05 With this change the PR build passes again. Thanks for the update. For all the linter tests I would suggest to double check that you went through all the steps of the install instructions. If you want to dig into why they are failing you could also look into each result file listed by |
* Increase MAX_STRING_SIZE It's too short for string length. It occurs the error when the string field in yaml files are too long.... Signed-off-by: Hyunseok Yang <hyunseok7.yang@lge.com> * update test to match increased limit Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> Signed-off-by: Zachary Michaels <zmichaels11@gmail.com>
It's too short for string length.
It occurs the error when the string field in yaml files are too long....