{"action":"created","issue":{"url":"https://api.github.com/repos/mkdocs/mkdocs/issues/859","repository_url":"https://api.github.com/repos/mkdocs/mkdocs","labels_url":"https://api.github.com/repos/mkdocs/mkdocs/issues/859/labels{/name}","comments_url":"https://api.github.com/repos/mkdocs/mkdocs/issues/859/comments","events_url":"https://api.github.com/repos/mkdocs/mkdocs/issues/859/events","html_url":"https://github.com/mkdocs/mkdocs/issues/859","id":138296417,"number":859,"title":"Large search indexes can cause Lunr to freeze the page while it creates the index.","user":{"login":"sashadt","id":4966983,"avatar_url":"https://avatars.githubusercontent.com/u/4966983?v=3","gravatar_id":"","url":"https://api.github.com/users/sashadt","html_url":"https://github.com/sashadt","followers_url":"https://api.github.com/users/sashadt/followers","following_url":"https://api.github.com/users/sashadt/following{/other_user}","gists_url":"https://api.github.com/users/sashadt/gists{/gist_id}","starred_url":"https://api.github.com/users/sashadt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sashadt/subscriptions","organizations_url":"https://api.github.com/users/sashadt/orgs","repos_url":"https://api.github.com/users/sashadt/repos","events_url":"https://api.github.com/users/sashadt/events{/privacy}","received_events_url":"https://api.github.com/users/sashadt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mkdocs/mkdocs/labels/Bug","name":"Bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":45,"created_at":"2016-03-03T21:03:24Z","updated_at":"2016-06-10T00:51:27Z","closed_at":null,"body":"When using readthedocs theme, search shows \"no results\" for a few seconds while search is being performed, and then results are loaded.  However, few seconds are enough to convince the users nothing is found, and they move on.\r\n\r\nFor example see:  http://docs.datatorrent.com  Try searching for \"test\" and you will see the following for a while:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/4966983/13509416/2605d938-e140-11e5-9a6b-6ef8446212cc.png)\r\n\r\n\r\nPerhaps an indicator of search in progress can be added?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/mkdocs/mkdocs/issues/comments/225067870","html_url":"https://github.com/mkdocs/mkdocs/issues/859#issuecomment-225067870","issue_url":"https://api.github.com/repos/mkdocs/mkdocs/issues/859","id":225067870,"user":{"login":"waylan","id":78846,"avatar_url":"https://avatars.githubusercontent.com/u/78846?v=3","gravatar_id":"","url":"https://api.github.com/users/waylan","html_url":"https://github.com/waylan","followers_url":"https://api.github.com/users/waylan/followers","following_url":"https://api.github.com/users/waylan/following{/other_user}","gists_url":"https://api.github.com/users/waylan/gists{/gist_id}","starred_url":"https://api.github.com/users/waylan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/waylan/subscriptions","organizations_url":"https://api.github.com/users/waylan/orgs","repos_url":"https://api.github.com/users/waylan/repos","events_url":"https://api.github.com/users/waylan/events{/privacy}","received_events_url":"https://api.github.com/users/waylan/received_events","type":"User","site_admin":false},"created_at":"2016-06-10T00:51:27Z","updated_at":"2016-06-10T00:51:27Z","body":"After posting the testing instructions, I realized that the serve command ignores the env variable. Not sure why. I know that exporting the variable on the same line as the command sets the variable for that command only, so maybe tornado is creating a separate process which doesn't get the variable. And as far as I can tell, if a runtime is not specified it will use Node if available every time.\r\n\r\nMy latest update today added an log message which tells us which runtime is being used, which helps a little. And yes, if a runtime is not available, or if a runtime fails, then it falls back to building the index in the browser. \r\n\r\nI'm inclined to just hardcode Node as the only runtime (as it is the only one that seems to work) and many users will just get the fallback behavior as they won't have Node installed. For most small sites that should be okay (adding a webworker should still improve things). If a user has a big site or really needs a better solution, then installing Node will be the solution for them. It may turn out that those who need it may already have Node installed to begin with.\r\n\r\nIn any event, thanks for the feedback. It helps tremendously. At this point, I think I'm ready to tackle the webworker."}}
{"actor":{"display_login":"waylan"}}