With dddp 0.19.0, I started seeing this error bubble up to the client:
autoupdate subscription failed: M…r.m…e.errorClass {error: 404, reason: "Subscription not found", details: undefined, message: "Subscription not found [404]", errorType: "Meteor.Error"} - referring to meteor_autoupdate_clientVersions
I found that the addition of the id_ in the websocket send bit of do_sub method (line 703 of api.py) is causing the error to now show. Prior to 0.19.0, this publication error occurred in dddp, but never showed up on the client, it seems.
Everything appears to work just fine, but the error will show up many times on the client as Meteor retries the subscription. So, with that, does this mean that dddp needs a subscription endpoint for it, or should the do_sub function silently ignore the error? I believe that meteor_autoupdate_clientVersions is a client-only local collection and isn't on the server anyway.
With dddp 0.19.0, I started seeing this error bubble up to the client:
autoupdate subscription failed: M…r.m…e.errorClass {error: 404, reason: "Subscription not found", details: undefined, message: "Subscription not found [404]", errorType: "Meteor.Error"}- referring tometeor_autoupdate_clientVersionsI found that the addition of the id_ in the websocket send bit of
do_submethod (line 703 of api.py) is causing the error to now show. Prior to 0.19.0, this publication error occurred in dddp, but never showed up on the client, it seems.Everything appears to work just fine, but the error will show up many times on the client as Meteor retries the subscription. So, with that, does this mean that dddp needs a subscription endpoint for it, or should the
do_subfunction silently ignore the error? I believe thatmeteor_autoupdate_clientVersionsis a client-only local collection and isn't on the server anyway.