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

Follow up #34064 #34109

Merged
merged 1 commit into from Oct 10, 2018
Merged

Follow up #34064 #34109

merged 1 commit into from Oct 10, 2018

Conversation

bogdanvlviv
Copy link
Contributor

@bogdanvlviv bogdanvlviv commented Oct 6, 2018

The removed code was added in 7f870a5,
then 7f870a5 was reverted by #34064.
But I found that that commit wasn't completely reverted, I guess it was
caused by resolving some conflicts during reverting.
@schneems could you please confirm that those changes weren't reverted
unintentionally, or reject this commit otherwise?

r? @schneems

The removed code was added in 7f870a5,
then 7f870a5 was reverted by rails#34064.
But I found that that commit wasn't completely reverted, I guess it was
caused by resolving some conflicts during reverting.
@schneems could you please confirm that those changes weren't reverted
unintentionally, or reject this commit otherwise?
@schneems
Copy link
Member

schneems commented Oct 7, 2018

If I missed something it was due to a merge conflict resolved incorrectly. My goal was to get “rails s” on master working again which my revert did. I don’t know that it’s 100% necessarry that all the code be removed. If we do merge this we need to let @tenderlove know so when he goes to work on this again he knows to revert both merge commits.

I restarted the failing tests.

@nicolasmlv
Copy link
Contributor

@schneems Some more information I found:

@eileencodes eileencodes merged commit 8a1cc51 into rails:master Oct 10, 2018
@eileencodes
Copy link
Member

"rails s" on master was working

This is true but it also broke GitHub's build that runs against master so I approved the revert (and we don't use devise). I think other apps would have broken as well.

@bogdanvlviv bogdanvlviv deleted the follow-up-34064 branch October 10, 2018 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants