Webpacker can't find core/inert.css

[neilzone]

Steps to reproduce the problem

I was trying to upgrade my glitch-soc version, to the latest code.

All the commands ran successfully, other than a warning from yarn install (but, as it was only a warning, it completed).

The web UI reloads, but I see the following error in my log:

FATAL -- : [925bdbed-b2e5-4408-8cb4-d7e1b571da94]
Jan 29 20:08:07 nuc3 bundle[1798538]: [925bdbed-b2e5-4408-8cb4-d7e1b571da94] ActionView::Template::Error (Webpacker can't find core/inert.css in /home/mastodon/live/public/packs/manifest.json. Possible causes:
Jan 29 20:08:07 nuc3 bundle[1798538]: 1. You want to set webpacker.yml value of compile to true for your environment
Jan 29 20:08:07 nuc3 bundle[1798538]:    unless you are using the `webpack -w` or the webpack-dev-server.
Jan 29 20:08:07 nuc3 bundle[1798538]: 2. webpack has not yet re-run to reflect updates.
Jan 29 20:08:07 nuc3 bundle[1798538]: 3. You have misconfigured Webpacker's config/webpacker.yml file.
Jan 29 20:08:07 nuc3 bundle[1798538]: 4. Your webpack configuration is not creating a manifest.

I can access the webserver, but it returns only the "oops" gif.

Expected behaviour

Web UI should reload successfully

Actual behaviour

Web UI reloads, but throws error and shows the "oops" gif.

Detailed description

No response

Mastodon instance

mastodon.neilzone.co.uk

Mastodon version

I can't access it to check

Browser name and version

Firefox 122

Operating system

Debian 12 testing

Technical details

No response

[ClearlyClaire]

Did you run bundle exec rails assets:precompile? If so and it did not error out, try bundle exec rails assets:clobber assets:precompile

[neilzone]

Did you run bundle exec rails assets:precompile?

embarrassed face

I've missed that step from the upgrade instructions. Running it now, but quite possibly entirely my own error. Sorry.

[neilzone]

That has certainly moved me onwards - thank you.

I've now got another error to debug, on loading the web UI in Firefox:

Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly.

Try refreshing the page. If that does not help, you may still be able to use Mastodon through a different browser or native app.

With a stack trace of:

TypeError: v is null


W@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/async/direct_timeline-a58f5e63ffdbcce76fa4.chunk.js:1:4057
ki@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:549936
kc@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:606791
_l@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:595945
vl@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:595873
bl@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:595734
il@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:592541
ll@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:592930
Ba@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:533777
al/<@https://mastodon.neilzone.co.uk/packs/js/flavours/glitch/home-780f44d543d29b69854d.chunk.js:2:590478



lastStatus.get (webpack:///app/javascript/home/mastodon/live/app/javascript/flavours/glitch/features/direct_timeline/components/conversation.jsx:173:31)
Xh (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:167:136)
Wk (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:290:336)
uj (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:280:391)
uj (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:280:322)
uj (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:280:179)
Ok (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:271:87)
Dk (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:273:299)
jg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:127:104)
Ek (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:267:272)

I wonder if I might have caused this myself, by failing to compile the assets at the right point initially.

[ClearlyClaire]

This definitely looks like it could be a bug due to a recent refactor, although I'm unable to reproduce it.

[neilzone]

If I can be of help in fixing it, please do just point me in the direction of what I can do to help!

[ClearlyClaire]

I have been able to reproduce this, and will try to fix it this evening.

[ClearlyClaire]

Your issue should be fixed by #2595

[neilzone]

Your issue should be fixed by #2595

Confirmed as working. Thank you, Claire.