-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure everything works after npm CouchDB upgrade #32
Comments
T minus 4️⃣ days... |
Thanks for letting us know! This should not be complicated, it's just a matter of..
|
@eridal thanks for summarizing that. Would you be willing to do that process? |
Yeah, I can take care. We could also use the opportunity to apply changes that require history reprocess, so two birds one stone.. but I don't want to rush those changes. Also fun fact they did not specify the exact date in UTC so we should stop the actions today:
|
oh another fun fact in UTC it already is 15/11 :)) |
Actions disabled |
Confirming npmjs finished the upgrade and sequence number changed. Later today I will leave the updater running, probably overnight. |
🍿 |
updater finished running, I'm wrapping up and will be publishing a new minor version during the next few minutes. Just for reference here are the steps needed to trigger a manual full reprocess: # allow cache, useful to save time on re-executions
mkdir -p .cache
export CACHE_DIR=.cache
export CACHE_READ=1
export CACHE_WRITE=1
# disable the timeout
export KILL_AFTER_MILLIS=Infinity
# clean all and execute
rm data/*
npm run update |
Update complete. Actions re-enabled but only every 12hs, just to make sure they work correctly. |
Nice! Thanks @eridal for taking care of that and for documenting the process. ⭐ |
Npm is going to upgrade the CouchDB and reset the sequence number as a result. Need to make sure that synchronization will continue to work after that.
This may require a manual update of the metadata or even a full rebuild.
See: https://github.blog/changelog/2021-09-08-npm-couchdb-upgrade-will-reset-sequence-number/
The text was updated successfully, but these errors were encountered: