Endless spinner on some posts

Bug
1

I have a strange thing on the latest version on Discourse (3.4.0.beta1-dev).

Some posts aren’t shown and give the following error in the console.
The spinner keeps turning and turning!

Strange thing is that some posts hang when i’m logged in and will load when i sign-out. But some never load.

This is what i get in the console:

Could not view topic TypeError: Cannot read properties of undefined (reading 'name_key')
    at post.js:32:29
    at Array.map (<anonymous>)
    at T.munge (post.js:28:51)
    at T.create (rest.js:19:29)
    at d.create (index.js:385:1)
    at _._build (store.js:301:25)
    at _._hydrate (store.js:423:17)
    at _.createRecord (store.js:225:14)
    at post-stream.js:1048:31
    at Array.forEach (<anonymous>)
    at k.updateFromJson (post-stream.js:1047:28)
    at post-stream.js:353:14
    at _ (rsvp.js:434:1)
    at y (rsvp.js:420:1)
    at invoke (backburner.js.js:282:1)
    at d.flush (backburner.js.js:197:1)
    at p.flush (backburner.js.js:358:1)
    at B._end (backburner.js.js:798:1)
    at B._boundAutorunEnd (backburner.js.js:523:1)

What i have done so far:

  • Checked in safe-mode. Same problem
  • Turned off plugins 1-by-1. Same problem
  • laucher rebuild app

I see this in the rebuild btw:

I, [2024-08-23T08:26:25.919351 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
warning " > @discourse/lint-configs@1.3.9" has incorrect peer dependency "ember-template-lint@6.0.0".
warning " > @glint/environment-ember-loose@1.4.0" has unmet peer dependency "@glimmer/component@^1.1.2".
warning " > discourse-markdown-it@1.0.0" has unmet peer dependency "xss@*".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > discourse > @uppy/aws-s3@3.0.6" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > discourse > @uppy/aws-s3-multipart@3.1.3" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > discourse > @uppy/xhr-upload@3.1.1" has incorrect peer dependency "@uppy/core@^3.1.2".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > discourse-plugins > ember-this-fallback@0.4.0" has unmet peer dependency "ember-source@^3.28.11 || ^4.0.0".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > admin > ember-source > router_js@8.0.3" has unmet peer dependency "rsvp@^4.8.5".
warning "workspace-aggregator-655d3348-fa9a-483d-b7d4-d3f77ee964e6 > discourse > @uppy/aws-s3 > @uppy/xhr-upload@3.3.0" has incorrect peer dependency "@uppy/core@^3.2.1".
1 Like
3

Are you able to share a public topic where it’s happening please?

5

Sure it’s happening here (when i’m logged in and logged ouy!)

And here it’s never happening:

And this one has it when i’m logged in:

but not when i’m logged out!

And other things i just tested is:

  • wiping my cookies
  • using an private browser.
    Same results :frowning:
6

I can’t repro sadly, can you make me a video of what you see please?

7

I was able to reproduce when the links were posted, but it works fine now.

8

I tried the first link and it didn’t work for me. Forum itself yes, but that topic showed just spinner.

9

No upgrade or change done today… only a new post.

But it looks like the problem is gone. :boom:

I had this for more than 2 days!
I’m almost bold from pulling my hair out :hear_no_evil:

@joffreyjaffeux could it be a db upgrade or something like that in background?

And thanks for looking into it!! :heart:

1 Like
12

I don’t know ATM, but I have had other reports, we will try to gather more info.

1 Like
13

I’ll keep an eye on this… When it happens again i’ll make a video!
Including what i see in the consolelog + networktabs :+1:

16

We’re having this issue now too on 3.4.0.beta2-dev. Same logs

1 Like
18

Unfortunately, we are also getting the issue on one of our forums on 3.4.0.beta2-dev. Same logs

1 Like
19

Then i hold my horses… Still on 3.4.0.beta1-dev.
Problem is solved in my forum but i still don’t know how…

1 Like
20

Just to update after a period of say 24H the issue has now gone away which suggests it is forcing some sort of reindexing as others have suggested.

1 Like
21

Thank you for reporting this bug. It should be fixed with this PR

We moved the like post-action type to the database. However, for performance reasons, we cache post action types (for 24 hours) - that’s why everything is automatically fixed for you after ~24 hours.

When Discourse is updated, we should reset this cache just to be sure that the front-end has access to all post-action types.

6 Likes
22

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.