-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Startup problem with Ruby 3.3 #241
Comments
So, the fix I can see is to explicitely passing the parameters to the method: |
ngiger
added a commit
that referenced
this issue
Feb 8, 2024
ngiger
added a commit
to ngiger/oddb.org
that referenced
this issue
Feb 8, 2024
ngiger
added a commit
to ngiger/oddb.org
that referenced
this issue
Feb 8, 2024
ngiger
added a commit
to ngiger/oddb.org
that referenced
this issue
Feb 8, 2024
zdavatz
added a commit
that referenced
this issue
Feb 8, 2024
(#241): Fix and test for exfactory and public prices
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to get fast a reliable environment for oddb developers I documented my use https://devenv.sh/ in
https://github.com/ngiger/oddb.org/blob/master/devenv.README.md
This allowed me to fix the few issues when moving to ruby 3.3 and testing them via unit test for the involved components like odba, sbsm, htmlgrid, ydbi, yus, migel and oddb.org.
Big drawback for this setup is that NixOS only provides builds for postgres 12 upto 16. Starting under Postgres 16 breaks at the line in
src/util/oddb_app.rb
with the content@system = ODBA.cache.fetch_named('oddbapp', self){ OddbPrevalence.new }
.I have not digged further into this problem, but it could be related to the fact that table no longer are able to contain columns named OID.
But ch.oddb.org (and my test installation oddb-ci2) runs with postgres 10.
Therefore I installed ruby-3.3 on oddb-ci2 and pulled all my changes from https://github.com/ngiger/oddb.org. I am starting the service manually
sudo -u apache bundle-330 exec rackup --host 192.168.0.75 -p 8012 --quiet
. The service startup up without any apparent failure but when I visit with my browser http://192.168.0.75:8012/ I see the error messageand in the console I see
I have no idea, why I get into this error
The text was updated successfully, but these errors were encountered: