search text indexing failing?

Question

search text indexing failing?

Closed this issue 11 years ago · 9 comments

"touch" should display fastclick which has "Polyfill to remove click delays on browsers with touch UIs." touch right in the description

Answer 1 · 2013-03-16T05:10:40.000Z

same with "debounce"

Answer 2 · 2013-03-16T05:13:27.000Z

Hm, maybe taking a manual request on your redis to see, if it's even indexed, would help?

Answer 3 · 2013-03-16T05:16:15.000Z

just did a new fetch, looks fine for debounce but not touch still

redis 127.0.0.1:6379> smembers word:debounce
1) "matthewmueller/debounce"
2) "jonathanong/debounce-hashed"

Answer 4 · 2013-03-16T05:22:46.000Z

That is really weird... I could only imagine some query generators failing, but that wouldn't make sense.
Did you try logging stuff?

app.get('/search/:query', function(req, res){
  // ...
  // perform search
  query = util.wordKeys(query);
  db.sunion(query, function(res) {
    console.log(query, res);
    reply(res);
  });
});

Answer 5 · 2013-03-16T05:32:34.000Z

I haven't looked into it at all yet, probably just a bug in the tokenizing thingy

Answer 6 · 2013-05-02T07:45:40.000Z

component.io is linked to from the wiki, but this issue is possibly so severe that it's better not to.
The search really seems unstable and it does not seem to have much fuzziness capabilities.
A search in the wiki-list is much more reliable, it's also easier to browse since each component
is associated with a context.
As a failing test, try searching for "onload" or "load", then do a "cmd + f" with the same query.

Answer 7 · 2013-05-02T14:36:36.000Z

ah shit it's definitely down again that's why, the site itself will remain up and GET /all is cached, damn, I'll look into this

Answer 8 · 2013-05-02T14:53:36.000Z

Github changed their api apparently

Answer 9 · 2013-05-02T15:08:42.000Z

k back online now but I still need to look into this