Lisandro Dalcin

I don't think I made any change in 3.1.2 from 3.1.1 that would explain such failure. Did you notice that old logs correspond to Open MPI 4.1.1, but new failing...

@drew-parsons Did you confirm whether this was an Open MPI regression from 4.1.1 to 4.1.2 ?

@drew-parsons What should we do with this issue? Did you report the problem upstream? Is the problem still there with the Open MPI 5.0.0rc tarball? Perhaps we disable the pack/unpack...

> would it be equal to the problem you raised at [open-mpi/ompi#8918](https://github.com/open-mpi/ompi/issues/8918) ? I'm not sure. Note however that you reported a Bus Error (alignment issues), and that's a bit...

@lxlde What's the output of the following commands? ``` which python python --version python -c "import mpi4py; print(mpi4py)" ```

Well, there you have: You are using Anaconda Python, and mpi4py is being imported from your Anaconda environment. So you are not using mpi4py from `sudo apt install python3-mpi4py`, which...

@lxlde Any update? Could you resolve your issues?

@lxlde Any update about Linux? Can I close this issue?

1. ~The envvars related to `mpi4py.futures` should be properly namespaced as `MPI4PY_FUTURES_XXX`, and the previous names should be deprecated. Let me look at this first before any attempt to further...

As you can see, I always find good excuses to not write documentation.