ENV variable to disable progress bar is not working

[ArcticXWolf]

Describe the bug
This might be a regression of #5207 . The env variable HAYSTACK_PROGRESS_BARS has no effect anymore. Progress bars are still visible.

Expected behavior
The env variable hides all progress bars.

To Reproduce
Create any pipeline and execute with the env variable. The progress bars are still shown.

FAQ Check

• Have you had a look at our new FAQ page?
  Yes. But you removed the relevant question from haystack 1.0 to haystack 2.0.

System:

• OS: WSL with Ubuntu 24.04
• GPU/CPU: not relevant
• Haystack version (commit or version number): 2.9.0

[anakin87]

Hello!

The PR you are referring to is related to Haystack 1.x.

Haystack 2.x is a complete rewrite and we have not migrated this functionality.

I believe several advances have been made on tqdm in the meantime.
You should be able to control the behavior of progress bars using environment variables like TQDM_DISABLE, TQDM_MININTERVAL, ... which correspond to tqdm.tqdm parameters.

Let us know if this helps or you still encounter problems.

[ArcticXWolf]

Sadly this does not work, because those ENVs only change the defaults of TQDM and you are forcefully overwriting those with your own variables, for example here:

haystack/haystack/components/embedders/hugging_face_api_document_embedder.py

Lines 244 to 246 in d939321

	for i in tqdm(
	range(0, len(texts_to_embed), batch_size), disable=not self.progress_bar, desc="Calculating embeddings"
	):

Sure, I can add the progress_bar parameter to every single node in my pipelines, but I would rather have a way to surpress output completely.

But thanks for your help!

[anakin87]

Ah, I see...
I will label this as a feature request.

[RAMZI0TO99]

Implemented in #13093, following the invitation for a smaller replacement in #10389.

The change reads HAYSTACK_PROGRESS_BARS at execution time across the progress loops currently in core. It supports enable/disable overrides while preserving component constructor settings and serialization. Tests cover changes between runs on the same instance and synchronous/asynchronous execution, including inherited Azure and evaluator behavior.

The PR includes FAQ/docstring updates and a release note. All 145 focused tests and type checking passed; the full-suite results and a reproduced pre-existing Windows MIME-type failure are documented in the PR.

The PR is a draft pending the contributor's personal review and CLA acceptance. Upstream CI and the documentation preview currently require maintainer authorization. The AI-generation disclosure is included in the PR description.