"0 new commits" on upgrade


#1

i’ve seen this happen on a few plugins. i’m running v2.0.0.beta10 +115.


(Joshua Rosenfeld) #2

That’s strange…looking at Commits · discourse/discourse-assign · GitHub you’re theoretically running 1 commit prior to latest (FIX: `upsert` was less safe under concurrency). Does upgrade work?


#3

i’ve hit it a few times. want me to try again? :wink:


(Joshua Rosenfeld) #4

No, unlikely anything will change. So when you hit it, do you go through the “normal” upgrade process (i.e. see the progress bar move and commands output)?


(Michael Friedrich) #5

I’ve seen this a while ago too (before beta10), but it was hard to reproduce. The overall fetching of each revision (core and plugins) was extremely slow, maybe an indicator when to hit this. Could be a caching problem where the previous diff was 0, but right in the same second a git push added +1 which enables the upgrade action button. Not sure if that’s two events (commit diff count and button), or just one.


#6

i refreshed a couple times and it just disappeared. … shrug


(Joshua Rosenfeld) #7

Moved this to support for now. If you can find a consistent repro, feel free to move it back.


#8

i got this again. might be related to this?


(Sam Saffron) #9

Can you rebuild from the console.

cd /var/discourse
./launcher rebuild app

Maybe something is off in the container.