Nieuwste versie update fout

An error occurred while updating Discourse. Please check the logs below.

Starting update

******************************************************** *** Please be patient, next steps might take a while *** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn pid: 44 Waiting for Unicorn to reload. Waiting for Unicorn to reload.. Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Waiting for Unicorn to reload… Stopping 3 Unicorn worker(s), to free up memory Stopping job queue to reclaim memory, master pid is 62237 $ cd /var/www/discourse & git fetch --tags --prune-tags --prune --force From https://ghfast.top/https://github.com/discourse/discourse 78ee107fe..e8bf70510 tests-passed → origin/tests-passed + 5d4649970…b0d88ea96 my-pref-lang → origin/my-pref-lang (forced update) $ cd /var/www/discourse & git reset --hard HEAD@{upstream} Updating files: 28% (2/7) Updating files: 42% (3/7) Updating files: 57% (4/7) Updating files: 71% (5/7) Updating files: 85% (6/7) Updating files: 100% (7/7) Updating files: 100% (7/7), done. HEAD is now at e8bf70510 FEATURE: create new topic while viewing restricted category or tag (#33495) $ bundle install --retry 3 --jobs 4 Bundle complete! 160 Gemfile dependencies, 207 gems now installed. Gems in the groups ‘test’ and ‘development’ were not installed. Bundled gems are installed into ./vendor/bundle 3 installed gems you directly depend on are looking for funding. Run `bundle fund` for details $ if [ -f yarn.lock ]; then yarn install; else CI=1 pnpm install; fi Scope: all 16 workspace projects Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +6 ++++++ ERR_PNPM_FETCH_404 GET https://registry.npmmirror.com/babel-plugin-ember-template-compilation/-/babel-plugin-ember-template-compilation-3.0.0.tgz: Not Found - 404 No authorization header was set for the request. Docker Manager: FAILED TO UPGRADE #<RuntimeError: RuntimeError> /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:211:in `run’ /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:102:in `upgrade’ /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in ’ /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork’ /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/commands/runner/runner_command.rb:44:in `load’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/commands/runner/runner_command.rb:44:in `block in perform’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2/lib/active_support/execution_wrapper.rb:91:in `wrap’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/commands/runner/runner_command.rb:70:in `conditional_executor’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/commands/runner/runner_command.rb:43:in `perform’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/command.rb:28:in `run’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/invocation.rb:127:in `invoke_command’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/command/base.rb:178:in `invoke_command’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor.rb:538:in `dispatch’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/command/base.rb:73:in `perform’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/command.rb:65:in `block in invoke’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/command.rb:143:in `with_argv’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/command.rb:63:in `invoke’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-8.0.2/lib/rails/commands.rb:18:in `’ /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `require’ /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require’ bin/rails:18:in `’ Spinning up 3 Unicorn worker(s) that were stopped initially

Can you rebuild from the console?

Probably related to: Bundling more popular plugins with Discourse core

I am currently on the latest version, but an updated version was released an hour ago. When I tried to install it using the Taobao source, it showed that the file could not be found.

1 like

Hallo, voert u een standaardinstallatie uit?

1 like

It looks like we lost some important information during the auto-translator here (cc @nat). Here’s the error which @cshll shared:

ERR_PNPM_FETCH_404 GET https://registry.npmmirror.com/babel-plugin-ember-template-compilation/-/babel-plugin-ember-template-compilation-3.0.0.tgz: Not Found - 404 No authorization header was set for the request. Docker Manager: FAILED

The problem seems to be with the NPM chinese mirror (set by web.china.template.yml). If I visit the same URL on the main NPMJS site, it works fine

https://registry.npmjs.com/babel-plugin-ember-template-compilation/-/babel-plugin-ember-template-compilation-3.0.0.tgz

Not really sure where to go from here. Perhaps you could try contacting npmmirror.com to report the missing package? :thinking:

1 like

The indicator says that the translation is outdated

Isn’t this the known problem that edits are not re-translated?

@Lhc_fl had je problemen met de update? Voor het geval dat je ook de taobao mirror gebruikt.

2 likes

Ik heb Taobao Mirror niet gebruikt voor discussies, maar voor zover ik weet, kan Taobao Mirror vergelijkbare problemen hebben omdat de mirroring niet voldoende is.

Ik heb in feite vergelijkbare situaties gezien in andere projecten (fouten in electron), en ik denk dat de enige beste oplossing is om een server buiten China te gebruiken, of een wereldwijde proxy in te schakelen. Omgaan met de problemen veroorzaakt door GFW is vermoeiend.

4 likes