-
Notifications
You must be signed in to change notification settings - Fork 706
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
bug with report of tag #58
Comments
Which branch are you on? master or interval? |
I get the same error. I simply installed via the git clone command in the docs. Click on a tag, then the reports for that tag and boom. |
I install uptime with npm install node-uptime, my node.js version is 0.8.9, the mongod version is 2.2.2 |
I think this is due to the tag not yet being calculated. This bug should fix itself after 5 minutes of monitoring. I am concentrating my efforts on the next version, currently in the |
hmm, but how to install interval version? |
yep, that'll do the trick |
wow! thanks for you great work, I just installed interval version, It's impressive. two question:
|
|
V3 is released. |
when I click the report of tag, the app.js process throw error messages:
/node_modules/node-uptime/node_modules/mongoose/lib/utils.js:437
throw err;
^
TypeError: Invalid select() argument. Must be a string or object.
at Query.select (/node_modules/node-uptime/node_modules/mongoose/lib/query.js
:1075:11)
at Function.findOne (/node_modules/node-uptime/node_modules/mongoose/lib/mode
l.js:970:46)
at model.populate [as _populate](/node_modules/node-uptime/node_modules/mong
oose/lib/model.js:139:6)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:265:14)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
at next (/node_modules/node-uptime/node_modules/mongoose/lib/model.js:228:57)
The text was updated successfully, but these errors were encountered: