Closed cgwhouse closed 4 months ago
since lavalink updated to spring 3.3.0
from 3.1.0
there seems to be a breaking change https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#parameter-name-retention
I fixed this issue in https://github.com/topi314/SponsorBlock-Plugin/pull/15 and will create a new release later today
Description
On a fresh rebuild (i.e. after running
docker system prune -a --force
) of my Lavalink server container, I see that 4.0.7 is pulled successfully. The image is defined asghcr.io/lavalink-devs/lavalink:4
per the documentation. Server starts up normally, and connection is established with the client. In my case, I am using a .NET client and the Lavalink4NET library.Once the server receives a track request from the client, a
ServletException
is thrown, and the inner mentions a compiler flag (I will include the full logs below of course). I tested with both Spotify and YouTube requests and received the same behavior FWIW. The issue is with the SponsorBlock integration in some sense, when I disable it I get standard behavior.To Reproduce
Steps to reproduce the behavior:
docker container logs [container name] --follow
)Expected behavior
Track is queued
Version info
Client used:
Output of
java -version
:I don't believe this is being used if I am relying on the Docker container? But here is the output, I do have a headless JDK installed on this Raspberry Pi host:
Lavalink Logs:
Additional context
While I absolutely do not expect anyone to spend time inspecting this issue let alone my own projects, here is the repo for my bot, it is what I used to produce the behavior above (branch
skip-text-bug-fix
). The latest commit in that branch has sponsorblock bits commented out, so I could verify that it works without them.