[Bug] The link to the model is incorrect in the GitHub Actions environment.

[pansong291]

• I didn't find a similar issue already open.
• I read the documentation (README AND Wiki)
• I have installed FFMpeg
• My problem is related to Spleeter only, not a derivative product (such as Webapplication, or GUI provided by others)
• I have found the specific location of the relevant code.

Description

I ran the spleeter separate command in an Ubuntu environment using GitHub Actions, but encountered an error. The issue lies in the incorrect download link for the model.

The information is

httpx.HTTPStatusError: 404 Client Error: Not Found for url: https://github.com/pansong291/github-action-tasks/releases/download/v1.4.0/2stems.tar.gz

And the code looks like

        return cls(
            environ.get("GITHUB_HOST", cls.DEFAULT_HOST),
            environ.get("GITHUB_REPOSITORY", cls.DEFAULT_REPOSITORY),
            environ.get("GITHUB_RELEASE", cls.LATEST_RELEASE),
        )

I suspect that this issue may be caused by the presence of a duplicate variable with the same name in the environment variables of GitHub Actions.

Step to reproduce

1. A different github repo
2. Use the Github Actions
3. Got 404 error

Output

httpx.HTTPStatusError: 404 Client Error: Not Found for url: https://github.com/pansong291/github-action-tasks/releases/download/v1.4.0/2stems.tar.gz

Environment

OS	Linux (Ubuntu)
Installation type	pip
RAM available	--
Hardware spec	CPU

Additional context

[pansong291]

https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable

[pansong291]

Due to the limitations of GitHub Actions, it is not possible to directly modify the GITHUB_REPOSITORY environment variable within its workflow, which means that running spleeter directly in the workflow is not feasible. Where can I modify this link address or are there any other solutions available? I can put this file in the release page of my repository. However, this is a temporary solution, and I hope there are other ways to fully resolve this issue.