-
Notifications
You must be signed in to change notification settings - Fork 54
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
problem: [currency] SubsCache.ready() always returning false #1068
Comments
#1057 seems to be the last PR I can see that it was working. Looping through all subcaches ready status presents Ready for all subs.
|
I actually turned on SubsCache in #1052. |
Any ideas on what’s going on ?
…On Wed, 11 Apr 2018 at 8:48 pm, zhan ishzhanov ***@***.***> wrote:
I actually turned on SubsCache in #1052
<#1052>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1068 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJEyiqAPHuz7usqze2Mr1b1S3_CsUmdks5tnfu0gaJpZM4TP28t>
.
|
Would you like me to find out? |
Sure
…On Wed, 11 Apr 2018 at 8:51 pm, zhan ishzhanov ***@***.***> wrote:
Would you like me to find out?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1068 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJEytUFtK7qBbjdcwNZkUNQd2wo0G-Uks5tnfw5gaJpZM4TP28t>
.
|
@blockrazorbot claim |
Is upstream issue: ccorcos/meteor-subs-cache#20 this is workaround: |
I honetly think its working its just the reactiveVar isn't getting updated. |
the issue is exclusive to this route though. |
Does enabling debug bring anymore light to the issue?
|
Some subscriptions don't pass in params when they should. |
Stops a bunch of subscriptions. |
I replied in upstream issue, and we kind of have a workaround. @blockrazorbot unclaim |
@janat08 are they fixing it upstream? Or if you know how to fix it just pull request to our version. |
That doesn't resolve. |
_(SubsCache.cache).chain().values().map((x) => x.ready()).reduce((a,b) => a && b).value() Will return true value, but I don't know what this means. |
They have an issue for it, I guess they'd like to. |
You mean because you aren't sure what it's doing upstream or just because it's confusing?
Don't count on them fixing it, if you can do it just do it. |
The functional code you've posted above just checks if all caches are ready (map maps them to x.ready() and reduce checks if all of them are true, if any of them is not ready, reduce will return false, otherwise the result is true). |
That's what original code does: https://github.com/ccorcos/meteor-subs-cache/blob/07a13c0de27dcf9c81e3874edce3df6887cc02d0/src/SubsCache.js#L246 |
The only difference between the two is that the one you've posted above uses underscore/lodash chaining and respective map and reduce, while the original code uses native js map and reduce. This shouldn't make any difference though, but I'm guessing it does. |
this issue is not exclusive to the
|
Couldn't reproduce in /problems/:id. This is just for subs-cache not working. Did you mean #1051? |
@blockrazorbot label "done", resolution in #1196 |
Problem: SubsCache.ready() always returning false therefore the LOADING indicator never goes.
Solution: Unknown
The text was updated successfully, but these errors were encountered: