Errors and unexpected behaviour you may hit while running your Cloud Function locally with make run — before Docker or the Document Store come into play.

make run fails with a .venv error

If make run returns an error mentioning installable modules or the venv, install the matching python3-venv package and rebuild:

sudo apt update
sudo apt install python3.12-venv

# Remove the broken venv and try again
rm -rf venv
make run

If you're using a different Python version, replace python3.12-venv accordingly.

make run fails with ERROR: Could not find a version that satisfies the requirement ixoncdkingress==1.0.0

This means your active Python version is older than what ixoncdkingress 1.x requires (Python 3.12+).

Check with python --version. If it reports anything below 3.12, install Python 3.12 (Windows users: inside WSL — see Prerequisites for Microsoft Windows systems). Consider pyenv if you need multiple versions side-by-side.

After installing the correct Python, delete the existing venv folder before retrying — otherwise make run will keep using the old version:

rm -rf venv
make run

Auto-reload not picking up changes

The Ingress reloads function code on save. If your edits aren't taking effect:

• Confirm the file you edited is inside the functions/ directory (or the directory pointed at by CBC_PATH).
• Confirm the function you're editing is decorated with @FunctionContext.expose.
• If you've added a new file alongside example.py, make sure there's an empty __init__.py in the same folder.
• As a last resort, stop and restart make run.