Oops... after upgrade (highlight.min.js)

AI-generated summary

After a Discourse update, Arimov encountered an “Oops…” error due to a missing file: /var/www/discourse/vendor/assets/javascripts/highlightjs/highlight.min.js. The error was traced to the highlight_js.rb file, which failed to read the file. Arimov later discovered that the issue was caused by insufficient disk space, and after cleaning up the space and rebuilding the application, the problem was resolved.

Friends, please advise how to solve the following problem: after the last Discourse update I get the error “Oops…”, I looked at the logs, I see in them this:

Processing by CategoriesController#index as HTML
Rendered categories/index.html.erb within layouts/application (Duration: 2.1ms | Allocations: 1070)
Rendered layout layouts/application.html.erb (Duration: 14.1ms | Allocations: 5207)
Completed 500 Internal Server Error in 235ms (ActiveRecord: 0.0ms | Allocations: 74877)
ActionView::Template::Error (No such file or directory @ rb_sysopen - /var/www/discourse/vendor/assets/javascripts/highlightjs/highlight.min.js)
lib/highlight_js.rb:51:in read' lib/highlight_js.rb:51:in bundle’
lib/highlight_js.rb:65:in version' lib/highlight_js.rb:70:in path’
app/helpers/application_helper.rb:702:in client_side_setup_data' app/views/layouts/application.html.erb:74 app/controllers/categories_controller.rb:91:in block (2 levels) in index’
app/controllers/categories_controller.rb:59:in index' app/controllers/application_controller.rb:421:in block in with_resolved_locale’
app/controllers/application_controller.rb:421:in with_resolved_locale' lib/middleware/omniauth_bypass_middleware.rb:74:in call’
lib/content_security_policy/middleware.rb:12:in call' lib/middleware/anonymous_cache.rb:389:in call’
lib/middleware/gtm_script_nonce_injector.rb:10:in call' config/initializers/100-quiet_logger.rb:20:in call’
config/initializers/100-silence_logger.rb:29:in call' lib/middleware/enforce_hostname.rb:24:in call’
lib/middleware/request_tracker.rb:233:in `call’

Turns out I ran out of disk space. Cleaned it up, rebuilt the application, everything became normal