Hi folks, As Robert said, compilation issues were solved after bump bgpcep to use yangtools 1.2.0, but still failing at integration tests. @Robert, do you have some tip for that? thanks in advance, --

Thanks Robert for your answer. Guys, do we have any timeline for that? Once BGP is facing compilation issues at Master branch it's a block issue. thanks in advance, -- Yrineu Rodrigues Software

Hello, sorry about that, it was my oversight. This will get fixed automatically when bgpcep switches from 2.0.0-SNAPSHOT to 1.2.0, as per yangtools branching proposal. The issue will resurface at

Hi YANGTools team, The following patch introduced an issue on BGP project, can you please give the best directions to solve that? https://git.opendaylight.org/gerrit/#/c/62537/ Seems that the

A ballpark figure and the combination of 100K with 5 seconds has worked well so far :) Regards, Robert

Thanks Robert for the reply. I have actually changed the number of notifications from 100000 to 1000 in QueuedNotificationManagerTest.java. And the test got passed. However, I'm not sure how 100000

This is probably timing, e.g. not all notifications are delivered in the 5 seconds the test is waiting for. Try updating the constant there to see if it helps. Regards, Robert

Thanks for the reply, Michael. I am on branch stable/carbon, which already includes the patch mentioned. Best regards, Leo Michael Vorburger ---2017/09/27 11:09:59 AM---Tx, M. From: Michael

Tx, M. -- Michael Vorburger, Red Hat vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch Which branch are you building? Just FYI almost a year ago this

Hi there, I am trying to build yangtools on IBM Z (s390x) and have run into the QueuedNotificationManagerTest failure. It seems it is missing notifications. Anyone have any ideas? Running

Yes, they are, but that is actually a mistake. yangtools does not define interaction patterns (like RPCs), hence these classes (and OperationFailedException, RpcError) should actually live in

Ahoi yangtholians, FYI https://git.opendaylight.org/gerrit/#/c/63413/ which introduces a small new FutureRpcResults utility that should simplify dealing with FutureRpcResult was just merged into

Seems like a dlux issue; adding that list. +dlux-dev Regards, Ryan Regards, Ryan Goulding

Hi Yang Team, I am getting this issue while switching between lists on yang UI. Make sure there are 2 lists both having some default values and check boxes as checked Now switch between these

Thanks for the reminder, yangtools is GO. Regards, Robert

Hello yangtools Project Team, We need PTL or a committer to sign off for yangtools on the upcoming release of nitrogen [1]. Please do that as soon as possible, no later than 2017-09-25 9:00 AM PST as

Hi Robert, Yes you are right. I think it is not just the pattern attribute, even length attribute gets ignored, if in leaf-list. Jie Han has already raised a bug:

Hello, So leaf { type string { pattern foo; } } works, while leaf-list { type string { pattern foo; } } does not? Probably an omission. Can you file an

Thanks Jie. Yes using typedef is definitely an alternative and it works too. Hope to see this fixed in binding2. Regards, Deepthi

Hi, I think it was a missing piece, as for now, you could use typedef instead to resolve the issue : typedef my-string { type string { pattern "[0-9a-fA-F]*"; } } and this would