Failing tests: i've not even dared to rebuild atm

My github backend tests are failing with this:

LoadError: libssl.so.1.1: cannot open shared object file: No such file or directory - /__w/discourse-chatbot/discourse-chatbot/vendor/bundle/ruby/3.2.0/gems/openssl-3.2.0/lib/openssl.so (LoadError)

Run if ! bin/rails zeitwerk:check --trace; then

[21](https://github.com/merefield/discourse-chatbot/actions/runs/8441786001/job/23121732154?pr=81#step:23:21)

[21](https://github.com/merefield/discourse-chatbot/actions/runs/8441786001/job/23121732154?pr=81#step:23:22)rails aborted!

[22](https://github.com/merefield/discourse-chatbot/actions/runs/8441786001/job/23121732154?pr=81#step:23:23)LoadError: libssl.so.1.1: cannot open shared object file: No such file or directory - /__w/discourse-chatbot/discourse-chatbot/vendor/bundle/ruby/3.2.0/gems/openssl-3.2.0/lib/openssl.so (LoadError)
  • I’ve updated gem dependencies, but still the error persists.
  • I’m using the core plugin workflow config now, but still the error persists.

It began with this seemingly irrelevant commit:

Has anyone else hit this yet, it just started happening today?

We’re working on upgrading our base docker image to use the latest version of Debian, so that could be the cause (Upgrade Debian to Bookworm · discourse/discourse_docker@23e7b55 · GitHub).

i’ve not even dared to rebuild atm

This new base image is currently only being used in CI. It won’t be used by ./launcher rebuild until the image tag is updated here

add openssl gem

Why are you adding that gem via a plugin? Looks like Discourse core already has it?

3 Likes

Thanks!

That was a jerk reaction within the PR to see if I could fix, but didn’t resolve the issue. I’ll row that back, thanks! (reverted!)

However, switching to the core plugin workflow is a nice simplification so it’s far from wasted effort.

Will this be resolved by some ongoing work with the base image?

3 Likes

Yup we’re seeing similar errors across multiple plugins, so we’ll get it sorted ASAP :+1:

3 Likes

no issues, thanks very much David!

4 Likes

That’s all going through nicely now!:

thanks for resolving!

I believe it was this commit? Revert "Upgrade Debian to Bookworm" (#788) · discourse/discourse_docker@fcc6326 · GitHub

Good luck with the upgrade.

2 Likes