-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing catch or finally after try #936
Comments
No need, we just need to wait for another fix for ytdl-core (as far as I suspect, this is the problem) |
I tried to rebuild the apps using updated libs from this comment: fent/node-ytdl-core#1216 (comment) and its working 😄 |
can you offer a branch? |
Looks like using ytdl 4.11.4 patch 1 is the better solution. But I was able to get it working by downgrading to 4.10.0. Allegedly its slower but I cant notice a difference and it works. |
I pushed an image to docker hub incorporating these fixes until this gets fixed on this repository. Image is evangelosch2811/muse, corresponding repo is here, |
Just tried and bot seems to be working for me with the current version of ytdl-core (4.11.4). |
Has it been pushed to docker? Sorry, can't seem to find it. Thanks :-) |
|
I installed version 2.2.4 using docker in a free tier oracle compute session. It was working flawlessly for about 3 days. Today whenever I try to play music it will not work. As for the cloud host, it has not reached any cap for bandwidth, memory, or storage usage.
I have tried playing:
Youtube search
Youtube direct link
Spotify search
Spotify direct link
When running docker logs I do not see any errors in the container. The only error I receive is from the bot on discord:
🚫 ope: Missing catch or finally after try
Other bot commands like disconnect and config work fine.
I have tried every combination of kicking the bot from the discord server, deleting the database, and trying different versions of the docker image.
The only thing I have not tried is using different api keys for spotify/youtube.
If there is another location to look for logs I am happy to post them here.
The text was updated successfully, but these errors were encountered: