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

Running with Rack > 3.1 gives error uninitialized constant Rack::Handler #151

Closed
4 tasks done
pezholio opened this issue Jun 14, 2024 · 1 comment · Fixed by #152
Closed
4 tasks done

Running with Rack > 3.1 gives error uninitialized constant Rack::Handler #151

pezholio opened this issue Jun 14, 2024 · 1 comment · Fixed by #152

Comments

@pezholio
Copy link
Contributor

pezholio commented Jun 14, 2024

Pre issue-raising checklist

I have already:

  • Read through the relevant docs at https://docs.pact.io
  • Upgraded to the latest version of the gem
  • Checked the CHANGELOG to see if the issue I am about to raise has been fixed
  • Created an executable example that demonstrates the issue using either a:
    • Dockerfile
    • Git repository with a Travis or Appveyor (or similar) build

Software versions

  • OS: Mac OSX 14.5
  • pact mock service: v 3.12.1

Expected behaviour

Tests pass

Actual behaviour

When running the tests with Rack version >= 3.1.0, the tests fail with the error:

NameError:
    uninitialized constant Rack::Handler

This looks related to changes in Rack starting 3.1.0 - https://github.com/rack/rack/blob/main/CHANGELOG.md#310---2024-06-11

Steps to reproduce

An example build with Rack > 3.1.0 ❌

https://github.com/alphagov/pact-mock_service/actions/runs/9513302857

And example build with Rack < 3.1.0 ✅

https://github.com/alphagov/pact-mock_service/actions/runs/9513330459

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 a pull request may close this issue.

2 participants