-
Notifications
You must be signed in to change notification settings - Fork 352
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
Remove legacy Rails and Rubies #366
Conversation
Whoops, accidentally closed it |
Currently requiring the whole of Rails to get the tests running. But I think it would be possible to reduce it to active support and active record maybe. First I want a green test run on at least all the active record tests. I'm not really sure how to tackle the mongoid and redis tests atm. never used those with rpush. |
I can't seem to get rpush to work with mongoid for now. Since I'm not sure if the tests heavily depend on Rails in a way that would make them fail, but even now the tests for Rails 4.2 fail. Anyone using I guess requiring Rails for all the tests makes no sense, so I guess I'd have to split the gemfiles even further in the sense that there'll be "mongoid" gemfiles and "regular" ones. Otherwise, since we cannot support MongoDB because of |
5aea737
to
f1eb5b4
Compare
@aried3r nice! any plans to release this to rubygems ? |
@aried3r , FYI after update rails we have strange error in our specs
|
Hmm, I already run rpush 3.0.0 RC1 in production since yesterday after testing for a week in staging. However with Rails 5.0.5, not 5.0.6 RC1. Do you actively run rpush in the specs or just check if there's new notifications in the database? Because I only test for that, without actually running rpush (since there's no dry-run implemented yet). |
@aried3r this can be miss-configuration in our test environment. We found out that this patch resolves this error
Did you have any issues when stop / restart rpush daemon ? |
btw ::ActiveRecord::Base.connection.close was introduced here 5653cab#diff-8c805eff0bcb8b533ecd802f81287ce1L149 |
Just tried on our staging server. Stopping, starting etc is no problem using 3.0.0.rc1. That change is three years old and seems not to have been touched since then https://github.com/rpush/rpush/blob/v3.0.0.rc1/lib/rpush/daemon/store/active_record.rb#L164 Can you make sure you're running 3.0.0.rc1? (I see you're pointing to I'm afraid I can't really help in this case. It's a Works on my machine!™ type-a-deal :D But feel free to open a new issue, this PR might not be the best place for others to see. I also plan to roll out the RC1 as a stable version by next week (wanna test in production some more) so more users will probably update and report bugs (which I hope there aren't any). |
@aried3r works for me as well, this lines just logged to log file. refs https://github.com/rails/rails/pull/14938/files#diff-c226a4680f86689c3c170d4bc5911e96R149 |
@aried3r I'm a heavy |
Remove legacy Rails and Rubies
I think even though this gem is kinda-sorta unmaintained (as in, there are no new releases), I think it's time we clean up some stuff.
Things I want to try to do for rpush "4.0" (or 3.0, if we want to add breaking changes there, but I think a lot of people are already using the
master
branch):I'm open for discussion!
Fixes #364