Closed wayneparrott closed 2 years ago
On linux running install with node16 as root is a PIA with permissions issues. No such issues with node 12 & 14. Thus the zillion commits as I slowly convert from running scripts and test suite to non-root user. Grant me patience!
In the very beginning of README.md
, the node
tag still mentions the old version restriction.
@felixdivo hi, the node tag is dynamically generated from https://img.shields.io/node/v/rclnodejs. When we publish the next rclnodejs release to npmjs.com the tag should be updated with the latest range of supported node versions.
Ah okay, sorry for the bump. Neat! 😃
There is an update, saying that this crash issue (from node v13 to v16) has been fixed on node v17, but with performance regression. @wayneparrott
I verify rclnodejs v0.20.1 with node v17.4.0 and the crash is gone.
I verify rclnodejs v0.20.1 with node v17.4.0 and the crash is gone
Was this build using the original ref-napi
and related packages or did you use the forked and udpated @rclnodejs/ref-napi and related packages?
I'm running rclnodejs v0.21.0 with node v17.8.0 on aarch64 and ros2 galactic and I'm experiencing the cannot reinterpret from nullptr pointer.
I found a work around earlier but, I've since flashed the computer and now, I'm unfortunately debugging something I already solved. I think I may have reverted node to 16 and used the previously mentioned solution.
Should I be experiencing this error still?
Public API Changes none
Description
package.json
test-security-related.js
Docs
Fix #735 #717