TheSharks / WildBeast

Feature-rich Discord bot framework
https://docs.wildbeast.guide
Other
290 stars 141 forks source link

Music Error #342

Closed ZandercraftGames closed 6 years ago

ZandercraftGames commented 6 years ago

I am running WildBeast, ArrangoDB, and the music thingy with Docker and I get an error about unknown length of undefined when running music commands but no errors when starting the music container or wildbeast container or the DB container.

curtisf commented 6 years ago

Please provide an error log or the stacktrace.

ZandercraftGames commented 6 years ago

INFO: Beginning startup sequence... INFO: Scaling known. Total: 1, mine: 0 INFO: Fully up-to-date, nice! INFO: Fully ready, serving 491 guild(s). INFO: LavaLink node ws://192.168.99.100:2333 ready. CMD: join-voice by ZandercraftGamesYT in Zandercraft PE Server | United MCPE/MC Windows 10 ERROR: Error: Error: Not Found at resolveTracks (C:\Users\j3zza\Desktop\WildBeast\src\encoders\lavalink.js:58:13) at process._tickCallback (internal/process/next_tick.js:68:7) CMD: join-voice by ZandercraftGamesYT in Zandercraft PE Server | United MCPE/MC Windows 10 ERROR: Error: Error: Not Found at resolveTracks (C:\Users\j3zza\Desktop\WildBeast\src\encoders\lavalink.js:58:13) at process._tickCallback (internal/process/next_tick.js:68:7) CMD: ping by ZandercraftGamesYT in Zandercraft PE Server | United MCPE/MC Windows 10 CMD: join-voice by ZandercraftGamesYT in Zandercraft PE Server | United MCPE/MC Windows 10 CMD: request by ZandercraftGamesYT in Zandercraft PE Server | United MCPE/MC Windows 10 ERROR: Error: Error: Not Found at resolveTracks (C:\Users\j3zza\Desktop\WildBeast\src\encoders\lavalink.js:58:13) at process._tickCallback (internal/process/next_tick.js:68:7)

ZandercraftGames commented 6 years ago

https://pastebin.com/iPn0eepL

ZandercraftGames commented 6 years ago

@caf203

ZandercraftGames commented 6 years ago

@linuswillner ?

linuswillner commented 6 years ago

For the sake of our inboxes, please do not create repeat reply after one unless necessary. Your issue will be reviewed when someone has time to. If you need to correct a reply, please use the edit feature.

As for your actual question, this seems to be a valid issue. There appears to be an error in the decoupling document. We are investigating a potential remedy and will let you know when one is available.

ZandercraftGames commented 6 years ago

Hmm... Because it was doing it before I de-coupled it... It gave this same error or a similar one when it was first installed in docker.

linuswillner commented 6 years ago

I see. No matter, we are investigating a remedy and will issue a correction when we have a solution.

ZandercraftGames commented 6 years ago

Ok. Thanks

ZandercraftGames commented 6 years ago

Got a fix yet or no? Hows progress?

Dougley commented 6 years ago

Please verify you're running lavalink v3 and not v2

ZandercraftGames commented 6 years ago

@Dougley How would I do that?

Dougley commented 6 years ago

Your issue is most likely related to you running lavalink v2. If you're using Docker, you can use the new compose file at https://github.com/TheSharks/WildBeast/blob/9688e75c91edc440d797576e9e3fdaa081413166/docker-compose.yml, otherwise reinstall lavalink yourself.

ZandercraftGames commented 6 years ago

@Dougley You have not yet replied how to check what lavalink version it is... And if it is the wrong lavalink version it would be because of improper setup and documentation on your part as I installed it following your documentation to the letter.

ZandercraftGames commented 6 years ago

This issue was not complete and therefore it is bad practice to close the issue before the it has been sorted out.

ZandercraftGames commented 6 years ago

@Dougley You should not be too quick to that close button.

Dougley commented 6 years ago

I suggest you change your tone of voice, you've already been banned from our support Discord for the same degree of hostility shown here. We're not tech support, use Google to find out what you need for basic stuff. Besides, this is my repository, so who are you to call me out on "bad practices"?

linuswillner commented 6 years ago

Documentation corrections are pending in #344, there are still some kinks to iron out in this PR. When it's merged, corrected decoupling documentation will be deployed.

As that PR mentions, what you are experiencing is an issue of partially our doing in addition to using the wrong Lavalink version. Please wait for the corrected documentation to receive additional instructions.

linuswillner commented 6 years ago

This issue should be resolved as of release 6.1.1.