# Rake error during update (not fatal)

**URL:** https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823
**Category:** Self-hosting
**Created:** [December 22, 2019, 1:15pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823 "2019-12-22T13:15:00Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [December 22, 2019, 1:15pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/1 "2019-12-22T13:15:00Z")

</div>

I saw this go by in the logs, but the upgrade continued with apparent success:

```
Waiting for Unicorn to reload...........................................................
$ 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

```

Is this important? Interesting?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 22, 2019, 6:44pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/2 "2019-12-22T18:44:54Z")

</div>

Not sure, @eviltrout did the rake task name change?

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [December 23, 2019, 4:11pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/3 "2019-12-23T16:11:17Z")

</div>

Is this service worker related @featheredtoast? I can’t find `flush_sw` in our codebase right now.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 23, 2019, 4:29pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/4 "2019-12-23T16:29:19Z")

</div>

That is a task that was live on master for less than 3h and was reverted afterwards.

Please use a rebuild @Ed_S.

```plaintext
cd /var/discourse
./launcher rebuild app

```

---

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [December 23, 2019, 4:53pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/5 "2019-12-23T16:53:26Z")

</div>

This won’t cause any issues updating, just noise in the logs which you can ignore for now - flush\_sw is a new rake task that _will_ exist once we re-add it. I’ve been working out some issues with the rake task in a draft PR, but for now those errors in the logs are harmless.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 23, 2019, 11:43pm UTC](https://meta.discourse.org/t/rake-error-during-update-not-fatal/136823/6 "2019-12-23T23:43:28Z")

</div>