Followup to 4f4e5342 which removed session resumption. That commit
deferred the _deactivateAllSubscriptions call on session shutdown, but
left around the immediate deletion of the merge box
state (collectionViews). This meant that if any publish callbacks were
called before the _deactivateAllSubscriptions call, they would operate
on the invalid collectionViews state.
This change ensures that the subscriptions are considered deactivated as
soon as we decide to deactivate them, even before we actually deactivate
them (and call their possibly-yielding stop callbacks).
Publishes statistics from the server to a Minimongo collection,
Facts.server. (On the server side, Facts is *not* backed by MongoDB.) By
default, this is available to all users if autopublish is on, or no
users if it is not on, but you can configure this with
Facts.setUserIdFilter.
You can add an ugly view on the stats to your app with {{> serverFacts }}.
Current stats, by package:
- mongo-livedata:
- observe-handles
- live-results-sets (when this is less than observe-handles,
cursor de-dup is helping you)
- livedata
- subscriptions
- crossbar-listeners
- sessions
The client version was running non-existent methods (because the
collection didn't exist server-side); because no callbacks were provided
to insert or update, this resulted in a Meteor._debug, but no failure.
Followup to 4f4e5342 which removed session resumption. That commit
deferred the _deactivateAllSubscriptions call on session shutdown, but
left around the immediate deletion of the merge box
state (collectionViews). This meant that if any publish callbacks were
called before the _deactivateAllSubscriptions call, they would operate
on the invalid collectionViews state.
This change ensures that the subscriptions are considered deactivated as
soon as we decide to deactivate them, even before we actually deactivate
them (and call their possibly-yielding stop callbacks).
Previously we were hashing the Unicode string, not the bytes.
This also removes a race condition. Now there is only one use of
watchSet.addFile which does not go through
watch.readAndWatchFile (adding package.js hashes to multiple watch sets
at once), and that use does correctly hash the bytes.
This fixes#1482 because EJSON.stringify clones its argument; this
change ensures that when it does that, it gets a Meteor.Error rather
than just an Object with some fields from the old Meteor.Error (which,
if the Meteor.Error was passed through a Future, will not include all
the fields we expect because they are not all enumerable).
