sergehuber commented on PR #939:
URL: https://github.com/apache/unomi/pull/939#issuecomment-6559756976
Closing this: the CI history shows a different root cause, and it is already
fixed in master.
**What the failed runs show.** 22 failing IT jobs hit `Failed waiting for
profile in list query` between 2026-08-11 and 2026-10-26, on ES and OpenSearch,
on master and on unrelated branches. Every one logs:
```
graphql-condition-type-null typeId=userListPropertyCondition
currentTenant=itTestTenant
resolvableUnderSystemTenant=false visibleConditionTypesInContext=26..42
```
- The tenant is set, and the type is missing from the **system** tenant as
well, so the new `executeAsSystem` fallback would have returned null in all 22
cases. (`MultiTypeCacheServiceImpl.getWithInheritance` already falls back to
the system tenant synchronously; there is no inheritance warm-up.)
- The missing type is `userListPropertyCondition`, used by `findLists`
itself, so the list query matches nothing whatever the profile contains.
Writing `systemProperties.lists` directly in `AddProfileToListCommand` would
not make the test pass.
- 30 visible types = baseplugin + advanced-conditions + hover-event, i.e.
everything except the graphql bundle's own types. In the Karaf log of failing
master run 37733062661, only 29 condition types were registered, none from
graphql cxs-impl.
That is the startup-scan race fixed by UNOMI-1028 (1285eb670, #933, merged
2026-10-29). There has been no occurrence since. UNOMI-1027 is being closed as
a duplicate of it.
Separately, a real bug this PR doesn't address is filed as its own ticket:
`CDPUpdateListsAction` mutates the profile's existing `lists` object in place,
so `updateProperties` sees no change and the add/remove isn't saved for
profiles that are already in a list.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
