Skip to content
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

Large Meteor.apply calls (Account.createUser) disrupt further Meteor.apply calls and Collection insertion, etc. #555

hgezim opened this issue Dec 16, 2012 · 2 comments


Copy link

@hgezim hgezim commented Dec 16, 2012

I have a scenario where once Account.createUser is called, no other Meteor.apply or Collection.insert, et al. go through to the server.

So, here, the last call will not go to the server:

Accounts.createUser(username: "tmp_username", password: "tmp_password")
Lists.insert(name: "Untitled", datecreated: new Date())

However, removing Account.createUser, all calls make it to the server.

An important note: It seems that the calls are queued on the client because I make the above calls with Accounts.createUser, I don't see the results of List.insert. However, if I go to my source, save (with no edits), this causes Meteor to reload something which then opens the flood gates for these calls that were queued before.

Here's the demo:

  1. Click Add Task button.
  2. You should see output on the server for the user created as well as "In Meteor.method." but you won't see the Lists count increase in Mongo.
  3. If you keep clicking Add Task no output will be shown on server.
Copy link

@n1mmy n1mmy commented Jan 10, 2013

Confirmed and replicated. Thanks for the good repro. Will investigate more.


n1mmy added a commit that referenced this issue Jan 12, 2013
Copy link

@n1mmy n1mmy commented Jan 12, 2013

Fixed on devel in 3ff567e. Thanks for catching this and providing a clear reproduction case!


@n1mmy n1mmy closed this Jan 12, 2013
StorytellerCZ pushed a commit that referenced this issue Sep 18, 2021
Update mocha to the latest version 🚀
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants