FIX: Twitter health check broken on Faraday update#35407
Merged
Conversation
tgxworld
approved these changes
Oct 15, 2025
|
This pull request has been mentioned on Discourse Meta. There might be relevant details there: https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/5 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the problem?
Faraday updated their authentication/authorization middleware in version 2, which was a breaking change for the Twitter auth health check.
Why didn't we catch it?
The test was manually mocking and stubbing the individual Faraday objects, so the relevant code path wasn't exercised by our tests.
How does this fix it?
stub_requestinstead. (This correctly catches the deprecated method error.)