Comments (4)
@lorenwest Thanks for the quick reply. And yes, we do see value in this package.
I'm testing the updated dependencies now (upgraded socket.io to 1.4.6). Although the basic functionality works (such as the use of ProcessProbe) the unit tests are having issues.
In 2 of the unit tests - RouterTest.js and MonitorTest.js - the test gets 'stuck' at a certain test case, as if the test.done() isn't getting called:
RouterTest.js
./node_modules/.bin/nodeunit --reporter verbose test/RouterTest.js
RouterTest.js
✔ Router - SetUp
✔ Router - Classes
✔ The Router data model is in place
✔ Router - ConnectInternal
✔ The error was null
✔ The router found the internal probe
✔ Router - InternalSameProbe
✔ The error was null
✔ Two monitors created with the same initParams are connected to the same probe id: 85aca867-ab08-dbc4-3545-fe1ce6af3f1a
✔ Router - InternalDifferentProbe
✔ The error was null
✔ Two monitors created with the same initParams are connected to different probes
gets stuck after that.
MonitorTest.js
./node_modules/.bin/nodeunit --reporter verbose test/MonitorTest.js
MonitorTest.js
✔ ModuleLoad - Externals
✔ Config package is exported
✔ Cron package is exported
✔ Underscore package is exported
✔ Backbone package is exported
✔ ModuleLoad - Monitor
✔ The Monitor data model is in place
✔ The Monitor collection is in place
✔ ModuleLoad - Submodules
✔ The Probe submodule is in place
✔ The Connection submodule is in place
✔ The Server submodule is in place
✔ The Router submodule is in place
✔ Protected - UUID
✔ A uuid was generated
✔ It has the correct V.4 length
✔ It is unique within the test UUIDs
✔ A uuid was generated
✔ It has the correct V.4 length
✔ It is unique within the test UUIDs
................
<more test results here>
................
✔ A uuid was generated
✔ It has the correct V.4 length
✔ It is unique within the test UUIDs
✔ A uuid was generated
✔ It has the correct V.4 length
✔ It is unique within the test UUIDs
✔ Protected - Router
✔ The default router is available
✔ Writable - CanWrite
✔ No errors on Inspect probe connect
✔ Inspector connected to the test variable
✔ You can set the probe value using monitor.set()
✔ Writable - SetControl
✔ No errors on Inspect probe connect
✔ Inspector connected to the test variable
✔ You can set the probe value using monitor.set()
gets stuck after that.
All other unit tests are passing.
I'm still trying to figure out the cause of this issue.
If you are able to point me in the right direction to check it would be great.
Thanks.
from node-monitor.
Upon further investigations, found that the issue is not from the monitor classes, but actually from the old version of socket.io used as a dependency (0.9.*).
Using the latest version of socket.io (1.4.6 right now) takes away the deprecated warning, and the basic functionality appears to be working with the new version.
However, more extensive tests would be needed to verify that all the functionality is working with the new socket.io version.
Any thoughts?
from node-monitor.
This package hasn't been maintained in years. If you're getting value from it and want to upgrade dependencies, issue a pull request. I'll do a quick check and publish to NPM.
from node-monitor.
I've encountered the same warning, DeprecationWarning: process.EventEmitter is deprecated. Use require('events') instead.
, with the following set up:
Environment
socket.io 1.4.6
express 4.13.3
node 6.1.0
npm 3.8.6
Mac OS X El Capitan 10.11.5
from node-monitor.
Related Issues (20)
- Removing components HOT 2
- "Add component" needs scrollbar by default. HOT 1
- npm start monitor failed HOT 1
- Support for HTTP monitoring? HOT 1
- Test with a remote Server HOT 3
- Troubles running example scripts on Mac HOT 5
- Monitor an application from Browser HOT 2
- node-monitor crashes HOT 2
- error running monitor HOT 4
- Error watching for file (runtime.json) ENOSPC HOT 3
- Need more examples HOT 5
- What about multiple processes? How are they handled? HOT 3
- Cannot get output when running a nodejs script file HOT 1
- How can I add additional data to the monitor result? HOT 4
- getConnection() return null
- Build error on install HOT 1
- Monitor information do not getting correctly in docker container HOT 1
- Waiting for response HOT 1
- Page onInit doesn't save HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-monitor.