Hi @baris

Thanks for the reply. We're on Redis here instead of Mongo. Sorry, I should have specified.
I did the same thing in Redis, It appears that we had a lot of "blank" notes which were just timestamps - I've removed these (or rather, I converted them over to objects with a timestamp property) and it appears to have resolved this for now.

Not sure going by the timestamps exactly what caused these notes to be added however, but I didn't want to lose the fact that something happened at that point.

Thanks for the guideance

Just curious if this has alwys been NodeBb's flow or not.

The Upgrade docs say to checkout the branch (in this case v1.13.x) to do the upgrades, however, I can't do this as currently that branch is on a prerelease not production ready realease.

So should we always be upgrading to the release behind the latest release? in this case, with the release of 1.13.3, we should be upgrading to 1.12.x ?

@julian No worries. It's just slightly alarming upgrading a production instance only to find out you've accidentally gone all the way to a pre-release. We've only recently taken over our current NodeBB forum from someone else and I'm not familiar with the workflow yet.

I've made a note in our internal docs so it doesn't happen again. I was just wondering if I'd mis-read the docs or if that was the intended workflow.

Hey @baris

So we should be checking out tags, not branches, correct? In which case, the docs are out of date as they still recommend checking out the branches, not the tags (there is no v1.13.3 branch, unless i'm missing something).

something like git fetch --tags && git checkout v1.13.3 ?

If so, it might be worth updating the upgrade docs here: https://docs.nodebb.org/configuring/upgrade/ to include a mention of this so people don't accidentally pull down pre-release builds by following the guides (which I did).

Thanks

Just curious if this has alwys been NodeBb's flow or not.

The Upgrade docs say to checkout the branch (in this case v1.13.x) to do the upgrades, however, I can't do this as currently that branch is on a prerelease not production ready realease.

So should we always be upgrading to the release behind the latest release? in this case, with the release of 1.13.3, we should be upgrading to 1.12.x ?

Hi @baris

Thanks for the reply. We're on Redis here instead of Mongo. Sorry, I should have specified.
I did the same thing in Redis, It appears that we had a lot of "blank" notes which were just timestamps - I've removed these (or rather, I converted them over to objects with a timestamp property) and it appears to have resolved this for now.

Not sure going by the timestamps exactly what caused these notes to be added however, but I didn't want to lose the fact that something happened at that point.

Thanks for the guideance

Currently getting the following error when doing a large update.. 1.8.x -> 1.13.x

[2019/4/5] Update moderation notes to hashes...
    [              ] (100/185135) 0% Error occurred
Error occurred during upgrade: TypeError: Cannot create property 'timestamp' on number '1494309356813'

Any idea what might be causing this? - other than the fact that a number obviously won't have a timestamp property

Thanks