Users reported a bug where filtering topic lists by the index tag fails for logged-in users, triggering JavaScript errors like ‘Cannot read properties of undefined’ and ‘VM BUG: Target must be set before attempting to jump’ Moin. The issue occurs regardless of how the tag is selected — via dropdown, tag link, or tag list — but does not affect visitors. Moin noted the bug sometimes caused browser freezes and rate-limiting errors (‘Slow down, too many requests…’), forcing tab or app restarts. Sam linked the issue to the ongoing migration from raw Handlebars to Glimmer components, encouraging further bug reports. cvx confirmed the bug occurs when logged-in users view topic lists containing only pinned topics and noted it will be fixed by PR #30372.
I noticed that filtering the topic list for the index tag doesn’t work for me. There are lots of errors in the console:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'get')
Uncaught (in promise) Error: VM BUG: Target must be set before attempting to jump
It does not happen when I do the same as a visitor.
This feels very related to our “raw handlebars” → “glimmer components” migration.
Please keep reporting these as you discover them, this is extremely helpful!
I would prefer not to discover any more. Once, Discourse didn’t stop sending requests until I saw the following:
Slow down, too many requests from this user. Please retry again in 11 seconds. Error code: id_60_secs_limit.
And sometimes my browser app didn’t respond, so I had to close it and quickly close the tab after reopening.
Thank you for the report! This was happening when a logged in user visited a topic lists that contained only pinned topics. Will be fixed by FIX: An off-by-one error in glimmer topic list by cvx · Pull Request #30372 · discourse/discourse · GitHub
This topic was automatically closed after 24 hours. New replies are no longer allowed.
