Talip7/scikit-learn-issues-multilabel huggingface dataset:
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
Thanks for raising this.

As mentioned in our [FAQ](https://github.com/IBM/actionspz/blob/main/docs/FAQ.md#is-there-a-fee-to-use-this-service-do-i-need-a-credit-card-to-sign-up), this service is provided at no cost. We do not provide direct access to our infrastructure, so we will handle the support.

My team and I are prepared to handle the maintenance workload needed to keep the ppc64le CI builds green. We’ll monitor the jobs regularly and take care of any architecture-specific or infra-related issues, so that the burden on maintainers remains minimal.

Any issues or coordination will be tracked via the [actionspz](https://github.com/IBM/actionspz) GitHub repo.

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
Nice that your team handles all of that. However, if that's the case, then another alternative would be the following setup:

- similar to conda-forge feedstock repos, have a repo per project you'd like to support, with periodic CI runs
- we can have a setup where ppc64le CI is enabled only with a commit tag, such as `[ci ppc64le]`
- whenever there are issues, you submit a PR to our repo with the fix, with the right commit tag to make sure it fixes the issue

This will ensure our CI doesn't get blocked due to ppc64le specific issues, and yet allowing to fix the issues and run CI on the main repo, only when necessary.

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
Thanks for the clarification. Just to confirm — are you suggesting that we maintain ppc64le support through our fork, or were you envisioning something else? We’ll start by making the necessary fixes in our fork and then open a PR to your repository with the [ci ppc64le] tag, so the CI runs only when needed.

Also, a quick question — do you plan to upload the ppc64le wheels to PyPI eventually, since that’s our intended end goal?

Lastly, could you please open an issue in the actions-pz repository to install our GitHub App for CI integration — similar to this one: https://github.com/IBM/actionspz/issues/21?

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
What I meant was not to have a fork and enable the CI on the fork, but to have a conda-forge feedstock like repo where its CI fetches the project and runs the build / tests on a CI. Whenever there are issues, you can be creative in solving them. I'm assuming your team would have access to such machines and therefore could test and solve the issue "locally".

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
> Lastly, could you please open an issue in the actions-pz repository to install our GitHub App for CI integration — similar to this one: https://github.com/IBM/actionspz/issues/21?

This doesn't look like the right workflow to have at all. I suggest when you open an issue for a project to enable such CI, the project to be already authorised. It feels odd for you to come and open this issue, and then ask us to open an issue on your project asking you to allow us to run on your machines. It might be useful for you to get somebody more familiar with the vibe on this part of the ecosystem in your team 😉

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
> What I meant was not to have a fork and enable the CI on the fork, but to have a conda-forge feedstock like repo where its CI fetches the project and runs the build / tests on a CI. Whenever there are issues, you can be creative in solving them. I'm assuming your team would have access to such machines and therefore could test and solve the issue "locally".

@adrinjalali, regarding the proposed “feedstock-style” separate repo for ppc64le CI builds and tests:

Could you please clarify who would be responsible for creating this repository?

Also, where is the recommended location for this repo — within the scikit-learn GitHub organization or elsewhere?

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
The idea is that you/your team create this feedstock style repository, run the CI on it, when you discover a problem you can make a PR to the main scikit-learn repository and propose a fix

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
numpy has decided not add ppc64le wheels: https://github.com/numpy/numpy/issues/22318#issuecomment-3280358883.

PyTorch has decided not to add pcc64le wheels: https://github.com/pytorch/pytorch/issues/141235#issuecomment-3161044828.

On the conda-forge side, there is a discussion about ppc64le being too costly to maintain compared to actual usage and that feedstocks maintainers should feel free to drop it: https://github.com/conda-forge/conda-forge.github.io/issues/2510

Labels: Build / CI, Needs Decision
CI: Enable GitHub Actions App for ppc64le (Power architecture) support

Hi scikit-learn team,

We’re reaching out to propose enabling CI support for the ppc64le (IBM Power) architecture in your repository, as part of a broader effort to ensure cross-platform compatibility in the scientific Python ecosystem.

We’re using a GitHub Actions (GHA)-based runner service provided and maintained by IBM to run jobs for the ppc64le architecture. This setup has already been successfully integrated into projects like:

✅ [cryptography](https://github.com/pyca/cryptography/issues/13086)

📌 [Tracking issue in NumPy](https://github.com/numpy/numpy/issues/29125)

We’d now like to propose enabling the GitHub Actions app in this repository to allow running CI jobs for ppc64le directly via GitHub Actions. This would support upstream compatibility and help ensure continued support for the Power architecture in scikit-learn.

Key Benefits:
🔒 Ephemeral and secure runners, isolated per job

🛠️ Maintained by IBM, requires no setup effort from your side

🔁 Integrates with existing GitHub Actions workflows

📚 Technical documentation and usage details:
https://github.com/IBM/actionspz/tree/main/docs

We’re happy to assist with the setup or provide any additional details the team may need.

Thanks so much!

COMMENT:
I think we can conclude that there's no action to be done at the moment from our side, since:

- numpy not releasing wheels means we won't
- we won't be adding the CI job here since we don't really have access to those machines anyway, and the CI needs to be handled by folks who have access to the hardware

However, we might accept patches which specifically fix issues for that platform, given we can test it nicely. That means IBM needs to give free access to those machines to maintainers.

With that, I think we can close this issue.

Labels: Build / CI, Needs Decision
DOC metadata docstrings generator has wrong indentation

### Describe the issue linked to the documentation

I am a maintainer of a third party package [fastcan](https://github.com/scikit-learn-contrib/fastcan).

After I update the scikit-learn version from 1.7.0 to 1.7.1, the Sphinx document generation gives the following error.

```
Parameters
---------- [docutils]
<SOME PY SCRIPT>:docstring of sklearn.utils._metadata_requests.RequestMethod.__get__.<locals>.func:38: CRITICAL: Unexpected section title.
```

The raw error log of readthedocs build can be found [here](https://app.readthedocs.org/api/v2/build/28919247.txt).

It is suspected the error is caused by the wrong indentation in `sklearn.utils._metadata_requests.py` as below.

```python
REQUESTER_DOC = """
Configure whether metadata should be requested to be passed to the ``{method}`` method.
```

### Suggest a potential alternative/fix

The correct indentation should be as below

```python
REQUESTER_DOC = """        Configure whether metadata should be requested to be \
passed to the ``{method}`` method.
```

I am not sure why the official documents of scikit-learn does not have this error. However, at least for consistence with `REQUESTER_DOC_PARAM` and `REQUESTER_DOC_RETURN`, which have 8 spaces indentation, `REQUESTER_DOC` should also have 8 spaces indentation.

COMMENT:
Thanks for reporting this, as well as directly opening a PR. Pinging @adrinjalali as he is knowledgable about metadata routing.

Labels: Documentation, Metadata Routing
⚠️ CI failed on Linux_Runs.pylatest_conda_forge_mkl (last failure: Jul 21, 2025) ⚠️

**CI failed on [Linux_Runs.pylatest_conda_forge_mkl](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=78376&view=logs&j=dde5042c-7464-5d47-9507-31bdd2ee0a3a)** (Jul 21, 2025)
- Test Collection Failure

COMMENT:
This failed with a HTTP 403 error while downloading dataset(s). I think this is a known problem that we, for now, solve by restarting/waiting for the next run.

Labels: Needs Triage
⚠️ CI failed on Linux_Runs.pylatest_conda_forge_mkl (last failure: Jul 21, 2025) ⚠️

**CI failed on [Linux_Runs.pylatest_conda_forge_mkl](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=78376&view=logs&j=dde5042c-7464-5d47-9507-31bdd2ee0a3a)** (Jul 21, 2025)
- Test Collection Failure

COMMENT:
## CI is no longer failing! ✅

[Successful run](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=78404&view=logs&j=dde5042c-7464-5d47-9507-31bdd2ee0a3a) on Jul 22, 2025

Labels: Needs Triage
⚠️ CI failed on Linux_Runs.pylatest_conda_forge_mkl (last failure: Jul 21, 2025) ⚠️

**CI failed on [Linux_Runs.pylatest_conda_forge_mkl](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=78376&view=logs&j=dde5042c-7464-5d47-9507-31bdd2ee0a3a)** (Jul 21, 2025)
- Test Collection Failure

COMMENT:
If you fail at first, try again

Labels: Needs Triage
⚠️ CI failed on Wheel builder (last failure: Jul 19, 2025) ⚠️

**CI failed on [Wheel builder](https://github.com/scikit-learn/scikit-learn/actions/runs/16384706430)** (Jul 19, 2025)

COMMENT:
## CI is no longer failing! ✅

[Successful run](https://github.com/scikit-learn/scikit-learn/actions/runs/16395867301) on Jul 20, 2025

Labels: Needs Triage
Documentation may be inaccurate regarding deprecation of `multi_class` in LogisticRegression

### Describe the issue linked to the documentation

In the documentation for `LogisticRegression`  under `multi_class`, there is a [note:](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html#:~:text=Deprecated%20since%20version%201.5%3A%20multi_class%20was%20deprecated%20in%20version%201.5%20and%20will%20be%20removed%20in%201.7.) 
"Deprecated since version 1.5: `multi_class` was deprecated in version 1.5 and will be removed in 1.7. " 

However, I think this will be removed in version 1.8, based on this PR: https://github.com/scikit-learn/scikit-learn/pull/31241


### Suggest a potential alternative/fix

Change the docs to 1.8 version - if that is correct.

COMMENT:
Good catch, thanks !

Labels: Documentation, Needs Triage
Documentation Bug: Warning about "unstable development version"

### Describe the issue linked to the documentation

When browsing the scikit-learn documentation, I selected a stable version (e.g., 1.7.0) from the versions. However, I still see the warning banner at the top of the page: **This is documentation for an unstable development version.**

This is a bit confusing, as I'm clearly viewing a stable release. 

<img width="1748" height="830" alt="Image" src="https://github.com/user-attachments/assets/3e236cbb-31cd-4e77-aead-05cdee6408c9" />

### Suggest a potential alternative/fix

_No response_

COMMENT:
Thanks for reporting this. We need to have a small investigation as to why it happens.

Labels: Bug, Documentation
Documentation Bug: Warning about "unstable development version"

### Describe the issue linked to the documentation

When browsing the scikit-learn documentation, I selected a stable version (e.g., 1.7.0) from the versions. However, I still see the warning banner at the top of the page: **This is documentation for an unstable development version.**

This is a bit confusing, as I'm clearly viewing a stable release. 

<img width="1748" height="830" alt="Image" src="https://github.com/user-attachments/assets/3e236cbb-31cd-4e77-aead-05cdee6408c9" />

### Suggest a potential alternative/fix

_No response_

COMMENT:
Related #31498 but in that case we just had to wait a bit for a deployment job to run, which I think isn't what is happening here

But maybe https://github.com/scikit-learn/scikit-learn/issues/29075?

Labels: Bug, Documentation
Documentation Bug: Warning about "unstable development version"

### Describe the issue linked to the documentation

When browsing the scikit-learn documentation, I selected a stable version (e.g., 1.7.0) from the versions. However, I still see the warning banner at the top of the page: **This is documentation for an unstable development version.**

This is a bit confusing, as I'm clearly viewing a stable release. 

<img width="1748" height="830" alt="Image" src="https://github.com/user-attachments/assets/3e236cbb-31cd-4e77-aead-05cdee6408c9" />

### Suggest a potential alternative/fix

_No response_

COMMENT:
Merged #31062 as a "random PR to `main`" to see if this fixes things. For the future we might need a better way of doing this

Labels: Bug, Documentation
Documentation Bug: Warning about "unstable development version"

### Describe the issue linked to the documentation

When browsing the scikit-learn documentation, I selected a stable version (e.g., 1.7.0) from the versions. However, I still see the warning banner at the top of the page: **This is documentation for an unstable development version.**

This is a bit confusing, as I'm clearly viewing a stable release. 

<img width="1748" height="830" alt="Image" src="https://github.com/user-attachments/assets/3e236cbb-31cd-4e77-aead-05cdee6408c9" />

### Suggest a potential alternative/fix

_No response_

COMMENT:
@WalidGharianiEAGLE if you have a moment to double check it would be great to hear your feedback. I think the issue is resolved now. I opened scikit-learn.org in a private browser window to avoid caching and the fact that the banner remembers that you dismissed it before. 

I no longer get the banner and the version switcher at the top right shows that I am on 1.7.1.

I'll already close this issue, but please reopen it if it isn't fixed for you as well

Labels: Bug, Documentation