Currently in the case of dynamic queries, end() uses the inout from API to determine extents, ignoring the actual number of blobs in container. This causes problems when the container is looped over in dynamic polling scenarios involving multiple swap chains.
Workaround is to just access first blob when processing dynamic poll data (first is the only one ever populated).
Currently in the case of dynamic queries, end() uses the inout from API to determine extents, ignoring the actual number of blobs in container. This causes problems when the container is looped over in dynamic polling scenarios involving multiple swap chains.
Workaround is to just access first blob when processing dynamic poll data (first is the only one ever populated).