Default Github CI failing to build wheel due to unsatisfied trait bounds

[RemingtonRohel]

I've got a project I'm working on that I am able to build locally without errors or warnings using pyo3 and maturin (specifically, maturin build --release, maturin develop --release, and maturin build --release --target x86_64-unknown-linux-gnu --zig all build). I've generated the default Github CI using maturin generate-ci --zig github, but the actions fail for all platforms and runners.

I'm confused why the github actions fail, while the local build works fine. It seems to me like maybe the pyo3 trait implementations aren't being recognized for some reason in the github workflow? Any insight is appreciated.

The actions fail at the "Build wheel" stage, with the following errors:

   Compiling dmap v0.1.1 (/home/runner/work/dmap/dmap)
error[E0277]: the trait bound `std::result::Result<Vec<IndexMap<String, DmapField>>, pyo3::PyErr>: OkWrap<_>` is not satisfied
  --> src/lib.rs:23:1
   |
23 | #[pyfunction]
   | ^^^^^^^^^^^^^ the trait `OkWrap<_>` is not implemented for `std::result::Result<Vec<IndexMap<String, DmapField>>, pyo3::PyErr>`
   |
   = help: the trait `OkWrap<T>` is implemented for `std::result::Result<T, E>`
   = note: this error originates in the attribute macro `pyfunction` (in Nightly builds, run with -Z macro-backtrace for more info)
error[E0277]: the trait bound `Vec<IndexMap<String, DmapField>>: PyFunctionArgument<'_, '_>` is not satisfied
   --> src/lib.rs:102:28
    |
102 | fn write_iqdat(mut fields: Vec<IndexMap<String, DmapField>>, outfile: PathBuf) -> PyResult<()> {
    |                            ^^^ the trait `FromPyObject<'_>` is not implemented for `Vec<IndexMap<String, DmapField>>`, which is required by `Vec<IndexMap<String, DmapField>>: PyFunctionArgument<'_, '_>`
    |
    = help: the trait `FromPyObject<'py>` is implemented for `Vec<T>`
    = note: required for `Vec<IndexMap<String, DmapField>>` to implement `FromPyObjectBound<'_, '_>`
    = note: required for `Vec<IndexMap<String, DmapField>>` to implement `PyFunctionArgument<'_, '_>`
note: required by a bound in `extract_argument`
   --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/extract_argument.rs:119:8
    |
113 | pub fn extract_argument<'a, 'py, T>(
    |        ---------------- required by a bound in this function
...
119 |     T: PyFunctionArgument<'a, 'py>,
    |        ^^^^^^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `extract_argument`

[RemingtonRohel]

I figured it out, this was due to an incompatibility between pyo3 and indexmap versions (see PyO3/pyo3#3880)