Hi,
I performed an upgrade from v.2.8.14 to v3.0.0, using this process:
docker exec -it app rails runner "Discourse.enable_readonly_mode(Discourse::USER_READONLY_MODE_KEY)"
cd /var/discourse
git pull
./launcher rebuild app --docker-args --net=host --skip-mac-address
docker exec -it app rails runner "Discourse.disable_readonly_mode(Discourse::USER_READONLY_MODE_KEY)"
Early on in the upgrade, I saw this bundler error:
remote: Enumerating objects: 18, done.
remote: Counting objects: 100% (18/18), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 18 (delta 10), reused 17 (delta 10), pack-reused 0
Unpacking objects: 100% (18/18), 5.00 KiB | 512.00 KiB/s, done.
From https://github.com/discourse/discourse_docker
e6cb71c..1de36f6 main -> origin/main
+ 2e142d4...8ca4f38 ruby-3.2 -> origin/ruby-3.2 (forced update)
Updating e6cb71c..1de36f6
Fast-forward
image/discourse_dev/Dockerfile | 2 ++
1 file changed, 2 insertions(+)
x86_64 arch detected.
2.0.20220818-0047: Pulling from discourse/base
Digest: sha256:7734701087766821ffb2ddcef423754798bd345c2ac0d550131c6e6905c268e8
Status: Image is up to date for discourse/base:2.0.20220818-0047
docker.io/discourse/base:2.0.20220818-0047
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 60 app
app
2.0.20220818-0047: Pulling from discourse/base
Digest: sha256:7734701087766821ffb2ddcef423754798bd345c2ac0d550131c6e6905c268e8
Status: Image is up to date for discourse/base:2.0.20220818-0047
docker.io/discourse/base:2.0.20220818-0047
/usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2023-01-11T22:11:31.990663 #1] INFO -- : Reading from stdin
I, [2023-01-11T22:11:32.008485 #1] INFO -- : File > /etc/service/redis/run chmod: +x chown:
I, [2023-01-11T22:11:32.014899 #1] INFO -- : File > /etc/service/redis/log/run chmod: +x chown:
I, [2023-01-11T22:11:32.021283 #1] INFO -- : File > /etc/runit/3.d/10-redis chmod: +x chown:
I, [2023-01-11T22:11:32.023029 #1] INFO -- : Replacing daemonize yes with in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.023985 #1] INFO -- : Replacing (?-mix:^pidfile.*$) with in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.024780 #1] INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2023-01-11T22:11:32.030179 #1] INFO -- :
I, [2023-01-11T22:11:32.030827 #1] INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.031567 #1] INFO -- : Replacing (?-mix:^bind .*$) with in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.032543 #1] INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.033375 #1] INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.034068 #1] INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2023-01-11T22:11:32.034790 #1] INFO -- : > echo redis installed
I, [2023-01-11T22:11:32.038297 #1] INFO -- : redis installed
I, [2023-01-11T22:11:32.038759 #1] INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2023-01-11T22:11:32.044082 #1] INFO -- : logfile ""
I, [2023-01-11T22:11:32.044505 #1] INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-11T22:11:32.046813 #1] INFO -- : > sleep 10
19:C 11 Jan 2023 22:11:32.056 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
19:C 11 Jan 2023 22:11:32.056 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=19, just started
19:C 11 Jan 2023 22:11:32.056 # Configuration loaded
19:M 11 Jan 2023 22:11:32.057 * monotonic clock: POSIX clock_gettime
19:M 11 Jan 2023 22:11:32.058 * Running mode=standalone, port=6379.
19:M 11 Jan 2023 22:11:32.058 # Server initialized
19:M 11 Jan 2023 22:11:32.059 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
19:M 11 Jan 2023 22:11:32.059 * Loading RDB produced by version 6.2.6
19:M 11 Jan 2023 22:11:32.059 * RDB age 7 seconds
19:M 11 Jan 2023 22:11:32.059 * RDB memory usage when created 4.42 Mb
19:M 11 Jan 2023 22:11:32.074 # Done loading RDB, keys loaded: 2003, keys expired: 0.
19:M 11 Jan 2023 22:11:32.074 * DB loaded from disk: 0.015 seconds
19:M 11 Jan 2023 22:11:32.074 * Ready to accept connections
I, [2023-01-11T22:11:42.050045 #1] INFO -- :
I, [2023-01-11T22:11:42.050510 #1] INFO -- : > thpoff echo "thpoff is installed!"
I, [2023-01-11T22:11:42.055661 #1] INFO -- : thpoff is installed!
I, [2023-01-11T22:11:42.056251 #1] INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end'
I, [2023-01-11T22:11:42.170880 #1] INFO -- :
I, [2023-01-11T22:11:42.171305 #1] INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2023-01-11T22:11:42.291228 #1] INFO -- :
I, [2023-01-11T22:11:42.291649 #1] INFO -- : > /usr/local/bin/ruby -e 'if (ENV["DISCOURSE_CDN_URL"] || "")[0..1] == "//"; puts "Aborting! CDN must have a protocol specified. Once fixed you should rebake your posts now to correct all posts."; exit 1; end'
I, [2023-01-11T22:11:42.408939 #1] INFO -- :
I, [2023-01-11T22:11:42.409402 #1] INFO -- : > rm -f /etc/cron.d/anacron
I, [2023-01-11T22:11:42.413262 #1] INFO -- :
I, [2023-01-11T22:11:42.417373 #1] INFO -- : File > /etc/cron.d/anacron chmod: chown:
I, [2023-01-11T22:11:42.423865 #1] INFO -- : File > /etc/runit/1.d/copy-env chmod: +x chown:
I, [2023-01-11T22:11:42.430470 #1] INFO -- : File > /etc/service/unicorn/run chmod: +x chown:
I, [2023-01-11T22:11:42.436838 #1] INFO -- : File > /etc/service/nginx/run chmod: +x chown:
I, [2023-01-11T22:11:42.443359 #1] INFO -- : File > /etc/runit/3.d/01-nginx chmod: +x chown:
I, [2023-01-11T22:11:42.449717 #1] INFO -- : File > /etc/runit/3.d/02-unicorn chmod: +x chown:
I, [2023-01-11T22:11:42.450156 #1] INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-01-11T22:11:42.453602 #1] INFO -- : > cd /var/www/discourse && git reset --hard
46:C 11 Jan 2023 22:11:42.462 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
46:C 11 Jan 2023 22:11:42.462 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=46, just started
46:C 11 Jan 2023 22:11:42.462 # Configuration loaded
46:M 11 Jan 2023 22:11:42.463 * monotonic clock: POSIX clock_gettime
46:M 11 Jan 2023 22:11:42.464 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
46:M 11 Jan 2023 22:11:42.464 # Failed listening on port 6379 (TCP), aborting.
Updating files: 100% (31436/31436), done.
I, [2023-01-11T22:11:46.521814 #1] INFO -- : HEAD is now at 44c53cb3 DEV: Update internal `package.json` metadata (#17978)
I, [2023-01-11T22:11:46.522342 #1] INFO -- : > cd /var/www/discourse && git clean -f
I, [2023-01-11T22:11:46.687168 #1] INFO -- :
I, [2023-01-11T22:11:46.687649 #1] INFO -- : > cd /var/www/discourse && git remote set-branches --add origin main
I, [2023-01-11T22:11:46.693562 #1] INFO -- :
I, [2023-01-11T22:11:46.694073 #1] INFO -- : > cd /var/www/discourse && git remote set-branches origin stable
I, [2023-01-11T22:11:46.700456 #1] INFO -- :
I, [2023-01-11T22:11:46.700906 #1] INFO -- : > cd /var/www/discourse && git fetch --depth 1 origin stable
From https://github.com/discourse/discourse
* branch stable -> FETCH_HEAD
* [new branch] stable -> origin/stable
I, [2023-01-11T22:11:51.425872 #1] INFO -- :
I, [2023-01-11T22:11:51.426067 #1] INFO -- : > cd /var/www/discourse && git checkout stable
Switched to a new branch 'stable'
I, [2023-01-11T22:11:52.937277 #1] INFO -- : Branch 'stable' set up to track remote branch 'stable' from 'origin'.
I, [2023-01-11T22:11:52.937763 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-01-11T22:11:52.942993 #1] INFO -- :
I, [2023-01-11T22:11:52.943124 #1] INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-01-11T22:11:52.947751 #1] INFO -- :
I, [2023-01-11T22:11:52.948175 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-01-11T22:11:52.952909 #1] INFO -- :
I, [2023-01-11T22:11:52.953419 #1] INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-01-11T22:11:52.958174 #1] INFO -- :
I, [2023-01-11T22:11:52.958683 #1] INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-01-11T22:11:52.962908 #1] INFO -- :
I, [2023-01-11T22:11:52.963002 #1] INFO -- : > cd /var/www/discourse && mkdir -p /shared/log/rails
I, [2023-01-11T22:11:52.967906 #1] INFO -- :
I, [2023-01-11T22:11:52.968059 #1] INFO -- : > cd /var/www/discourse && bash -c "touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2023-01-11T22:11:52.974492 #1] INFO -- :
I, [2023-01-11T22:11:52.974636 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log"
I, [2023-01-11T22:11:52.981277 #1] INFO -- :
I, [2023-01-11T22:11:52.981426 #1] INFO -- : > cd /var/www/discourse && bash -c "mkdir -p /shared/{uploads,backups}"
I, [2023-01-11T22:11:52.988544 #1] INFO -- :
I, [2023-01-11T22:11:52.988650 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-01-11T22:11:52.995236 #1] INFO -- :
I, [2023-01-11T22:11:52.995665 #1] INFO -- : > cd /var/www/discourse && bash -c "mkdir -p /shared/tmp/{backups,restores}"
I, [2023-01-11T22:11:53.002123 #1] INFO -- :
I, [2023-01-11T22:11:53.002620 #1] INFO -- : > cd /var/www/discourse && bash -c "ln -s /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-01-11T22:11:53.008952 #1] INFO -- :
I, [2023-01-11T22:11:53.009509 #1] INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2023-01-11T22:11:53.023178 #1] INFO -- :
I, [2023-01-11T22:11:53.023305 #1] INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2023-01-11T22:11:53.028782 #1] INFO -- :
I, [2023-01-11T22:11:53.029010 #1] INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2023-01-11T22:11:53.029663 #1] INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-01-11T22:11:55.157643 #1] INFO -- :
I, [2023-01-11T22:11:55.157770 #1] INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-chat-integration.git
Cloning into 'discourse-chat-integration'...
I, [2023-01-11T22:11:56.384108 #1] INFO -- :
I, [2023-01-11T22:11:56.384233 #1] INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/angusmcleod/discourse-events.git
Cloning into 'discourse-events'...
I, [2023-01-11T22:11:57.450187 #1] INFO -- :
I, [2023-01-11T22:11:57.450656 #1] INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-01-11T22:11:57.455146 #1] INFO -- :
I, [2023-01-11T22:11:57.455633 #1] INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2023-01-11T22:11:57.458991 #1] INFO -- :
I, [2023-01-11T22:11:57.459528 #1] INFO -- : > mkdir -p /var/nginx/cache
I, [2023-01-11T22:11:57.463224 #1] INFO -- :
I, [2023-01-11T22:11:57.464140 #1] INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-01-11T22:11:57.464741 #1] INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2023-01-11T22:11:57.465363 #1] INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-11T22:11:57.465927 #1] INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2023-01-11T22:11:57.466452 #1] INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-01-11T22:11:57.466894 #1] INFO -- : > echo "done configuring web"
I, [2023-01-11T22:11:57.469846 #1] INFO -- : done configuring web
I, [2023-01-11T22:11:57.470392 #1] INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2023-01-11T22:11:58.205287 #1] INFO -- : Successfully installed bundler-2.4.1
1 gem installed
I, [2023-01-11T22:11:58.205417 #1] INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2023-01-11T22:12:04.207590 #1] INFO -- :
I, [2023-01-11T22:12:04.208261 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --production --frozen-lockfile && yarn cache clean'
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".
warning "eslint-config-discourse > eslint-plugin-lodash@7.1.0" has unmet peer dependency "lodash@>=4".
I, [2023-01-11T22:13:13.024109 #1] INFO -- : yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ yarn --cwd app/assets/javascripts/discourse $(node -e 'if(JSON.parse(process.env.npm_config_argv).original.includes(`--frozen-lockfile`)){console.log(`--frozen-lockfile`)}')
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 38.23s.
Done in 61.96s.
yarn cache v1.22.19
success Cleared cache.
Done in 6.12s.
I, [2023-01-11T22:13:13.029790 #1] INFO -- : > sed -i '/add_header Referrer-Policy/d' /etc/nginx/conf.d/discourse.conf
I, [2023-01-11T22:13:13.046717 #1] INFO -- :
I, [2023-01-11T22:13:13.047508 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'
[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local deployment 'true'`, and stop using this flag
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'test development'`, and stop using this flag
Bundler::PathError: The path `/var/www/discourse/vendor/bundle/ruby/2.7.0/bundler/gems/web-push-369df8f475a4` does not exist.
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/source/path.rb:209:in `load_spec_files'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/source/git.rb:205:in `load_spec_files'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/source/path.rb:107:in `local_specs'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/source/git.rb:172:in `specs'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/lazy_specification.rb:86:in `materialize_for_installation'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:195:in `map!'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:195:in `specs_for_dependency'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:33:in `block in for'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:22:in `loop'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:22:in `for'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/spec_set.rb:79:in `materialize'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/definition.rb:198:in `missing_specs'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/definition.rb:202:in `missing_specs?'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/installer.rb:253:in `resolve_if_needed'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/installer.rb:82:in `block in run'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/process_lock.rb:12:in `block in lock'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/process_lock.rb:9:in `open'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/process_lock.rb:9:in `lock'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/installer.rb:71:in `run'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/installer.rb:23:in `install'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/cli/install.rb:62:in `run'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:260:in `block in install'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/settings.rb:131:in `temporary'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:259:in `install'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:34:in `dispatch'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:28:in `start'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/exe/bundle:45:in `block in <top (required)>'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.4.1/exe/bundle:33:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
I, [2023-01-11T22:14:09.288884 #1] INFO -- : Running `bundle install --deployment --jobs 4 --retry 3 --verbose --without "test" "development"` with bundler 2.4.1
Frozen, using resolution from the lockfile
The definition is missing dependencies, failed to resolve & materialize locally (https://github.com/xfalcox/web-push (at openssl-3-compat@369df8f) is not yet checked out. Run `bundle install` first.)
Frozen, using resolution from the lockfile
HTTP GET https://index.rubygems.org/versions
HTTP 206 Partial Content https://index.rubygems.org/versions
HTTP GET https://index.rubygems.org/versions
HTTP 200 OK https://index.rubygems.org/versions
Fetching gem metadata from https://rubygems.org/
Looking up gems ["actionmailer", "actionpack", "actionview", "actionview_precompiler", "active_model_serializers", "activejob", "activemodel", "activerecord", "activesupport", "addressable", "annotate", "ast", "aws-eventstream", "aws-partitions", "aws-sdk-core", "aws-sdk-kms", "aws-sdk-s3", "aws-sdk-sns", "aws-sigv4", "better_errors", "binding_of_caller", "bootsnap", "builder", "bullet", "byebug", "capybara", "cbor", "certified", "cgi", "chunky_png", "coderay", "colored2", "concurrent-ruby", "connection_pool", "cose", "cppjieba_rb", "crack", "crass", "css_parser", "debug_inspector", "diff-lcs", "diffy", "digest", "discourse-fonts", "discourse-seed-fu", "discourse_dev_assets", "docile", "ecma-re-validator", "email_reply_trimmer", "erubi", "excon", "execjs", "exifr", "fabrication", "faker", "fakeweb", "faraday", "faraday-net_http", "faraday-retry", "fast_blank", "fast_xs", "fastimage", "ffi", "fspath", "gc_tracer", "globalid", "guess_html_encoding", "hana", "hashdiff", "hashie", "highline", "hkdf", "htmlentities", "http_accept_language", "i18n", "image_optim", "image_size", "in_threads", "jmespath", "json", "json-schema", "json_schemer", "jwt", "kgio", "libv8-node", "listen", "literate_randomizer", "lograge", "logstash-event", "logstash-logger", "logster", "loofah", "lru_redux", "lz4-ruby", "matrix", "maxminddb", "memory_profiler", "message_bus", "method_source", "mini_mime", "mini_portile2", "mini_racer", "mini_scheduler", "mini_sql", "mini_suffix", "minitest", "mocha", "msgpack", "multi_json", "multi_xml", "mustache", "net-http", "net-imap", "net-pop", "net-protocol", "net-smtp", "nio4r", "nokogiri", "oauth", "oauth-tty", "oauth2", "oj", "omniauth", "omniauth-facebook", "omniauth-github", "omniauth-google-oauth2", "omniauth-oauth", "omniauth-oauth2", "omniauth-twitter", "openssl", "openssl-signature_algorithm", "optimist", "parallel", "parallel_tests", "parser", "pg", "prettier_print", "progress", "pry", "pry-byebug", "pry-rails", "public_suffix", "puma", "r2", "racc", "rack", "rack-mini-profiler", "rack-protection", "rack-test", "rails-dom-testing", "rails-html-sanitizer", "rails_failover", "rails_multisite", "railties", "rainbow", "raindrops", "rake", "rb-fsevent", "rb-inotify", "rbtrace", "rchardet", "redis", "redis-namespace", "regexp_parser", "request_store", "rexml", "rinku", "rotp", "rqrcode", "rqrcode_core", "rspec", "rspec-core", "rspec-expectations", "rspec-html-matchers", "rspec-mocks", "rspec-rails", "rspec-support", "rss", "rswag-specs", "rubocop", "rubocop-ast", "rubocop-discourse", "rubocop-rspec", "ruby-prof", "ruby-progressbar", "ruby-readability", "ruby2_keywords", "rubyzip", "sanitize", "sassc", "sassc-rails", "selenium-webdriver", "shoulda-matchers", "sidekiq", "simplecov", "simplecov-html", "simplecov_json_formatter", "snaky_hash", "sprockets", "sprockets-rails", "sshkey", "stackprof", "syntax_tree", "syntax_tree-disable_ternary", "test-prof", "thor", "tilt", "timeout", "tzinfo", "uglifier", "unf", "unf_ext", "unicode-display_width", "unicorn", "uniform_notifier", "uri", "uri_template", "version_gem", "webdrivers", "webmock", "webrick", "websocket", "xorcist", "xpath", "yaml-lint", "zeitwerk"]
HTTP GET https://index.rubygems.org/info/actionmailer
HTTP GET https://index.rubygems.org/info/actionpack
[....]
Despite this, it carried on right through to the end of the upgrade, applying all the database migrations cleanly, and I was able to login to my Discourse instance and see that the version 3.0.0 was shown. I could not visually identify any anomalies, which was a surprise given the dependency error.
I rolled back my change in the meantime, as I’d like to get clarification that this error is known/expected/surprising but nothing to worry about?
I didn’t grab all the upgrade output, but the rest that I saw looked ‘normal’ having run many upgrades like this in the past. I do have the DB migration log steps saved if you would like to see them, but like I said, they applied cleanly.
Thanks!