{"action":"created","issue":{"url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/278","repository_url":"https://api.github.com/repos/aldeed/meteor-tabular","labels_url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/278/labels{/name}","comments_url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/278/comments","events_url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/278/events","html_url":"https://github.com/aldeed/meteor-tabular/issues/278","id":135542332,"number":278,"title":"updateRecords Error : can't wait without a fiber","user":{"login":"prdox29","id":17416424,"avatar_url":"https://avatars.githubusercontent.com/u/17416424?v=3","gravatar_id":"","url":"https://api.github.com/users/prdox29","html_url":"https://github.com/prdox29","followers_url":"https://api.github.com/users/prdox29/followers","following_url":"https://api.github.com/users/prdox29/following{/other_user}","gists_url":"https://api.github.com/users/prdox29/gists{/gist_id}","starred_url":"https://api.github.com/users/prdox29/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prdox29/subscriptions","organizations_url":"https://api.github.com/users/prdox29/orgs","repos_url":"https://api.github.com/users/prdox29/repos","events_url":"https://api.github.com/users/prdox29/events{/privacy}","received_events_url":"https://api.github.com/users/prdox29/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-02-22T21:02:12Z","updated_at":"2016-04-07T13:52:38Z","closed_at":null,"body":" i get a recurrent error which crash my app and cause meteor to restart.\r\nWhat can i do to resolve this ?\r\n\r\nThe error comes from aldeed_tabular/server/tabular.js:118:1 :\r\n\r\nthrow new Error('Can\\'t wait without a fiber');\r\nW20160222-21:46:42.046(1)? (STDERR)     at Function.wait (C:\\Users\\Seb\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.1.10\\mt-os.windows.x86_32\\dev_bundle\\server-lib\\node_modules\\fibers\\future.js:155:9)\r\nW20160222-21:46:42.046(1)? (STDERR)                   ^\r\nW20160222-21:46:42.048(1)? (STDERR)     at Timer.listOnTimeout [as ontimeout] (timers.js:121:15)\r\nW20160222-21:46:42.043(1)? (STDERR)\r\nW20160222-21:46:42.047(1)? (STDERR)     at updateRecords (packages/aldeed_tabular/server/tabular.js:118:1)\r\n\r\nThank you for your help"},"comment":{"url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/comments/206915497","html_url":"https://github.com/aldeed/meteor-tabular/issues/278#issuecomment-206915497","issue_url":"https://api.github.com/repos/aldeed/meteor-tabular/issues/278","id":206915497,"user":{"login":"bpartridge","id":20748,"avatar_url":"https://avatars.githubusercontent.com/u/20748?v=3","gravatar_id":"","url":"https://api.github.com/users/bpartridge","html_url":"https://github.com/bpartridge","followers_url":"https://api.github.com/users/bpartridge/followers","following_url":"https://api.github.com/users/bpartridge/following{/other_user}","gists_url":"https://api.github.com/users/bpartridge/gists{/gist_id}","starred_url":"https://api.github.com/users/bpartridge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bpartridge/subscriptions","organizations_url":"https://api.github.com/users/bpartridge/orgs","repos_url":"https://api.github.com/users/bpartridge/repos","events_url":"https://api.github.com/users/bpartridge/events{/privacy}","received_events_url":"https://api.github.com/users/bpartridge/received_events","type":"User","site_admin":false},"created_at":"2016-04-07T13:52:38Z","updated_at":"2016-04-07T13:52:38Z","body":"@aldeed Also want to understand the root cause, I agree that recreating the cursor isn't optimal!\r\n\r\n@JuliaKoe We also have a background process writing to Mongo, and the error happens when it makes a change that would move a row in or out of the table.\r\n\r\nI'm thinking out loud here, but perhaps if the single Meteor instance is the only thing making changes to the collection (which is how most people use Meteor), then Meteor is running all the observeChanges within a fiber already... but if the change is coming from *oplog tailing,* then observeChanges might just be triggered from a node callback, not an actual fiber? Or perhaps the count is cached if all the changes are being made through Meteor, and that cache is invalidated if oplog entries come in?\r\n\r\nIn the meantime @JuliaKoe if you need a quick fix, you can simply clone and checkout the branch I linked into `your_app_directory_where_meteor_is_running/packages/aldeed_tabular`. Then Meteor on restart should use the local copy rather than fetching the Atmosphere-published mainline version. It's a good idea to use git submodules for this, and make sure your server deploy runs the necessary submodule checkout commands. Plenty of articles on google about cloning local packages as submodules."}}