setup script conflicts with ipython autoreload

[lallulli]

I was installing Invenio 3.2 following the quickstart guide.

At the database setup step:

./scripts/setup

I got the following error:

Usage: invenio files location [OPTIONS] NAME URI
Try "invenio files location --help" for help.

Error: Got unexpected extra arguments (disable autoreload in ipython_config.py to improve performance. /home/luca/.local/share/virtualenvs/dlt-4L5I9W9K/var/instance/data)

The reason is that, on my machine, I enabled autoreload in IPython. Every time I start IPython, I get the warning message disable autoreload in ipython_config.py to improve performance. It looks like for some reason this warning became an argument to invenio files script.

In order to resolve the problem, I commented out this line in IPython configuration:

c.InteractiveShellApp.exec_lines.append('print("Warning: disable autoreload in ipython_config.py to improve performance.")')

In this way, IPython does not produce a warning message (even if autocompletion is still enabled) and the Invenio setup script runs correctly.

[aigentic-net]

Triage note (March 2026)

This is an edge case caused by the user's IPython configuration emitting a warning message to stdout:

disable autoreload in ipython_config.py to improve performance.

The invenio files location CLI command (invoked by ./scripts/setup) interpreted this stdout output as an extra CLI argument, causing the "Got unexpected extra arguments" error.

Root cause: The user's ipython_config.py printed a warning via exec_lines, and the setup script captured all stdout (including this warning) when parsing CLI output. This is not a bug in Invenio -- it is a consequence of a user-specific IPython configuration polluting stdout during CLI execution.

Current state:

• The instance setup scripts (./scripts/setup) have been rewritten since v3.2
• InvenioRDM uses a different setup flow (invenio-cli)
• The invenio files location command itself works correctly when stdout is not polluted by external tools

Recommendation: Close as a configuration issue. Users encountering similar problems should ensure their shell/Python startup files do not emit output to stdout that could be captured by subshell commands.