You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least with Meteor versions 2.6.1 ... 2.8.1 the oplog converter will break with update operations formed/caused by Astronomy. Not exactly an issue of Astronomy, but I thought it might be worthwhile cross posting: meteor/meteor#12325
Errors such as
Error in oplog callback TypeError: Cannot read property 'a' of null
at isArrayOperator (packages/mongo/oplog_v2_converter.js:46:19)
at packages/mongo/oplog_v2_converter.js:91:11
at Array.forEach (<anonymous>)
at convertOplogDiff (packages/mongo/oplog_v2_converter.js:71:24)
at packages/mongo/oplog_v2_converter.js:109:9
at Array.forEach (<anonymous>)
at convertOplogDiff (packages/mongo/oplog_v2_converter.js:71:24)
at packages/mongo/oplog_v2_converter.js:109:9
at Array.forEach (<anonymous>)
at convertOplogDiff (packages/mongo/oplog_v2_converter.js:71:24)
at oplogV2V1Converter (packages/mongo/oplog_v2_converter.js:122:3)
at packages/mongo/oplog_observe_driver.js:607:16
at Object.Meteor._noYieldsAllowed (packages/meteor.js:785:12)
at OplogObserveDriver._handleOplogEntrySteadyOrFetching (packages/mongo/oplog_observe_driver.js:579:12)
at packages/mongo/oplog_observe_driver.js:133:20
at packages/mongo/oplog_observe_driver.js:17:9
at Object.Meteor._noYieldsAllowed (packages/meteor.js:785:12)
at packages/mongo/oplog_observe_driver.js:121:16
at packages/mongo/oplog_tailing.js:108:7
at runWithEnvironment (packages/meteor.js:1347:24)
at Object.callback (packages/meteor.js:1360:14)
at packages/ddp-server/crossbar.js:114:36
...might mean your Meteor app is failing to process the oplog entries caused by Astronomy's update operations and you clients will unknowingly operate based on stale data.
The text was updated successfully, but these errors were encountered:
At least with Meteor versions 2.6.1 ... 2.8.1 the oplog converter will break with update operations formed/caused by Astronomy. Not exactly an issue of Astronomy, but I thought it might be worthwhile cross posting: meteor/meteor#12325
Errors such as
...might mean your Meteor app is failing to process the oplog entries caused by Astronomy's update operations and you clients will unknowingly operate based on stale data.
The text was updated successfully, but these errors were encountered: