Skip to content
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

chore: Install ostruct alongside virtus #404

Closed
wants to merge 6 commits into from
Closed

Conversation

scottmries
Copy link
Contributor

Closes #402

Background: ostruct (aka OpenStruct) is part of Ruby's standard library, but it's being pulled out of the standard library and into a gem. For now, both versions are available. If you require the version from the standard library, Ruby 3.3.5 will print a warning urging you to switch over to using the gem version. In Ruby 3.5.0, the standard library version will not exist.

The warning looks like this:

/Users/mjacobson/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/virtus-2.0.0/lib/virtus.rb:1: warning: /Users/mjacobson/.rbenv/versions/3.3.5/lib/ruby/3.3.0/ostruct.rb was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add ostruct to your Gemfile or gemspec to silence this warning.
Also please contact the author of virtus-2.0.0 to request adding ostruct into its gemspec.

Because axe-core-gems uses virtus, and virtus uses ostruct, users of axe-core-gems will start to see this warning when they upgrade to Ruby 3.3.5.

Ideally, virtus itself would add ostruct to its gemspec, but virtus is discontinued and has not received an update in years and is not likely to receive one again. Given that, I suggest axe-core-gems adds ostruct to its gemspecs, to make sure the gem version is installed and used. That way, no warning will be printed and the gem should be compatible with Ruby 3.5.0.

Note: this is a fork of #403 that allows CI to run.

No QA required.

@scottmries scottmries mentioned this pull request Sep 18, 2024
scottmries added a commit that referenced this pull request Sep 18, 2024
When running CI on [another
PR](#404), Selenium would
consistently fail with
```
Failure/Error: $driver.get fixture "/index.html"
Selenium::WebDriver::Error::InvalidSessionIdError: invalid session id
```

This [appears to be due to resourcing issues for new versions of
Chrome](https://stackoverflow.com/questions/56002701/selenium-webdriver-error-invalid-session-id);
pinning the Chrome version in CI consistently fixes the issue.

No QA needed.
@scottmries scottmries closed this Sep 18, 2024
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.

Request: Remove virtus dependency
2 participants