-
Notifications
You must be signed in to change notification settings - Fork 0
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
bump faraday version - to avoid multipart warning #1
base: master
Are you sure you want to change the base?
Conversation
help_scout-sdk.gemspec
Outdated
@@ -31,7 +31,7 @@ Gem::Specification.new do |spec| | |||
spec.require_paths = ['lib'] | |||
|
|||
spec.add_dependency 'activesupport' | |||
spec.add_dependency 'faraday', '1.7.2' | |||
spec.add_dependency 'faraday', '1.9.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mfittko @BassamAziz any reason why we don't update this to 1.9.3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo no
@bassam we could probably go to latest faraday (2.9.0) - let's run the tests though |
lib/help_scout/api/client.rb
Outdated
@@ -13,7 +13,7 @@ def connection | |||
@_connection ||= build_connection.tap do |conn| | |||
if authorize? | |||
HelpScout::API::AccessToken.refresh! | |||
conn.authorization(:Bearer, access_token) if access_token | |||
conn.request :authorization, 'Bearer', 'authentication-token' if access_token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mfittko I think this isn't working yet, because when I run a HelpsScout query in the console of the update-bugsnag-faraday branch, I get the error HelpScout::API::NotAuthorized: The access token is invalid or has expired
I don't get the error if I try that on master. Also the same error shows up on bugsnag for the testing_cobain_testing stage on bugsnag from last nights cron-jobs - not sure if that is related?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ouch, yeah we need to use the token not some random string 🤦
No description provided.