Skip to content

Conversation

@kjriga
Copy link
Contributor

@kjriga kjriga commented Oct 17, 2025

After switching to Github actions, some things were broken. This covers fixing up various missing dependencies, failing specs, etc to get a green run.

@kjriga kjriga marked this pull request as ready for review October 17, 2025 19:52
@kjriga kjriga changed the title Run migrations on github actions Fix Github actions test runs Oct 20, 2025
@kjriga kjriga force-pushed the fix-github-actions-workflow branch from 1afa9d6 to b1bfa0b Compare October 20, 2025 16:38
@kjriga kjriga force-pushed the fix-github-actions-workflow branch 3 times, most recently from acdd1e3 to 33058e9 Compare October 21, 2025 15:57
@kjriga
Copy link
Contributor Author

kjriga commented Oct 21, 2025

Just an update, my local spec suite passes. Figuring out github actions now.

@kjriga kjriga force-pushed the fix-github-actions-workflow branch from f2fca82 to 3f2332d Compare October 21, 2025 16:28
Comment on lines +23 to +28
# Standard library gems that became separate in Ruby 3.4+
gem 'bigdecimal'
gem 'mutex_m'
gem 'drb'
gem 'csv'
gem 'ostruct'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't love this, particularly because I don't think this gem actually uses any of these itself. (Outside of ostruct in a couple of tests.)

We should probably look at making these gem dependencies of the appropriate Solidus gems that need them.

But since this is just the Gemfile, I'm okay with this for now.

@kjriga kjriga force-pushed the fix-github-actions-workflow branch 2 times, most recently from f2faecd to 3120fbc Compare October 21, 2025 17:33
@kjriga kjriga force-pushed the fix-github-actions-workflow branch 4 times, most recently from 689365f to 6199e11 Compare October 21, 2025 19:10
Copy link
Member

@adammathys adammathys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One tiny comment about tweaking the Rails versions in our matrix, but otherwise good to go I think.

Copy link
Member

@jarednorman jarednorman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks all reasonable to me pending Adam's comments being addressed.

Since this gem doesn't support Solidus 4+ yet.
To fix
`uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger
(NameError)`
I got errors that these were not recognized.
To fix an error we got,
```
Error loading the 'sqlite3' Active Record adapter. Missing a gem it
depends on? can't activate sqlite3 (~> 1.4), already activated
sqlite3-2.7.4-arm64-darwin.  Make sure all dependencies are added to
Gemfile.
```

The error message shows the version it was erroring to activate. Locking
it to that version and `bundle update sqlite3` fixed the issue.
Because we were build_stubbed'ing in these, the orders are missing some
details that cause errors, such as 'no 'abbr' for nil'.
On the version we were using we got 'stack level too deep' spec
failures. Locking it to 0.6.0 in the meantime solves this problem.
To fix
```
/home/runner/work/solidus_tracking/solidus_tracking/vendor/bundle/ruby/3.1.0/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:12:in `<module:LoggerThreadSafeLevel>': uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)

    Logger::Severity.constants.each do |severity|
    ^^^^^^
```

This could be removed once we're solely testing on Rails 7.1+, but
because this gem is a bit outdated (Solidus < 4) we need it for now.
The spec failures was showing extra callbacks being fired.
@kjriga kjriga force-pushed the fix-github-actions-workflow branch from 6199e11 to afbfdf3 Compare October 27, 2025 16:16
@adammathys adammathys merged commit 946b1f1 into solidusio-contrib:master Oct 27, 2025
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants