PATCH player request never times out | Lavalink | Page 1

subtle zenith Sep 15, 2023, 12:42 PM

#

Sending a PATCH request with invalid data results in a request that never finishes.

curl -H "Authorization: $LAVALINK_PASSWORD" http://localhost:2333/v4/sessions/3qygjqfuvxcejpug/players/182892283111276544 -i -X PATCH --json '{"voice" : {"token" : "02ab32bd6b39aaf3", "endpoint" : "wss://madrid253.discord.media:443", "sessionId" : "4541df6f11175d3f34b3baedb7b57a0d"}}'

Tested with this cURL command, where the invalid data is an endpoint that includes the protocol, and the command never finished, even after running for over an hour.

Is this intended behaviour?, being permanently stuck on an await, or running out of threads in a pool because of a failed request that could easily return an error, or time out, doesn't seem like something that's intended.

sick sorrel Sep 15, 2023, 12:49 PM

#

just for my understanding

#

what is actually invalid in there

subtle zenith Sep 15, 2023, 12:50 PM

#

"endpoint" : "wss://madrid253.discord.media:443"
this is "invalid" and causes this issue

"endpoint" : "madrid253.discord.media:443"
this works completely fine

#PATCH player request never times out