Skip to content

Commit

Permalink
Fixing typos
Browse files Browse the repository at this point in the history
  • Loading branch information
anvaka committed May 19, 2015
1 parent 683d370 commit 00c8be6
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions indexUserFollowers.js
Expand Up @@ -7,7 +7,7 @@ var githubClient = require('./lib/githubClient.js')(process.env.GH_TOKEN);
var redisClient = require('./lib/redisClient.js')();
var config = require('./redisNames.js');

redisClient.get(config.BEIND_INDEXED_USER_FOLLOWERS)
redisClient.get(config.BEING_INDEXED_USER_FOLLOWERS)
.then(greet)
.then(indexUserFollowers);

Expand Down Expand Up @@ -56,6 +56,6 @@ function startNextUser() {
}

function markUser(user) {
redisClient.set(config.BEIND_INDEXED_USER_FOLLOWERS, user);
redisClient.set(config.BEING_INDEXED_USER_FOLLOWERS, user);
return user;
}
6 changes: 3 additions & 3 deletions redisNames.js
Expand Up @@ -9,18 +9,18 @@ module.exports = {
* search invariant that allows us to iterate over millions of users. This
* `created` time represents such invariant.
*/
LAST_FOLLOWER_TIME: '_lastFollowerTime',
LAST_FOLLOWER_TIME: 'lastFollowerTime2',

/**
* Where findUsersWithFollowers stores all users with followers, it has to be
* a set, since we don't want to have duplicates from overlapping searches.
*/
JOINED_AFTER: '_joinedAfter',
JOINED_AFTER: '_joinedAfterV2',

/**
* The followers crawler will pop a user from JOINED_AFTER set and temporary
* store him or here here. So that if the programm is interrupted we can
* resume without loosing current user
*/
BEIND_INDEXED_USER_FOLLOWERS: '_userBeingIndexedForFollowers'
BEING_INDEXED_USER_FOLLOWERS: '_userBeingIndexedForFollowers'
};

0 comments on commit 00c8be6

Please sign in to comment.