+3
−2
+4
−3
+4
−3
+6
−5
+6
−5
Loading
Nine DistOps tests failed at suite setup against a broker that enforces TS 104-175 § 9.3.3 on registration creation: 1. idPattern exclusives (400) — D013_01_exc, D013_02_exc, D014_01_exc, D014_02_exc, D016_01_exc registered ONE exclusive CSR with entity_id_pattern=urn:ngsi-ld:Vehicle:*. § 9.3.3: "an id pattern or Entity type defining a group of entities is not supported for exclusive registrations". New fixture context-source-registration-vehicle-speed-with-batch-ops-exclusive.jsonld carries two id-specific information[] elements (one per batch entity, each with propertyNames:["speed"]) — still one registration, one endpoint, one stub, so the stub_count=1 assertions hold. The Prepare keyword gains an optional entity_id2= (appended last, callers by name) that injects the second id into $.information[1].entities[*]. 2. local-overlap (409) — D005_01_exc, D009_01_exc (and D014_01/02_exc) created the entities from vehicle-simple-different-attributes (speed, isParked2) BEFORE registering an exclusive CSR on speed. The broker shall hold no local data for exclusively-registered attributes, so creation-time conflict checking answers 409. Create from vehicle-simple-attributes-second (brandName, isParked2) instead — keeps the isParked2 the D005 assertions track, drops the local speed. § 9.3.3 explicitly permits unregistered attributes locally. 3. redirect + local entity (409) — D006_01_red, D006_02_red created the entity locally and then registered two redirect CSRs over it. For redirect, "the Context Broker itself holds no data locally in conflict to the registration". The bodies never touch the local entity (pure forward assertions), so simply drop the local create. Also: D013_01/02_exc asserted the forwarded batch body contains the FULL entities; an exclusive forward carries only the registered slice (chop-and-forward), so assert containment of the entity ids and the registered attribute instead. Verified against swBroker: D013_01_exc, D014_01_exc, D016_01_exc, D006_01_red, D006_02_red now PASS end-to-end; D013_02_exc/D014_02_exc proceed to the known Get-Request-Url-Params stub-mode crash, D005_01_exc to the name-wrapped-fragment issue, D009_01_exc to the GET-stub body/query-match issues — all separately documented.