Duplicate events

[jdgjsag67251]

It appears that, on the client, added and changed (and maybe others?) events get called multiple times for clients that originated the request when using observe events like so:

Collection.find().observe({
    changed() {
        console.log("Changed");
    }
});

Collection.update("7pmHJGvoT5CESRrwv", { $set: { someField: true } });

// Changed 3x

Similarly to #51 this causes flickers for updates. But we also have code that calls observe directly that assumes that added is only called once per insert.

Sequential WebSocket messages

{
    "msg": "method",
    "id": "1",
    "method": "/collection/update",
    "params": [
        {
            "_id": "7pmHJGvoT5CESRrwv"
        },
        {
            "$set": {
                "someField": true
            }
        },
        {}
    ]
}

{  "msg": "updated", "methods": ["1"] }

{  "msg": "result", "id": "1"  }

{
    "msg": "changed",
    "collection": "collection",
    "id": "7pmHJGvoT5CESRrwv",
    "fields": {
        "someField": true
    }
}

cultofcoders:redis-oplog is at the top of the packages file. We are using https://github.com/radekmie/changestream-to-redis though, so maybe it inserts the changes too late? We are also using collection-hooks.

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee you issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[jdgjsag67251]

I figured it out! For anyone else having this issue, you do have to have pushToRedis set to true even if you use an external publisher