-
Notifications
You must be signed in to change notification settings - Fork 131
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
recommendedFor empty array with remote connection #37
Comments
I just tried this with my local version of redis and the same thing happened. I see the keys but no results are returned. |
Did you add auth? |
Sorry haven't had lots of time to maintain this. |
Feel free to help debug ;) |
I didn't add an auth, what would that entail? I've never done that before. Also where is |
Connect raccoon to your redis instance: raccoon.connect(port, url, auth); |
It's part of the quickstart |
Raccoon.prototype.connect = function(port, url, auth){ client = redis.createClient(port, url); |
What would be an example of a valid auth input? I'm pretty sure my docker container of redis is wide open. I can connect to it with |
Ah i get this when i add auth - 'Warning: Redis server does not require a password, but a password was supplied.' |
when i run
|
@guymorita Also worth noting, when i switch the function over to |
@guymorita would i be able to pick your brain for 10 minutes on gitter :) |
So it looks like other methods are working, however |
Sure, want to have a call? I'd be happy to chat. On Tue, Dec 22, 2015 at 7:20 PM, Josh Bedo [email protected] wrote:
Guy Morita T 206.240.5846 l [email protected] [email protected] LinkedIn http://www.linkedin.com/in/guymorita l Github |
Do you have a solution for this problem ? I am using auth for my redis server but recommendFor and similarUsers return a nil array. If however I put the recommend in the callback of a .like or .dislike call then it returns the array. |
I used the .liked and .disliked with a callback. then recommendFor did not work. Without a callback it seems they work. But only after the user rates again something. |
It's because the first two aren't finished yet. Hence the callbacks which
|
well it worked for one new user but then it stopped. I use the callback function after the .liked to ask for the recommend but still it does not work. I have many data into redis server imported. for example user with id = 1 has rated 300. if i use .recommendFor(1,10,... i get an empty array. Same for a new user with 2-3 ratings. and also the allLikedFor and allDislikedFor , return values but wrong values.
|
same here |
@gsmeros @clivend The recommendations only run for that user when you call .liked. This means that if you add a bunch of ratings for user 1, then user 2, then user 3. Then ask for recommendations from user 1, the array will be empty. Two ways to fix this:
|
thanks @guymorita for your time. right now, I am using version 0.2.3. my workflow is something like this:
if I look at redis I find but not something like what am I doing wrong? |
@clivend Was customer 2 one of the first entries? If so there will be no recs until you insert another .liked for that user. I'd recommend upgrading to the latest version if possible. |
actually there's no customer 2. the liked calls are these
then redis get like this
and I call
unfortunately upgrading is not easy right now |
PS can I still use callbacks with 0.2.8 or I need to refactor to promise style? EDIT I upgraded to latest version, but still got the same issue :( |
hi @guymorita , here is my last implementation based on 0.2.8
after this, redis is like `
and the recommendations for customer8Id and customer7Id are still empty arrays :( |
Same thing happened to me, I simply put code in my test that was displayed in the example. I logged into my redis server and made sure that the keys do exist. Here is the code i have.
NOTE: I'm connecting to a docker container by the docker machine ip address so its a remote connection
The text was updated successfully, but these errors were encountered: