-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Error: Doc not found in list: reywood_publish-composite.js line 210 #38
Comments
Hmmm, that is a brain buster. After reviewing the code, I can't figure out how that's possible unless there is some test code that produces a document with a mutating |
Closing for now. Feel free to re-open if a reproduction for this issue is found. |
FWIW I seem to get this a lot and can't actually pin it down somewhere. Feels as if it is related to publications getting teared down as logged in user changes, since all my publications require this.userId
|
@reywood I just updated to
|
Having the same problem since last update and was also having trouble debugging this. Any ideas why would it start complaining with the last version? @reywood
|
@reywood @martinhbramwell Guys, someone has to reopen this, the issue persists with latest available version |
+1 |
+1 |
I've found that using the selector function reactive, it is runs (because of Tracker.autorun) too often and prevents going to the next page. By being careful with assigning to those ReactiveVars only when actually changed (see below) this is prevented. I use this code (both server & client):
and then use .setIfChanged(value) to make the selector only be called (autoran) when actual new values arrive. Hope it helps! |
Thanks @jorisroling I'll look into the rate the subscription is being called, it seems like it's refreshing as new data comes from higher containers. It didn't seem to have this problem before the latest update to meteor-publish-composite |
I can confirm that this bug is also present using Meteor My stack-trace just looks a little different because I'm using
|
If someone can create a small example project that reproduces this bug, I'm happy to have a look. |
I haven't seen it again in the past month, but that doesn't say much. We've had a big spike that day I got the error; the past month was rather quiet. Seems like it's a very tough race-condition. I'll keep you posted as I see it again, but it's definitively there - please reopen. |
@reywood @filipenevola can someone please reopen it, because this still is a bug, and the exception still occurs at least once a week. I'll now start forking the project by adding more logs to when what and how this could happen. |
@SimonSimCity done. |
I'm having the same problem. Using Meteor 1.8.1 / cultofcoders:redis-oplog 2.0.2 / publish-composite 1.7.1
|
@tpmh31292 you can help us - e.g. by taking my fork of this package, import it as a custom-override and share your insight 😉 I've just added a bunch of logging data in case it fails: SimonSimCity@0f37777 I'm running this in production trying to get more details ... |
Was anything resolved here. I am seeing this under load too |
@adamgins would you be willing to include my patch and share the details? You can just create a copy of this package into the |
@SimonSimCity will do soon and get back to you |
@SimonSimCity @adamgins any new insight into this issue and a potential fix? |
@StorytellerCZ I have to admit that my focus for private and business projects has shifted away from Meteor. For this reason, I won't be able to provide any new insights without substantial effort. |
This error only appears in my Cucumber log, seems not to affect my app in any way and does not reference any code in my app. Meteor-publish-composite seems to be a dependency of some other package; I did not add it explicitly myself. Perhaps it is a accident waiting to happen :
I'd like to know if I am the only one seeing this. If you need further details, I'll be happy to oblige.
I'm running it in a Xubuntu 14.04 client guest of a KVM virtual machine.
It appears exactly four times, one immediately after the other, and only during startup of my Cucumber/Velocity testing.
The text was updated successfully, but these errors were encountered: