
Description
EDIT by @unixfox: This bug affects all the invidious instances, please don't add a comment if you just want to say that you can also reproduce the same issue, thank you! Just react with a 👍
Could not extract JSON. Youtube API returned error 500 with message:
"ExecuteQuery for ChannelMiddlewareService-GetShelves failed: RET_CHECK failure (video/youtube/channels/frontend/shared/continuations/channel_middleware_token_encoding.cc:15) absl::WebSafeBase64Unescape(web_safe_token, &unescaped_token) ; OneMustSucceed: input 'mw_shelf_source_exp_continuation_unwrapper'; OneMustSucceed: input 'mw_shelf_source_exp_subgraphs'; OneMustSucceed: input 'mw_shelf_source_exp_empty_shelf_filter'; OneMustSucceed: input 'ShelfSourceExpansion__graph'; OneMustSucceed: input 'get_shelves_shelf_candidate_rank_sorter'; OneMustSucceed: input 'wrapped_main_subgraph'; OneMustSucceed: input 'pre_decoration_subgraph'; OneMustSucceed: input 'decoration_annotator_subgraph'; OneMustSucceed: input 'post_decoration_subgraph'; PropagateAllErrors: input 'GetShelvesEndpoint__graph'; PropagateAllErrors: input 'default_filter_survivor_probe_op'; PropagateAllErrors: input 'policy_enforcement_candidate_predicate'; /ChannelMiddlewareService.GetShelves RPC failed"
Activity
shnappi-kk commentedon Mar 31, 2023
Yep. The error appears when you enter the channel.
/channel/UCQHX6ViZmPsWiYSFAyS0a3Q for example.
In some cases, refreshing the page gives the expected result, but then refreshing the page again gives this error.
Sections "streams", "community", "playlists", individual playlists and individual videos do not cause this error.
Perhaps, subscriptions are not updated for the same reason.
I see this error on yewtu.be invidious.snoopyta and on my own instance.
SethPyle376 commentedon Mar 31, 2023
davidhfrankelcodes commentedon Mar 31, 2023
knivey commentedon Mar 31, 2023
I'm also getting it, from log file after clicking to view a channel:
99thim commentedon Mar 31, 2023
Abyssgrowth commentedon Mar 31, 2023
Was there an internal youtube update that caused this?
unixfox commentedon Mar 31, 2023
Yes that's correct. If you want, you can discuss it further on matrix or IRC.
alithechemist commentedon Mar 31, 2023
That is because a change is being deployed to a large cluster
garoto commentedon Mar 31, 2023
It seems it's related to how channels are now using the new
@name
handle/moniker format by default.ytfzf -c invidious-channel
pystardust/ytfzf#667unixfox commentedon Apr 3, 2023
New commit fixed the issue: #3718
Please update your invidious instance.
pkgs/invidious: upgrade 2023-03-15 to 2023-04-01