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) https://github.com/merefield/discourse-chatbot/actions/runs/8441786001/job/23121732154?pr=81 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: https://github.com/merefield/discourse-chatbot/actions/runs/8440497064/job/23118126077 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? Gemfile.lock bf35928a1 openssl (3.2.0)

Thanks! [image] David Taylor: Why are you adding that gem via a plugin? Looks like Discourse core already has it? 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?

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

That’s all going through nicely now!: https://github.com/merefield/discourse-chatbot/actions/runs/8442671263/job/23140789511?pr=81 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.

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

Development

merefield (Robert) March 26, 2024, 8:50pm 6

no issues, thanks very much David!

Topic		Replies	Views
Notes about Installing Discourse on Ubuntu 20.04 Development	2	2398	May 6, 2022
Getting error at dev build in step "bundle install" Self-hosting	3	2623	May 10, 2022
Cannot install custom SSL new_file: no such file Product Support	6	2084	March 20, 2025
Dev environment setup failed on bundle install Self-hosting	2	2095	September 10, 2022
Rebuild failed - with exit code 128 (fix: SSL cert for plugin domain needed updating) Self-hosting	3	473	May 18, 2024

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

Related topics