-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
TypeError: Cannot set property '3' of undefined #92
Comments
same here |
Same here, I am using old copy of node_modules for now. This is a problem in one of dependencies. |
You have a copy ? From: Sammy Libre [mailto:[email protected]] Same here, I am using old copy of node_modules for now. This is a problem in one of dependencies. — |
Try upgrade node-redis to 2.1.0 there is a bug fixed with argument mutation when using redis.multi. This should fix problem. Please report a result. Just run npm upgrade. |
If it does not work, please downgrade version and detect working one. Please report result here. |
Yeah, hardcode in package.json
|
Quick fix in master. Pull changes and run |
This starts, but now all my payments and fees are NAN in stats.. weird, From: Sammy Libre [mailto:[email protected]] Quick fix in master. Pull changes and run npm upgrade. — |
What is your setup? I am using slightly modified version of this pool and this fix works for me like a charm. |
node 0.10.40, node-redis 0.12.1. Delete node_modules and run npm update again. It must work. |
Also, i am running redis-server 2.8.4. |
Yes it works BUT, like I said before the fix, it messed my REDIS I think all amount and fee = nan in payments tab… any idea ? From: Sammy Libre [mailto:[email protected]] Also, i am running redis-server 2.8.4. — |
Is it fresh setup? If yes, then it's maybe ok, I can't remember actually how it goes on fresh setup without any data in redis. |
No its: Had issues with payments not going out.. Ran.. it fucked redis.. Re got the soure Applied the redis 0.12.1 Reran.. All shows as NAN From: Sammy Libre [mailto:[email protected]] Is it fresh setup? If yes, then it's maybe ok, I can't remember actually how it goes on fresh setup without any data in redis. — |
No idea. I fall into this issue by upgrading server and running npm update. I noticed bug from the title, so I downgraded redis and it works for me now. No idea, try to add additional |
Nah something else did… also the admin not working no more… this is a clean install even tried on a clean db. From: Sammy Libre [mailto:[email protected]] No idea. I fall into this issue by upgrading server and running npm update. I noticed bug from the title, so I downgraded redis and it works for me now. No idea, try to add additional hiredis parser right before redis. I am not sure I am right and even not talking bullshit, cuz I have no time to play with different setups, etc at this time. Just some guesses. Redis downgrade can't fuck your data, I am using it on my production hashinvest.net. — |
TypeError: Cannot set property '3' of undefined
at collectStats [as _onTimeout] lib/api.js:43:25
at Timer.listOnTimeout [as ontimeout] timers.js:110:15
2015-09-30 09:55:45 [master] API died, spawning replacement...
The text was updated successfully, but these errors were encountered: