-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Audio] Lavalink jar download/redirect #2682
Comments
Okay, so there's some weirdness here. The redirect is normal:
(Not using curl's location flag intentionally to just quickly check if we are being redirected) However, this shouldn't cause any issues (and in fact didn't seem to on the same machine where I got redirected with curl) aiohttp (which we use for the download) follows redirects unless explicitly told not to. Here's where the actual weirdness kicks in. On the surface, this looks to be related to aio-libs/aiohttp#3535 However (And the reasons this may not be related)
So unless the connection is terminated during download (at either end) I'm not sure we should be impacted by this issue specifically. I'll try and look into this more later, but as I can't actually reproduce this locally, I am relying solely on what we have as an error and inspecting the conditions required to make this happen. |
|
For now until this is resolved, users can manually download the Lavalink.jar from https://github.com/Cog-Creators/Lavalink-Jars/releases/tag/3.2.0.3_796 and place it in their Audio data directory while the bot is off. |
I did this and the bot tries to download the jar anyway. |
The SSL error is a complete red herring (i.e. it's unrelated to this issue) and actually a bug in Python Asyncio and will be fixed in the next minor release of 3.7. It's simply a messy error message which shouldn't be logged (the 3.7 fix literally involves just not logging the error when it's received). My guess is that this issue doesn't exist - the users are waiting for the jar to download, it's taking a little while, they check their console, see the SSL error, and assume it failed even though it's still downloading normally. |
Some users waited over 10 minutes for the jar to download with no file at the end of it. |
For users experiencing problems when Red downloads the Lavalink jar, please install #2764 and try again. This will log whatever exception occurred in the console. If nothing is logged it means the connection is just damn slow, and it's probably still trying to download. To install it, if you have the updatered cog, use this command in Discord:
Or update manually from the console using the install command but replace |
Here's the error with @Tobotimus patch:
|
Aha! Thank you very much. Just note that this is just a single instance of an error, this is unlikely to the only error which was previously being silenced, other users are likely to have other exceptions. As for this error you're receiving, some context... Red downloads the Lavalink.jar to a temporary directory (created automatically with the It looks as though in your filesystem, |
Resolves [this issue](Cog-Creators#2682 (comment)). Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
Resolves the issue outlined [here](#2682 (comment)). Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
Closing this now the logging PR has been merged and the most common underlying issue has been fixed. |
Other bugs
What were you trying to do?
Helping people in support where they have installed Red 3.1 and are loading audio. This does not occur on every install.
What were you expecting to happen?
For the Lavalink.jar on our jar repo to be downloaded in the background on first load.
What actually happened?
[INFO] red.audio.manager: Downloading Lavalink.jar...
The bot stays "stuck" here
until the user receives an SSL error:(Edit: This error is unrelated, see below)ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
How can we reproduce this issue?
Not quite sure of the cause on why some users can get the direct link and others get a redirect before they are served the jar. Yami and I tried curling the jar link we have in audio's manager.py and received a redirect. The bot installed on the machine I was doing the curl on was able to download the jar with no issues.
Note for users: If you're experiencing this issue, see this comment below on how to help us help you.
See: https://discordapp.com/channels/133049272517001216/387398816317440000/578251926303670303
The full SSL error:(Edit: This error is unrelated, see below)The text was updated successfully, but these errors were encountered: