Docker Manager runs non-existent rake task

The rake task to flush the service worker fails as seen below:

$ bundle exec rake assets:flush_sw
rake aborted!
Don't know how to build task 'assets:flush_sw' (See the list of available tasks with `rake --tasks`)
Did you mean?  assets:clean
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
(See full trace by running task with --trace)
WARNING: Unable to flush service worker file
Running post deploy migrations
$ bundle exec rake multisite:migrate
Multisite migrator is running using 20 threads

Migrating default
DONE

I just figured I would report this. I did a cursory search but may have missed if this is a dupe.

2 Likes

I saw this myself upgrading a site last week. For what it is worth, upgrade seemed to work fine, site is still running.

Sorry for the noise, there is some ongoing work on the service worker currently that is pending a few extra fixes/tests so we are able to kick the tires here - this warning will go away once we’ve got the service worker flushing logic in core :slight_smile:

5 Likes