@Phil Ewels seeing an error on conda with Multiqc 1.33

>     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/multiqc/plots/plot.py", line 616, in initialize
    >       raise ValueError("No datasets to plot")
    >   ValueError: No datasets to plot
    >
    >   During handling of the above exception, another exception occurred:
    >
    >   Traceback (most recent call last):
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/bin/multiqc", line 10, in <module>
    >       sys.exit(run_multiqc())
    >                ~~~~~~~~~~~^^
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/multiqc/__main__.py", line 21, in run_multiqc
    >       multiqc.run_cli(prog_name="multiqc")
    >       ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/click/core.py", line 1485, in __call__
    >       return self.main(*args, **kwargs)
    >              ~~~~~~~~~^^^^^^^^^^^^^^^^^
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/rich_click/rich_command.py", line 216, in main
    >       rv = self.invoke(ctx)
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/click/core.py", line 1269, in invoke
    >       return ctx.invoke(self.callback, **ctx.params)
    >              ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/click/core.py", line 824, in invoke
    >       return callback(*args, **kwargs)
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/multiqc/multiqc.py", line 545, in run_cli
    >       result = run(*analysis_dir, clean_up=clean_up, cfg=cfg, interactive=False)
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/multiqc/multiqc.py", line 629, in run
    >       exec_modules(mod_dicts_in_order)
    >       ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
    >     File "/home/runner/tests/9ad412e6decd807638e570f612b7100a/work/conda/env-46cb47fa7c654ddf59f1c6f0e7915e5e/lib/python3.14/site-packages/multiqc/core/exec_modules.py", line 157, in exec_modules
    >       rich.panel.Panel(
    >       ^^^^^^^^^^
    >   AttributeError: module 'rich' has no attribute 'panel'. Did you mean: 'pager'?

And seeing the same thing when I update to multiQC 1.34 with docker. Any idea?

It's conda dependency drift

I did noticed it only with conda on 1.33, but with docker as well with 1.34

We fixed the issue for the next release. Anyone encountering this has other issues with their multiqc inputs triggering an error- the issue is with the exception handling.

Yeah, we noticed it fails only on tiny data, not on megatests

Probably worth figuring out what the underlying issue is anyway, I suspect multiqc has been too shy about yelling about stuff

My guess not enough data or wrongly managed null values by the tools that fed it to multiQC