You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I invoke client.SetPlaylistImagewithoutclient.WithRetry, everything works and the playlist image updates. When I invoke client.SetPlaylistImagewithclient.WithRetry, the playlist image is updated but client.SetPlaylistImage returns "io: read/write on closed pipe".
Expected Behavior
client.SetPlaylistImage should work the same with or without autoretry
Possible Cause
The API endpoint (PUT /playlists/{playlist_id}/images) returns 202 Accepted (Regardless if autoretry is enabled or not) which is then retried because of shouldRetry. The reason that it works without autoretry is this if statement. I'm not entirely sure if the problem is Spotify returning an unexpected response (Please note that this library seems to anticipate the 202 response here) or the condition in shouldRetry.
It seems this may have been discussed in #100 (Specifically this comment)
The text was updated successfully, but these errors were encountered:
Version
go version go1.17.5 windows/amd64
github.com/zmb3/spotify/v2
:v2.0.1
Issue
When I invoke
client.SetPlaylistImage
withoutclient.WithRetry
, everything works and the playlist image updates. When I invokeclient.SetPlaylistImage
withclient.WithRetry
, the playlist image is updated butclient.SetPlaylistImage
returns"io: read/write on closed pipe"
.Expected Behavior
client.SetPlaylistImage
should work the same with or without autoretryPossible Cause
The API endpoint (
PUT /playlists/{playlist_id}/images
) returns202 Accepted
(Regardless if autoretry is enabled or not) which is then retried because ofshouldRetry
. The reason that it works without autoretry is this if statement. I'm not entirely sure if the problem is Spotify returning an unexpected response (Please note that this library seems to anticipate the 202 response here) or the condition inshouldRetry
.It seems this may have been discussed in #100 (Specifically this comment)
The text was updated successfully, but these errors were encountered: