Meteor 3 compatibility release

[StorytellerCZ]

Based on #59, this PR takes the next step and makes things compatible with Meteor 3.

[StorytellerCZ]

I'm wondering if mtest is compatible with Meteor 3. I see no reason not to, but the cancellation is strange.

[wreiske]

Looking forward to this! I tried getting the latest versions of both running with Meteor 3.0.2 but ran into this...

meteor add mizzao:[email protected]
mizzao:user-status with version constraint 2.0.0-beta.0 has already been added.

wreiske@Wills-MacBook-Pro bluehive-ai % meteor add mizzao:[email protected]
 => Errors while adding packages:             
                                              
While selecting package versions:
error: Conflict: Constraint mizzao:[email protected] is not satisfied by mizzao:timesync 1.0.0-beta.0.
Constraints on package "mizzao:timesync":
* mizzao:[email protected] <- top level
* mizzao:[email protected] <- mizzao:user-status 2.0.0-beta.0

[StorytellerCZ]

@wreiske I'll release a new rc for mizzao:user-status to fix this shortly.

[alisnic]

After upgrading to Meteor 3.0.4 and to timesync 1.0.0 beta, the _timeSync method is called very often:

These are stats for 7 active containers on galaxy and about 700 connections

[StorytellerCZ]

That is a concern, but at first look I don't see any change that should cause an increase. 🤔

[alisnic]

@StorytellerCZ my take is that timesync does not account that ddp methods are queued, and if timeSync calls are blocked by other method calls it will just re-issue timeSync calls. I think this whole DDP thing needs to be reverted

[jankapunkt]

@StorytellerCZ this is blocking because mtest is not meteor 3 compatible

[jankapunkt]

related zodern/mtest#2