Hi, I'm working on #2128, and for some reason Spotify has started giving me 401 responses, blocking me from getting the last few caches. Should I just wait, or have I ruined the api keys for everyone?
#Getting HTTP 401 from Spotify
tall blade
cunning silo
tall blade
On Arch Linux, on a checkout of https://github.com/spotDL/spotify-downloader/pull/2128 with PR 2120 merged in and the failing cassettes deleted.
Command:
python -m pytest --record-mode=once tests/test_matching.py
(Besides which, the test seems pretty flaky - I don't always get the same errors, even using vcrpy)
hm. checking the error logs, it's due to "the access token expired"?
tall blade
(Besides which, the test seems pretty flaky - I don't always get the same errors...
eg case in point, the ISRC search for https://open.spotify.com/track/6fyzS9YbkUhmEmJ52s19Ob yields no results, yet when I try to run it independently I do correctly obtain https://music.youtube.com/watch?v=OtdCiuyE40g
Weirdly enough, I'm getting inconsistent results even with --recording-mode=none --block-network -- sometimes, cassettes that should work cause test failures
also, for some reason, I'm inconsistently getting YT-DLP download error on a couple of the test cases
(even though if I try to download the respective videos with yt-dlp, I get no trouble)
tall blade
Weirdly enough, I'm getting inconsistent results even with `--recording-mode=non...
specifically:
- Outside my chroot, I just get 4 failures to find matches for songs
- On the first run in my chroot, I get 27 nonspecific failures (23 aren't even logged by
pytest --log-file, 2 complain that they want to overwrite the existing cassette) - On subsequent runs in the chroot, I get the 4 match failures + 3 YT-DLP failures