I have error when upgrade the latest discourse

[cmdntd]

I have error when upgrade the latest discourse:

Get:13 https://dl.yarnpkg.com/debian stable/main all Packages [10.9 kB]
Get:14 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [8,669 B]
Err:15 http://apt.postgresql.org/pub/repos/apt -pgdg Release
  404  Not Found [IP: 147.75.85.69 80]
Get:16 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.9 kB]
Get:17 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [318 kB]
Reading package lists...

I, [2024-05-19T08:52:40.856728 #1]  INFO -- : Terminating async processes
I, [2024-05-19T08:52:40.856789 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 34
I, [2024-05-19T08:52:40.856844 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 96
96:signal-handler (1716108760) Received SIGTERM scheduling shutdown...
2024-05-19 08:52:40.862 UTC [34] LOG:  received fast shutdown request
2024-05-19 08:52:40.865 UTC [34] LOG:  aborting any active transactions
2024-05-19 08:52:40.875 UTC [34] LOG:  background worker "logical replication launcher" (PID 49) exited with exit code 1
2024-05-19 08:52:40.879 UTC [44] LOG:  shutting down
96:M 19 May 2024 08:52:40.909 # User requested shutdown...
96:M 19 May 2024 08:52:40.909 * Saving the final RDB snapshot before exiting.
2024-05-19 08:52:40.957 UTC [34] LOG:  database system is shut down
96:M 19 May 2024 08:52:40.988 * DB saved on disk
96:M 19 May 2024 08:52:40.988 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && apt-get update failed with return #<Process::Status: pid 500 exit 100>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["apt-get update"]}
bootstrap failed with exit code 100
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
369a74ec6c3081026b2553dacc13d62c6d27881d8b5797fbec26c4d257afdc70

[cmdntd]

I have edit file.yml again for:

Discourse Chatbot (Now smarter than ChatGPT!*)

Summary A cloud chatbot adaptor for Discourse, currently supporting OpenAI Repository Link GitHub - merefield/discourse-chatbot: An AI bot with RAG capability for Topics and Chat in Discourse, currently powered by OpenAI Install Guide How to install plugins in Discourse Enjoying this plugin? Please it on GitHub ! [image] What is it? The original Discourse AI Chatbot! Converse with the bot in any Topic or Cha…

I think @merefield edit his plugin to remove this:

# Config GPT
#    - exec:
#        cd: $home
#        cmd:
#          - sudo apt-get install wget ca-certificates
#    - exec:
#        cd: $home
#        cmd:
#          - wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -
#    - exec:
#        cd: $home
#        cmd:
#          - sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ `lsb_release -cs`-pgdg main" >> /et>
#    - exec:
#        cd: $home
#        cmd:
#          - apt-get update
#    - exec:
#        cd: $home
#        cmd:
#          - apt-get -y install -y postgresql-server-dev-${PG_MAJOR}
#    - exec:
#        cd: $home/tmp
#        cmd:
#          - git clone https://github.com/neondatabase/pg_embedding.git
#    - exec:
#        cd: $home/tmp/pg_embedding
#        cmd:
#          - make PG_CONFIG=/usr/lib/postgresql/${PG_MAJOR}/bin/pg_config
#    - exec:
#        cd: $home/tmp/pg_embedding
#        cmd:
#          - make PG_CONFIG=/usr/lib/postgresql/${PG_MAJOR}/bin/pg_config install
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "create extension if not exists embedding;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "DROP INDEX IF EXISTS hnsw_index_on_chatbot_post_embeddings;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "DROP EXTENSION IF EXISTS embedding;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "ALTER EXTENSION vector UPDATE;"'
# End config GPT

But I’m not sure my old indexes still alive?

[merefield (Robert)]

I’m afraid it is impossivle for me to provide free support indefinitely for changes made months ago.

These lines have been unnecessary for a long time.

This technology has been so cutting edge and fast changing it was impractical to deliver it without breaking changes whilst providing it for free.

I have helped several users for free in private to work out issues with this change. However I do not have the time or resources to do that on my own for free any longer.

This change was clearly communicated at the time. Unfortunately the communications from topic are now cleared out on a monthly basis at the polite request of CDCK.

If you need me to take a deeper dive I can do so on contract.

[Moin]

@merefield

This change was clearly communicated at the time.

Did you also add the information to the first post? Then it could still be found in the edit history like these instructions