-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getting error TypeError: Cannot read property 'timestamp' of null #290
Comments
What causes this? |
facing the same issue |
Hi @PratikG9 please could you provide the code snippet that is causing this error? That will be real helpful, thanks. |
Here is the architecture diagram of our cloudboost development server, To diagnose the issue we've added logs in /database-connect/realTime.js file at line 131.
from the above logs it is cleared that
@sauban , @nawazdhandala please comment |
TypeError: Cannot read property 'timestamp' of null
at /home/vagrant/apps/cloudboost/database-connect/realTime.js:131:66
at /home/vagrant/apps/cloudboost/helpers/socketQuery.js:18:17
at tryCatcher (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/util.js:26:23)
at Promise.successAdapter (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/nodeify.js:23:30)
at Promise._settlePromiseAt (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/promise.js:582:21)
at Promise._settlePromises (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues (/home/vagrant/apps/cloudboost/node_modules/bluebird/js/main/async.js:15:14)
at runCallback (timers.js:773:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate [as _immediateCallback] (timers.js:711:5)
Mon, 22 Jan 2018 14:06:36 GMT body-parser deprecated undefined extended: provide extended option at server.js:86:27
Getting this error on cloudboost, which restarts the cloudboost server and all sockets connections are lost
The text was updated successfully, but these errors were encountered: