Error 409 Release already in progress about nucleus HOT 8 CLOSED

@bastientanesie That error was designed to prevent race conditions when performing actions in the file store. There was however a bug in 0.7.4 --> 0.8.0 that prevents locks being released.

If you update to 0.8.1 locks will be released properly. Sorry 'bout that 😄

https://github.com/atlassian/nucleus/blob/master/CHANGELOG.md

Once you update to 0.8.1 you will have to sign in as an admin, then simply navigate to <YOUR_DOMAIN>/rest/admin/release-locks in your browser. That will cause all current locks to be released and everything should work normally from then on.

from nucleus.

Also just wanna say thanks for the super detailed issue report, it makes my life so much easier when all the information is provided up front 😸

from nucleus.

@MarshallOfSound I tried to update nucleus-server (globally installed with yarn) but it seems the latest version available is 0.7.5 🤔. Am I missing something?

BTW, you're welcome for the detailed issue 👍. I deal with a lot of bug reports too, from random users just telling me "it's not working", so I learned to teach them how to do first-class reports.

PS: I looked at the changelog but didn't think that the last fix was applicable to my case, sorry!

from nucleus.

@bastientanesie Oh hm, we switched to deploying internally using docker I guess I forgot to publish 0.8.x with npm 😆

Let me see if I can deploy this from home, otherwise I'll do it tomorrow morning

from nucleus.

NP @MarshallOfSound, that happens ^^... I'll keep checking for the new version and I'll let you know if this fixes my problem 👌

from nucleus.

@bastientanesie 0.8.1 is now live on npm 🤔 😄

from nucleus.

Thanks @MarshallOfSound! I'll give it a try as soon as we get back our office internet connection 😅

from nucleus.

@MarshallOfSound it works! 🎉
I called /rest/admin/release-locks and was able to release the drafted version. Thank you for you support and quick answers! Cheers 😄

from nucleus.