Ebben Aries

> A schema-unaware collector that receives an update with `atomic = true` can optimise its storage by not individually caching paths below this prefix. i.e., if `/a/b/c` is received with...

> I'm not entirely sure I understand. > > Technically, with `atomic = true`, I think a target is allowed (based on the current loose spec) to annotate this anywhere,...

@gcsl - PTAL - this just tightens up the protocol around disallowing list keys to be included in the value payload since they are immutable in this context

@dplore - looking for review here. This has been a long standing PR - it looks like some protocol needs to be put in place across various repos to ensure...

First - thx for this @jp7677! - tested out this patch set today and see 2 noticeable issues atm 1. When using multiple outputs/monitors (extend, not clone), no matter if...

> I've reworked deconstruction and it should be good now. Could you please retest and report back? Much better now - so far so good testing a few hotplug situations...

> PPS: I've pushed a commit (can be squashed later) that detects if numeric sorting should be applied for both name and workspace ID. In your case all sort settings...

Personally I disagree with the statements in https://github.com/mbj4668/pyang/issues/577 There is no verbiage in YANG 1.0 or 1.1 stating inheritance rules which then I assume could be interpreted as there are...

> [mbj4668/pyang#577 (comment)](https://github.com/mbj4668/pyang/issues/577#issuecomment-600485288) provides their opinion that inheritance is not supported, so they agree with you Ebben. They say to properly deprecate a container or uses statement, one must deprecate...

Few comments/questions: * Components can be SW or HW components - the way this is written seems to imply its HW component specific * Since component names must be unique...