You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Youtube-tui does panic if invidious has popular feed disable:
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', src/items/itemlist.rs:42:16
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
If I enable the popular feed at server youtube-tui does work again.
I have try to disable popular at the page,yml but this has not fix the problem.
main.yml:
mouse_support: trueinvidious_instance: https://youtube.luckyturtle.devmax_watch_history: 50allow_unicode: truemessage_bar_default: All good :)images: Sixelsrefresh_after_modifying_search_filters: trueimage_index: 4provider: YouTubeenv:
terminal-emulator: alacritty -evideo-player: mpvdownload-path: '''~/Downloads/%(title)s-%(id)s.%(ext)s'''youtube-downloader: yt-dlpbrowser: firefox
In commands.yml, change launch_command to something else (for example loadpage watchhistory ;; flush ;; history clear).
What happened
I believe when you disable the popular feed, instead of returning nothing on the api request, it returns an empty array (instead of an error) which itemlist sorta freaks out.
The Popular item in pages.yml is just the popular page button, by all it does is load a page (similar to a hyperlink). But because in the launch command in commands.yml loads the popular page on start, as soon as the page loads it crashes because it was not expected to recieve an empty array.
I'm gonna catch this case so it doesnt crash maybe later
Apparently it was already fixed a few git commits ago, its just that the latest crates.io version (0.6.2) is not new enough to include this fix, but it will be included in the next crates.io version
Youtube-tui does panic if invidious has popular feed disable:
If I enable the popular feed at server youtube-tui does work again.
I have try to disable popular at the
page,yml
but this has not fix the problem.main.yml
:pages.yml
:The text was updated successfully, but these errors were encountered: