EstablishSubscription does not work #35
Comments
timho93
changed the title
|
Update: I do not know why but suddenly, without changing the code, it is working. Now the callbacks are holded like this: But in the next second its the same problem again |
|
Tim, I put an explanation of what is happening with Cheers, Einar |
|
I working with CSR1000v and IOS XE 16.8.1 |
|
Like promised the failure case: |
|
Tim, It looks like what is happening is that the first push of data is happening immediately when the subscription is established, and before the subscriptin result has been sent by the device. What I see in the logs is: Enqueuing
|
|
But in the first and working case this is also the case (timestamp show nearly same arriving time). But thank you for yout help. Do you have any clue to workaround temporary ? It would be nice because i am working with this library while my master-thesis. Thank you |
|
Tim, In both cases your callback should start receiving data once the subscription result is received. In my testing all that happens is that the first notification gets dropped inside Is this not happening reliably for you? Cheers, Einar |
|
Yes for sure you are absolutly right. Because of the error i closed the program an missed this fact. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
i am not sure if this is a bug or false usage but here is my code:
Following Error occurs:
I take a look at the code and printed out some parts.
The subsction_listener od YangPushListener holds the callback and errorback like this:
A notification itself holds the subscription id like this:
So the error occuring in callback(self, root, raw) method of YangPushListener:
seems to be a result of the following part:
'urn:uuid:7e68a11e-ecad-4ce4-8255-0483a0ce707e' != 2147483664
Regards
Tim
The text was updated successfully, but these errors were encountered: