-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
🚫 ope: filterWrapper is not iterable #948
Comments
Did you try running with |
Gotcha
This is the error I caught, the error is pretty inconsistent sometimes it works and sometimes it doesnt. Hopefully we can make this solve this inconsistency |
Looks like this is a bug with the ytsr package: TimeForANinja/node-ytsr#180 |
Getting an identical error using the latest release through Docker on a fresh install of Ubuntu 22.04. Tried installing a few months ago on a completely different machine through the basic Node.js install route and got the same error. Is there a known fix I'm missing?
|
I am also getting this same error while using docker on latest release |
+1 happening to me as well using latest docker build |
happening to me as well, latest docker release |
+1 |
1 similar comment
+1 |
+1 latest docker |
Same issue, downgraded to codetheweb/muse:2.2.4 for now... |
+1 experiencing this issue, latest version and 2.2.4 as well |
this issue used to be sporadic, but after a while of running the bot, it occurs on literally every play command (no matter if the input is a search query, spotify or youtube url), rendering the bot entirely unusuable. I would suggest that node-ytsr is forked. in the meantime, I applied the ytsr fix in my docker-compose setup like so in order to avoid building my own image:
|
@drpepper66 This worked for me! Thank you! P.S. Could the sporadic nature be due to Muse's caching? I know nothing about this project yet, so sorry if this is a dumb question. |
how do you do that but with node? |
sed -i 's/of filterWrapper[)]/of filterWrapper|| [])/g' /node_modules/ytsr/lib/utils.js
|
I don't have the time right now, but if anyone else is interested in fixing this I think we could completely drop the |
As per this this github issue, to fix all you have to do is edit before after |
since the API is pretty limited, I believe we can use the API as a failure fallback while keeping ytsr as the main search engine. |
Just installed this -- same error. Using the latest docker. =/ |
Looks like the problem was fixed on TimeForANinja/node-ytsr#203 |
🚀 Released in Release v2.4.2. |
Running the bot for the first time using docker image (latest 2.4.2 version) and I have the same problem. :( |
@cRaZy92 do you have any logs? 2.4.2 completely solved the issue for me. |
Never mind, it only happened with one specific track on Spotify, sorry for the false alarm. Thank you anyways! |
What's happening?
Concisely describe what's going wrong.
Logs
logs seems to be not found on console
Additional context
This error occurs randomly while using
/play
Confirmed that this is not a user error seems to be the server side.
Runtime
I'm running Muse:
Versions
The text was updated successfully, but these errors were encountered: