Don’t know exactly when the change happened but I thought I’d updated
fairly recently. After doing the first rebuild I could have sworn I saw a
git pull but I didn’t watch carefully enough. As soon as I can take a
little more downtime (probably tonight) will try again.
I’m having the same issue. My guess is that because ./launcher rebuild says “Your version of Discourse Docker is ahead of origin” when git tries to get the latest version, so the latest version is never pulled?
Actually what I did was git reset --hard origin/master to have the repository in sync again and then another./launcher rebuild (that didn’t trigger the “ahead of origin” message). Now I’l wait to see if I get the reports. Is there any way to trigger those reports manually so that I don’t have to wait?
In my case the sysadmin deleted Staff category when we installed discourse (3 years ago).
Now I have create another Staff category (only admins and staff can create/reply/see it).
This category was created before the last upgrade to Discourse Docker Image 1.3.3 (so we have git pull and rebuild all and the upgrade was a success).
By the way in logs I have this error when I trigger Jobs::DailyPerformanceReport in sidekiq: