dex0shubham 70dfbf151c fix(utils): write console progress to stderr instead of stdout ...

ConsoleProgressDisplay wrote every progress frame to sys.stdout. Progress
is diagnostic output, so stderr is the correct stream for it — tqdm and
most progress renderers default there for the same reason — and stdout
must stay clean for programs that carry a machine-readable protocol on
it. The stdio MCP servers put newline-delimited JSON-RPC on stdout, where
an interleaved progress bar makes a response body unparseable (#1134).

ConsoleProgressDisplay now takes an optional stream, defaulting to
stderr. The stream is resolved per write rather than captured at
construction, so a later rebinding of sys.stderr (pytest capture, for
instance) is honoured. All writes and the four bare flushes route through
it, and the emoji-capability probe now inspects that stream rather than
stdout, so a cp1252 stderr still degrades correctly.

The existing cp1252 tests in tests/deduplication/test_deduplication.py
patched sys.stdout to assert emoji auto-disabling; they now patch the
stream progress is actually written to. Their intent is unchanged.

Closes #1134 (point 1 only; the SEMANTICA_KG_PATH persistence and README
items remain with @akaszubski)

2026-08-29 13:53:48 +01:00

..

__init__.py

fix(kg): resolve 'unhashable type: Entity' in GraphAnalyzer #159

2026-01-08 17:23:31 +05:30

test_cluster_merge_coverage.py

test(deduplication): cover ClusterBuilder, MergeStrategyManager, and batch paths (#907)

2026-08-11 12:52:15 +05:00

test_deduplication.py

fix(utils): write console progress to stderr instead of stdout

2026-08-29 13:53:48 +01:00