filterCreationErrorCallback is not a function about caterpillar

[lgbanuelos]

I believe the problem is connected with some incompatibilities among versions web3.js. You can see a similar issue at web3/web3.js#552
You can probably check the version of web3.js that is installed in your local project. If the version does not correspond with the one specified in caterpillar-core's package.json, you could try to downgrade to such version. Unfortunately, I cannot check the problem myself in this moment. But, Orlenys can later double-check my answer and come up with a fix or workaround.

Luciano

[orlenyslp]

This error TypeError: filterCreationErrorCallback occurs when the BlockChain (Ethereum) server is not running.

In the lines 23-24 in
https://github.com/orlenyslp/Caterpillar/blob/master/caterpillar-core/src/models/models.controller.ts and 12-13 in
https://github.com/orlenyslp/Caterpillar/blob/master/services-manager/src/models/models.controller.ts
you will see the provider is http://193.40.11.64:80. That is an Ethereum node that we have at the university but unfortunately, it needs to be restarted continuously after some time.

For running the demo, I would recommend you to install testrpc on your computer. You can follow the instructions here https://github.com/ethereumjs/testrpc. Then, change the provider in both files to http://localhost:8545. Be aware that it's necessary to start testrpc on your computer before running the applications. Additionally, to run caterpillar_core you need to register the services because they are used by the demo example (see the demo video). You can also specify another provider if you prefer.

By the end of the next week, I will upload a new release of Caterpillar with some updates after the demonstration in BPM 2017. From there, you will see testrpc as the default provider.

[TBP-BE]

I have the same problem.
I did like you said :i verified the web3 version. The provider is already set to http://localhost:8545/.
Still having the same error.

[a19c97]

I checked my web3 version, and it seems to match the one in package.json in caterpillar-core for v1.0.

This issues still persists - any idea how to fix it?