It was never said that problem will be fixed in v5.3. Problem will be fixed in one of the future versions but not in v5.3.Same here. The Support said it should be fixed in 5.3 (stable). But no word about ETA yet
Just for the record... (nevermind when exactly it will be fixed)It was never said that problem will be fixed in v5.3. Problem will be fixed in one of the future versions but not in v5.3.Same here. The Support said it should be fixed in 5.3 (stable). But no word about ETA yet
ok, and why would you release a new version with "bad data" in OVPN?OVPN crash and "bad data" error are completely two different problems.
v5.3 should be released this week.
Thumbs up! Well donewe managed to fix this problem before version was released, so fix will be included in v5.3
I've tested the pre-release v5.3 (link from support) and the BAD_DATA problem was still there.we managed to fix this problem before version was released, so fix will be included in v5.3
which pre-release? last build was 30 minutes ago, so you don't have this fix yet. email again for new build.I've tested the pre-release v5.3 (link from support) and the problem was still there.we managed to fix this problem before version was released, so fix will be included in v5.3
I just updated to 5.3 and I at least in my environment I can confirm that the BAD_DATA issue seems to be fixed.nice ROS 5.3 is released!
but what about the BAD_DATA problem - is there a fix in 5.3?