Bump autofix-ci/action from dd55f44df8f7cdb7a6bf74c78677eb8acd40cd0a to ff86a557419858bb967097bfc916833f5647fa8c in the actions group

[dependabot]

Bumps the actions group with 1 update: autofix-ci/action.

Closes #310

Updates autofix-ci/action from dd55f44df8f7cdb7a6bf74c78677eb8acd40cd0a to ff86a557419858bb967097bfc916833f5647fa8c

Commits

• ff86a55 Update README.md
• 2891949 fix: reuse commit-message for in-action commit (#15)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[larsoner]

Ugh on macOS:

2024-12-02 14:48:18+00 Mac-1733150552115 installd[2324]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “MNE-Python-1.8.0_0-macOS_Intel.pkg”." UserInfo={NSFilePath=./postinstall, NSURL=file:///Users/runner/work/mne-installers/mne-installers/MNE-Python-1.8.0_0-macOS_Intel.pkg#run_installation.pkg, PKInstallPackageIdentifier=tools.mne.pkg.run_installation, NSLocalizedDescription=An error occurred while running scripts from the package “MNE-Python-1.8.0_0-macOS_Intel.pkg”.} {
	    NSFilePath = "./postinstall";
	    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cMNE-Python-1.8.0_0-macOS_Intel.pkg\U201d.";
	    NSURL = "file:///Users/runner/work/mne-installers/mne-installers/MNE-Python-1.8.0_0-macOS_Intel.pkg#run_installation.pkg";
	    PKInstallPackageIdentifier = "tools.mne.pkg.run_installation";
	}

and on Linux during installation:

InvalidMatchSpec: Invalid spec 'https://conda.anaconda.org/conda-forge/linux-64/x264-1%21164.3095-h166bdaf_2.tar.bz2 md5=6c99772d483f566d59e25037fea2c4b1': Invalid version '1%21164.3095': invalid character(s)

seems like a problem with a new constructor release but I'll check by pinning...

[larsoner]

Nope, not the constructor version :(

Also I think the x264 error is probably due to some dep now requiring it, and they have exclamation points in their version numbers

https://anaconda.org/conda-forge/x264/files

Not sure how to fix either of these

[larsoner]

Seems like we're hitting conda/constructor#908, I'll see what's requiring x264 and try removing it to see if things succeed again...

[jaimergp]

Hm, I just cut a new conda-libmamba-solver today, so it might be that. Can you try pinning conda-libmamba-solver to <=24.9 in your constructor environment?

[larsoner]

@jaimergp it does look like the conda-libmamba-solver pinning fixed things! I'll push another commit to unpin just to make 100% sure

[larsoner]

Failing successfully without the pin, going to restore the pin and merge this. But hopefully knowing it was working before helps with conda/constructor#908 (maybe issue needs to move to the conda-libmamba-solver repo?)