-
Notifications
You must be signed in to change notification settings - Fork 20
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
tutor-forum upgrade to Ruby 3.3 #33
Comments
@ghassanmas , will you be able to apply and test the Ruby 3.3 upgrade? |
@kdmccormick yes will do, hopefuly in frinday by the end of this week. |
@kdmccormick looking now again at it, I can start with Ruby 3.3, but it would use old mongo verison, given tutor nightly still not updated to mongo 7, so if I understnad correcly I shall wait until tutor nightly is using mongo 7 (overhangio/tutor#1020 ) ? is that correct?. Otherwise I would be testing Ruby 3.3 with Mongo |
Good point @ghassanmas , it would fair for you to wait until Tutor upgrades to Mongo 7 first. |
@ghassanmas Hi, the mongo PR has been merged to nightly. You are all set for this. Thanks |
@DawoudSheraz thanks for the update, I think I'll persume/start next Thursday or Friday, hopefully PR will be ready to review by the end of this week, given Redwood cut branch is soon. |
I am not sure which Gemfile or Gemfile.lock, it's suppsoe to be used for 3.3. However now I can see Gemfile is pinned for ruby 3.1, while Gemfile3 for 3.0. So I though given 3.3. is cloaser to 3.1, Gemfile is suppose to be used, but it didn't work because it's missing a library, thus I openedx a PR upstream to add it |
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
getting rid of dockerize might resolve #33 and provide other solution for #35 dockerize is used for waiting for other services, in order replicate it's effect, we set `MONGOID_TIMEOUT` 600 second for mongodb, related upstream PR: - openedx/cs_comments_service/pull/432
From https://discuss.openedx.org/t/tutor-cs-comment-service-mongo-and-ruby-upgrade/12472 :
The text was updated successfully, but these errors were encountered: