Ember addons are resolving as incorrect peer dependencies. -- fixed by removing "content-tag@3.1.0": "patches/content-tag@3.1.0.patch",

Dev
7

Today I couldn’t run my dev environment because Discourse insisted on pnpm 9.15.5 and npm insisted on installing 10 something. ‘pnpm --version’ would tell me 10.x in my home directory, but would refuse to run in the discourse directory. It took all afternoon. I finally ended up uninstalling pnpm with npm and instead adding this to my update script:

  PNPM_VERSION=$(docker run discourse/base:release bash -c 'pnpm --version'|cut -d'v' -f2)
  echo "GOT PNPM version: $PNPM_VERSION"
  asdf install pnpm $PNPM_VERSION 2>&1|grep -v "already"
  asdf global pnpm $PNPM_VERSION 2>&1|grep -v "already"

That seems to work.

I tried using the docker development magic, but I can’t figure out how to pass ENV to it, and it doesn’t even have DISCOURSE_DEV_ALLOW_ANON_TO_IMPERSONATE set, so I couldn’t log in.

And now I’m getting this again:

 Error encountered while starting Sidekiq: [Discourse::Utils::CommandError] /home/pfaffman/src/discourse-r
epos/discourse/lib/discourse.rb:139:in `exec': renice: failed to set priority for 116553 (process ID): Permission denied

I think I fixed it before by editing . . . something.

OK. Here’s what to fix the nice thing. I swear I don’t see how I’m the only one hit by this.

In a file like

sudo nano /etc/security/limits.d/90-pfaffman-nice.conf

Add something like

pfaffman soft priority 5
pfaffman hard priority 5
1 Like