ice.d
May 22, 2026, 10:25pm
1
So:
All i did was hit update all then i went to check the logs then went to admin on a user then hit back to forum and got this message.
What happened?
Edit
Just opened it in a new tab and it worked what’s happening?
ice.d
May 23, 2026, 1:59pm
3
Here you go with the most recent logs
Ethsim2
May 23, 2026, 2:24pm
4
There seem to be two different things in those logs.
The ActionView::Template::Error / Propshaft lines about a missing chunk...js asset may explain why this happened immediately after “update all” and then worked in a new tab. That looks like an old tab trying to load an asset filename that no longer exists after the update/rebuild.
The separate line:
NameError (uninitialized constant ReactionsSerializerHelpers) app/serializers/post_stream_serializer_mixin.rb:31:in 'PostStreamSerializerMixin#post_stream'
looks like the bundled discourse-reactions issue I reported here:
my Discourse version is 2026.5.0-latest.1 (fbcbdc46d8 )
I am seeing repeated /logs errors when loading topic posts. The error appears to come from the bundled discourse-reactions plugin while serializing the post stream.
The site reports the message as 8 copies reported.
I checked the compare range below, but it does not look like it touches the failing backend code path, so I am reporting this separately:
I also opened a PR here:
main ← Ethsim12:fix-reactions-serializer-helpers-nameerror
opened 12:19PM - 23 May 26 UTC
Tests run:
bundle exec rubocop plugins/discourse-reactions/plugin.rb plugins/… discourse-reactions/lib/discourse_reactions/reactions_serializer_helpers.rb
ruby -c plugins/discourse-reactions/plugin.rb
ruby -c plugins/discourse-reactions/lib/discourse_reactions/reactions_serializer_helpers.rb
LOAD_PLUGINS=1 bundle exec rspec plugins/discourse-reactions/spec --exclude-pattern "plugins/discourse-reactions/spec/system/**/*_spec.rb"
Result: 183 examples, 0 failures.
I also attempted the targeted system spec locally. After installing Playwright/Chromium dependencies, the browser opened a blank page and the app did not mount (`#main.ember-application` was not found), so I treated that as a local Codespaces system-test environment issue and left full system coverage to CI.
So I would treat the Propshaft asset error as likely stale-tab/update fallout, and the ReactionsSerializerHelpers error as a separate backend reactions-plugin issue.
1 Like
