Skip to content
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

Open
zarianec opened this issue Sep 9, 2021 · 11 comments
Open

Make sure everything works after npm CouchDB upgrade #32

zarianec opened this issue Sep 9, 2021 · 11 comments

Comments

@zarianec
Copy link
Collaborator

zarianec commented Sep 9, 2021

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/

@zarianec zarianec self-assigned this Sep 9, 2021
@zeke
Copy link
Member

zeke commented Sep 11, 2021

The npm registry will upgrade its public CouchDB instance on September 15, 2021. As part of this upgrade, we will promote a new CouchDB replica to become our new public CouchDB instance, https://replicate.npmjs.com. This upgrade will reset the CouchDB sequence number.

T minus 4️⃣ days...

@eridal
Copy link
Contributor

eridal commented Sep 12, 2021

Thanks for letting us know!

This should not be complicated, it's just a matter of..

  1. Stop github actions
  2. Wait till sequence is updated..
  3. Clone the repo, remove the metadata, re-run the updater locally
  4. Commit the new metadata and packages, along with npm version minor
  5. Start github actions

@zeke
Copy link
Member

zeke commented Sep 14, 2021

@eridal thanks for summarizing that. Would you be willing to do that process?

@eridal
Copy link
Contributor

eridal commented Sep 15, 2021

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:

The npm registry will upgrade its public CouchDB instance on September 15, 2021. As part of this upgrade, we will...

@eridal
Copy link
Contributor

eridal commented Sep 15, 2021

oh another fun fact in UTC it already is 15/11 :))

@eridal
Copy link
Contributor

eridal commented Sep 15, 2021

Actions disabled

@eridal
Copy link
Contributor

eridal commented Sep 16, 2021

Confirming npmjs finished the upgrade and sequence number changed. Later today I will leave the updater running, probably overnight.

@zeke
Copy link
Member

zeke commented Sep 17, 2021

🍿

@eridal
Copy link
Contributor

eridal commented Sep 17, 2021

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

@eridal
Copy link
Contributor

eridal commented Sep 18, 2021

Update complete. Actions re-enabled but only every 12hs, just to make sure they work correctly.

@zeke
Copy link
Member

zeke commented Sep 19, 2021

Nice! Thanks @eridal for taking care of that and for documenting the process. ⭐

@zarianec zarianec removed their assignment Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants