david g.
@mrozati thanks! I think this is a call made from AEM product code (for the context hub). I searched for "inifinity" in our code base and it doesn't exist -...
@mrozati have you by any chance logged an issue w/ Adobe support about this to validate the security concerns. I agree this seems generally overkill, but the AEM ContentHub profile...
@mrozati contexthub (including the profile store) is intended for use on aem publish. You can see this in the AEM reference implementation in we.retail. aem author doesn’t need/use context hub...
@shijuc18 have you neem able to log a Adobe Support ticket? As noted in the above thread, this appears to be spawned from OOTB Context hub. While i agree .infinity.json...
mmm - Interesting. Can I ask what your test is doing? (i assume it uses some ASC API? which one?)
@kaushalmall that would be great - I actually tried going down this path assuming cq:conf was applied to the page structure (actually the new sling prop I can’t think of...
Note that it appears AEM stores Sling CAConfig paths in `cq:conf` rather than `sling:configRef`, so we can follow suite.
@kwin IIUC you introduced the `cloud` profile, mainly for local development? (vs. just always building everything) to make that build/cycle faster for 6.5.x developers?
@kaushalmall I think a 1.5min+ query is the real issue?
The issue w/ load masking is when the load is fast, it can cause flickering.. thoughts on how this would look/work?