302 for stems download attempt on first run

[chris-miner]

What I did:

1. launched the system with docker-compose -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml up
2. accessed system via localhost url
3. uploaded a file
4. clicked on dynamic mix
5. accepted defaults and clicked on "create mix"
6. the system begins processing the mix

What I Expected:
I expected the system to produce various output files for vocals, drums, bass, etc.

What I Found:
Error Message:

Redirect response '302 Found' for url 'https://github.com/deezer/spleeter/releases/download/v1.4.0/4stems.tar.gz' Redirect location: 'https://objects.githubusercontent.com/github-production-release-asset-2e65be/211124697/e6d5ff80-f98d-11e9-80ea-8d8855627afb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240131%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240131T141235Z&X-Amz-Expires=300&X-Amz-Signature=305269d82fd8aa0f18ebe75eca6f504a6a12c817b6e83600c047b75581dd1739&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=211124697&response-content-disposition=attachment%3B%20filename%3D4stems.tar.gz&response-content-type=application%2Foctet-stream' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/302

Extra Info:
I got this error a few times, even after restarts, but then somehow when I restarted the system, I got a different error about not having a save_path set. That error persisted after restarting the container. So I deleted the container, and relaunched. Same save_path error. Then I deleted the volumes and the container and restarted the system. I was then able to produce the error by attempting a dynamic mix with both the 4 and 5 stems models. The "static mix" pathway seems to result in the save_path error, which is then the only error it seems I can produce. to get back to the 302, need to start with a fresh container/volumes setup.

My Take:

It seems the 302 redirect is not being followed. Not sure why this error isn't produced every-time. You'd think failure to download the stems would result in the same error every time since they were presumably not downloaded successfully ever.

[JeffreyCA]

Thanks for the report, this is being fixed in #949

A few workarounds:

1. Use a previous prebuilt image (no ARM support):

TAG=v3.19.0 docker-compose -f docker-compose.yml -f docker-compose.build.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml up

2. In requirements.txt, change httpx==0.26.0 to httpx==0.19.0 and build the images from source using --build.
3. Check out the branch in #949 and build the images from source.

I'll look into why the download errors aren't happening consistently

[JeffreyCA]

This should be fixed in the latest release. I added some logic to remove leftover files from the failed model download so you shouldn't have to delete any Docker volumes for it to work