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
both test_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default2 and test_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default3 are registered in the FIELDS with a size and capacity much smaller that the actual size of their array. This is due to len() not returning the number of bytes but the number of codepoints.
Also should the \ in \x really be escaped in the constant definition ? If it's escaped \\xc3\\xb6 is just the string "\xc3\xb6" and not "ö".
I can create a PR with a fix but I'd like to confirm my suspicions
The text was updated successfully, but these errors were encountered:
both test_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default2 and test_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default3 are registered in the FIELDS with a size and capacity much smaller that the actual size of their array.
obviously this is wrong as you pointed out.
If it's escaped \xc3\xb6 is just the string "\xc3\xb6" and not "ö".
i think you are right about this. it does not make sense to me either.
I can create a PR with a fix but I'd like to confirm my suspicions
thank you very much, i am happy to review the PR 👍 much appreciated.
For the WString something is wrong in the generated
__description.c
file. Relevant part:both
test_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default2
andtest_msgs__msg__WStrings__DEFAULT_VALUE__wstring_value_default3
are registered in the FIELDS with a size and capacity much smaller that the actual size of their array. This is due tolen()
not returning the number of bytes but the number of codepoints.Also should the
\
in\x
really be escaped in the constant definition ? If it's escaped\\xc3\\xb6
is just the string "\xc3\xb6" and not "ö".I can create a PR with a fix but I'd like to confirm my suspicions
The text was updated successfully, but these errors were encountered: