Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

Adding a message for gazebo subscribe and unsubscribe to verify that it worked, i guess it would be more intuitive than the

#!python

undefined

Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

Copying @ahaidu question here:

"... However, do you know if there is a way of writing javascript publishers which take into account the gazebo master from different PC's, by changing GAZEBO_MASTER_URI? "

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

The filtered messages need the name of the model or link.

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

When using 2 different instances of gazebojs.Gazebo, publishers and subscribers all use the same one.

var gazebo = new gazebojs.Gazebo();
var gazebo2 = new gazebojs.Gazebo();

Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

since gazebojs will mostly be used as a bridge, its kind of a good idea to have sth like this

#!python

boost::shared_ptr<gazebo::msgs::Response> response
          = gazebo::transport::request(name, "heightmap_data");

in it, we actually send requests alots through gazebojs and gazebow.

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

The math is wrong trying to compute the compression ratio

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

The readme has incomplete install instructions. It could probably just point to the tutorials at http://gazebosim.org/tutorials?cat=gazebojs

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

npm install issues the following warning:

(node) child_process: options.customFds option is deprecated. Use options.stdio instead.

It is because of chilld_process code like this:

proc = spawn('node', args, { stdio: 'inherit', customFds: [0, 1, 2] });

This happens with node v5.10.1

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

functions like Play, Pause, are both in C++ and js, they are not being used in the C++, was there any particular reason for them being in both places?

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

See this question

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

It was found out if we add a little delay it always works though:

setTimeout(function (){
gazebo.publish(type, topic , msg);
console.log('\npublished!');
},10);

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

From this tutorials pull request:

"It seems like when the script runs, the messages don't get to Gazebo. Could be an issue with script engine process being destroyed too soon when run as a script."

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

~/D/c/s/gazebo-js> yarn add gazebojs
yarn add v1.22.10
...
[4/4] 🔨  Building fresh packages...
error /myproject/gazebo-js/node_modules/gazebojs: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments:
Directory: /myproject/gazebo-js/node_modules/gazebojs
Output:
fs.js:47
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:47:5
    at req_ (/myproject/gazebo-js/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/myproject/gazebo-js/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/myproject/gazebo-js/node_modules/node-gyp/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (node:internal/modules/cjs/loader:1109:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
    at Module.load (node:internal/modules/cjs/loader:989:32)
    at Function.Module._load (node:internal/modules/cjs/loader:829:14)
    at Module.require (node:internal/modules/cjs/loader:1013:19)
    at require (node:internal/modules/cjs/helpers:93:18)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Looks related: https://stackoverflow.com/questions/55921442/how-to-fix-referenceerror-primordials-is-not-defined-in-node-js

I'm on:
MacOS 11.4
Node.js 16.2.0
Gazebo 11

Original report (archived issue) by Khalid Adil (Bitbucket: Khalid Adil).

I have gazebo9 and other dependencies installed properly.

When I try to install gazebojs in a new node project after running npm init by doing:
npm install gazebojs --save

I end up with these errors:
https://cl.ly/3Z2m3q343x2Z/gazebojs_errors.png

When running node-gyp rebuild in the Node REPL, I see these errors:
https://cl.ly/pbWt/Image%202018-02-16%20at%205.53.01%20PM.png

Any idea what I may be doing wrong?

Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

I wasn't calling the unsubscribe function the right way, there is no use for this issue now, so if anyone would delete.

whenever i close gazebojs after subscribing to a topic i get this error msg

#!python

node: /usr/include/boost/smart_ptr/shared_ptr.hpp:653: typename boost::detail::sp_member_access<T>::type boost::shared_ptr<T>::operator->() const [with T = gazebo::transport::Connection; typename boost::detail::sp_member_access<T>::type = gazebo::transport::Connection*]: Assertion `px != 0' failed.
Aborted (core dumped)

to reproduce:
-run gazebo
-run node -> var gazebojs = require("gazebojs") -> var gazebo = new gazebojs.Gazebo() -> gazebo.subscribe('gazebo.msgs.Model','~/model/info',console.log)
-insert any model into gazebo if you want to see the log
-close nodejs.

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

The callback is not invoked afterwards.

This problem only happens on certain machines. To try to reproduce, setup a cemera in Gazebo and run the save_jpeg example.

NOTE:

I am not sure what causes the problem, but it looks like it can be circumvented if the gazebo instance is used in the loop at the end. It looks like the garbage collector is trying to delete the gazebo instance prematurely. The following code hides the problem:

#!python

console.log('setup a loop with 5 sec interval tick');
setInterval(function (){
  console.log('tick');
 
  // ADD THIS LINE TO HIDE THE PROBLEM
  var x = gazebo;

},1000);

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

Add a code checker similar to other projects. Examples:

• gazebo

• ignition math

• ignition transport

Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

This would be a nice feature, especially helping in throttling topics with heavy traffic.

Original report (archived issue) by Justine Lam (Bitbucket: koalaninja).

This is the error message with:

node -v v4.2.1
npm -v 1.2.18

Justines-MacBook-Pro:gz_node_inst justinelam$ npm install gazebojs
npm WARN package.json [email protected] No README.md file found!
npm http GET https://registry.npmjs.org/gazebojs
npm http 304 https://registry.npmjs.org/gazebojs
npm http GET https://registry.npmjs.org/node-gyp
npm http 304 https://registry.npmjs.org/node-gyp
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/nopt
npm http GET https://registry.npmjs.org/osenv
npm http GET https://registry.npmjs.org/npmlog
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/tar
npm http GET https://registry.npmjs.org/which
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/nopt
npm http 304 https://registry.npmjs.org/osenv
npm http 304 https://registry.npmjs.org/fstream
npm http 304 https://registry.npmjs.org/npmlog
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/semver
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/which
npm ERR! Error: No compatible version found: mkdirp@'^0.5.0'
npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.0.2","0.0.3","0.0.4","0.0.5","0.0.6","0.0.7","0.1.0","0.2.0","0.2.1","0.2.2","0.3.0","0.3.1","0.3.2","0.3.3","0.3.4","0.3.5","0.4.0","0.4.1","0.4.2","0.5.0","0.5.1"]
npm ERR! at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:685:10)
npm ERR! at /usr/local/lib/node_modules/npm/lib/cache.js:607:10
npm ERR! at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR! at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

npm ERR! System Darwin 14.5.0
npm ERR! command "mailto:[email protected]">[email protected]

npm ERR! System Darwin 14.5.0 npm ERR! command "/usr/local/Cellar/node/4.2.1/bin/node" "/usr/local/bin/npm" "install" "gazebojs" npm ERR! cwd /Users/justinelam/Sites/gazebo tutorial/gz_node_inst npm ERR! node -v v4.2.1 npm ERR! npm -v 1.2.18 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /Users/justinelam/Sites/gazebo tutorial/gz_node_inst/npm-debug.log npm ERR! not ok code 0

npm ERR! npm -v 1.2.18

Original report (archived issue) by Alexey Shaykov (Bitbucket: Alexey Shaykov).

Hi. I try to ask in gzebo forum
http://answers.gazebosim.org/question/16978/gazebojs-subscribetoimagetopic-subscribe-
rate/

but no answers. Please help.

Original report (archived issue) by Mohamd Ayman (Bitbucket: Mohamd Ayman).

The tests of the spawn works fine -already merged-, and the tests in the [topic_tests](Link https://bitbucket.org/mohamd_ayman/gazebojs/branch/test_topics) branch works fine,
when merging and replacing the 'sim.spawn' -c++- by the -js- 'spawn' , not only does the topic_tests fail, but also the spawn test itself Sometimes fail.