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

0.9.1.beta2 does not work with Ruby 3.3 #553

Closed
tagliala opened this issue Jan 4, 2024 · 10 comments · Fixed by #554
Closed

0.9.1.beta2 does not work with Ruby 3.3 #553

tagliala opened this issue Jan 4, 2024 · 10 comments · Fixed by #554

Comments

@tagliala
Copy link
Contributor

tagliala commented Jan 4, 2024

$ mailcatcher -f -v --http-ip=0.0.0.0
Starting MailCatcher v0.9.1.beta2
==> smtp://127.0.0.1:1025
==> http://0.0.0.0:1080
image

Unfortunately I cannot run specs on my machine, it looks like that there are issues with base64 (no longer a default gem) and maybe more

tagliala added a commit to tagliala/mailcatcher that referenced this issue Jan 16, 2024
Also:

- Fix compatibility with latest Selenium
- Test against Ruby 3.3
- Bump Sinatra and Rack dependency to allow Ruby 3.3

Close sj26#553
tagliala added a commit to tagliala/mailcatcher that referenced this issue Jan 16, 2024
3.0 will EOL soon, and it has issues when compiling eventmachine

Also:

- Fix compatibility with latest Selenium
- Bump Sinatra and Rack dependency to allow Ruby 3.3

Close sj26#553
tagliala added a commit to tagliala/mailcatcher that referenced this issue Jan 16, 2024
3.0 will EOL soon, and it has issues when compiling eventmachine

Also:

- Fix compatibility with latest Selenium
- Bump Sinatra and Rack dependency to allow Ruby 3.3

Close sj26#553
tagliala added a commit to tagliala/mailcatcher that referenced this issue Jan 16, 2024
3.0 will EOL soon, and it has issues when compiling eventmachine

Also:

- Fix compatibility with latest Selenium
- Bump Sinatra and Rack dependency to allow Ruby 3.3
- Bump version to 0.10.0.alpha1

Close sj26#553
@matt-whiteley
Copy link

This issue is affecting 0.9.0 release on ruby 3.3.0

If the fix is just upgrading the dependencies then this needs to be merged and released because mailcatcher is unusable for anyone who is running ruby 3.3 currently.

@FinnIckler
Copy link

FinnIckler commented Feb 6, 2024

Also just noticed this investigating a failing healthcheck for mailcatcher. Here's a minimal repo:

docker run -it ruby:3.3.0 /bin/bash
gem install mailcatcher
mailcatcher --http-ip=0.0.0.0 --no-quit
curl localhost:1080 # Internal server error

gregorbg pushed a commit to thewca/mailcatcher that referenced this issue Feb 7, 2024
3.0 will EOL soon, and it has issues when compiling eventmachine

Also:

- Fix compatibility with latest Selenium
- Bump Sinatra and Rack dependency to allow Ruby 3.3
- Bump version to 0.10.0.alpha1

Close sj26#553
@markymc
Copy link

markymc commented Apr 3, 2024

I'm also seeing this issue on Ruby 3.3.0. Is there a workaround?

@matt-whiteley
Copy link

I'm also seeing this issue on Ruby 3.3.0. Is there a workaround?

Use rbenv or rvm, and cd into a folder configured to use an older ruby version before starting mailcatcher.

@dorianmariecom
Copy link

e.g.:

> mkdir mailcatcher
> cd mailcatcher
> echo "3.2.2" > .ruby-version
> echo "ruby 3.2.2" > .tools-versions
> asdf install
> gem install mailcatcher
> mailcatcher --foreground
Starting MailCatcher v0.9.0
==> smtp://127.0.0.1:1025
==> http://127.0.0.1:1080

@sj26
Copy link
Owner

sj26 commented May 17, 2024

Pushed to rubygems — please try it out:

gem install mailcatcher --pre

After a couple of good reports I will promote this to v0.10.0.

@andreynering
Copy link

@sj26 It works for me! 😄

@tagliala
Copy link
Contributor Author

15:51:32 mailcatcher.1    | Starting MailCatcher v0.10.0.alpha1
15:51:32 mailcatcher.1    | ==> smtp://127.0.0.1:1025
15:51:32 mailcatcher.1    | ==> http://0.0.0.0:1080
15:52:34 mailcatcher.1    | ==> SMTP: Received message from '<[email protected]>' (271 bytes)

Works for me too

@ansonhoyt
Copy link

Works for me with Ruby 3.3.0 and Rails 7.1.

@mockdeep
Copy link
Contributor

Works for me!

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.

9 participants