Unexpected errors from attempted upgrade with the main branch

Have some unexpected errors from attempted upgrade with the main branch:

warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
[2/4] Fetching packages...
warning Pattern ["wrap-ansi@^7.0.0"] is trying to unpack in the same destination "/home/discourse/.cache/yarn/v6/npm-wrap-ansi-cjs-7.0.0-67e145cff510a6a6984bdf1152911d69d2eb9e43-integrity/node_modules/wrap-ansi-cjs" as pattern ["wrap-ansi-cjs@npm:wrap-ansi@^7.0.0"]. This could result in non-deterministic behavior, skipping.
error An unexpected error occurred: "https://registry.yarnpkg.com/ember-compatibility-helpers/-/ember-compatibility-helpers-1.2.6.tgz: Request failed \"500 Internal Server Error\"".
info If you think this is a bug, please open a bug report with the information provided in "/var/www/discourse/app/assets/javascripts/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

This was from UX upgrade page will try again from console to rebuild with the new commits.

New changes:

This sounds like a temporary issue on the yarn registry server.

I tried to find some information about it, but could not find anything.

Try again to see if it still happens. :thinking:


First rebuild crashed but second one completed.

The UX updater is going again now another warning:

WARNING: ember-test-selectors: You are using an unsupported ember-cli-babel version. data-test properties are not automatically stripped from your JS code.2

Annother #137 failure!!

Rebuild succeeded with another gb of memory, still used 83% of 2 instead of 92% of 1.

Took one more rebuild to finish everything went to 91.4% of 2gb memory with AMD.

Does adding a gig or two of swap help?

I don’t know what swap is or how to add that, but the extra memory seems to be sufficient all of the recent updates have worked.

Site doesn’t have any traffic for now but can do testing to help with checking to see if things will pass the tests necessary to become part of the stable version.

Server is a $14/month droplet now: 2 GB Memory / 1 AMD vCPU / 35 GB Disk / NYC1 - Ubuntu 23.10 x64 (url community.wombatarchitecture.com)

Glad that adding RAM helped. I don’t think percentage-used is much use as a measure, though. RAM usage is very elastic, because spare RAM will be used as filesystem cache.

The resource you’re aiming to have enough of is memory, and

  • memory=RAM+swap

So if adding RAM isn’t preferred, you can usually add swap instead, and that’s usually cheaper.

Adding RAM will increase costs significantly, so if you want to avoid that, one option is to upgrade temporarily to a larger-RAM machine and then migrate back. This costs you some minutes of downtime.


That makes sense, had just read 2GB is recommend as minimum for discourse. The graph is showing memory usage at steady 80% now, so just slight drop from 90% of half before added the second GB.

Will look to see about adding SWAP if that can help for other site is still at 1GB of ram.