-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.1.0 #388
Release 2.1.0 #388
Conversation
@StorytellerCZ, Where I can see error logs of tests in GitHub Actions? |
You will need to go to the origin repository: https://github.com/Meteor-Community-Packages/redis-oplog/actions |
Hmmm, this is strange error, because we don't call collection2
|
That should not be the case, but looks like we will have to make a review of them to fix this. |
The error message says it happens in the |
No, that is just collection2 reporting that after it has filtered out stuff that was not in the schema, there was nothing left. collection2 is just the reporter here. |
But we didn't attach |
To be more precise we did not attach a schema. We need to find where |
This is from the |
#363 might be worth looking at, though I don't personally need it; what I'd personally like in this space is a nicer solution to #357. (My biggest issue remains #365 though; I still don't have a fix other than restarting my Meteor processes every week or so.) |
Running with vent only mode would definitely be useful to some. Probably a bit of rework around the tests (or just rerun a subset of tests with this configuration option turned on). I also don't think it effectively solves #365. Correct me if I'm wrong but I do believe the goal with this release need to be support for 2.6+ before adding additional features. |
Just a heads up PR here that fixes this. |
remove socialize:user-presence since it's not used anywhere
Published cultofcoders:redis-oplog@2.1.0 |
@edemaine I posted a code tweak that may help. We had the same issue, and decided that a little extra DB load is justified to keep the server cache in sync. This may not be the case for some applications, but it works well for us so far. Here are some additional comments/context: #291 (comment) |
Includes PRs #371 and #387. I have also fixed running of tests by migrating them to GH Actions. One test is currently failing @maxpain @megawebmaster can you please take a look.
Also I'm open to get one or two more PRs into this release. Which ones would you like?