Meteor.autorun is not "autorunning" on Collection changes

[speigg]

Is there any reason why inserts to the "test" collection bellow do not trigger an autorun in the reactive context?

My code:

Test = new Meteor.Collection("test");

if (Meteor.isServer) {

    Test.remove({});    

    Meteor.setInterval(function() {
        console.log("Inserting Test");
        Test.insert({test: 1}); 
    }, 1000);

    Meteor.autorun(function() {

        // This section only runs once?!

        var tests = Test.find({}); 

        console.log("(" + tests.count() + ") Tests:");
        tests.forEach(function (t) {
            console.log(t);
        });

    });

}

My output:

(0) Tests:   // this came from the Meteor.autorun, but only runs the first time
Inserting Test
Inserting Test
Inserting Test
Inserting Test
Inserting Test
... etc

[speigg]

BTW, I can confirm that the Test objects are being successfully inserted into the collection. The problem seems to be with the reactive context never being invalidated when the Test collection changes.

According to the documentation, "When called in a reactive context, forEach registers dependencies on the matching documents." Meteor.autorun's job is to make a reactive context, and I've used it successfully before, so it seems that forEach is not honoring its contract of registering a dependency.

[glasser]

If you look at the docs for the deps system, you'll see that it's
documented as client-only. While the basic building blocks of deps
(Context, autorun, etc) will work on the server, Meteor doesn't provide any
reactive data sources on the server. Specifically, it's the client-side
local cache ("minimongo") that is a reactive data source; server-side
collections are not directly reactive. (You can use cursor.observe on the
server to do something similar though.)

On Fri, Nov 9, 2012 at 1:57 PM, speigg notifications@github.com wrote:

BTW, I can confirm that the Test objects are being successfully inserted
into the Collection. The problem seems to be with the reactive context
never being invalidated when the Test collection changes.

According to the documentation, "When called in a reactive context,
forEach registers dependencies on the matching documents." Meteor.autorun's
job is to make a reactive context, and I've used it successfully before, so
it seems that forEach is not honoring its contract of registering a
dependency.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/471#issuecomment-10246061.

[speigg]

Ah, that explains everything. Thanks so much.

[skeetmtp]

I stucked on the same probleme, before finding the reason here. May be it could help people to add a little message in the server console when someone is trying to call Deps function on the server ?

[dmacd]

Yes. Just wasted about two hours on this exact issue with nairy a whisper that Deps.autorun was being used it ways not intended.

[mizzao]

Took me several months of Meteor before I bumped into this too. Using Deps.autorun on the server should probably result in an error message.

Then again, declarative programming is very clean and less error prone. Couldn't we entertain the idea of having deps on the server?

[matb33]

Just ran into this today. Would also love to be able to use Deps to its full capacity on the server (such as in a setInterval)

[hexsprite]

+1 for Deps.autorun on server or at least a WARNING. I just spent the last hour trying to figure out why it wasn't re-running when I thought it should.

EDIT: re-reading apparently Deps.autorun does exist, its just missing reactive data sources. Either way it's a bit of a wart of the iso JS experience.